First Strike Forums — exiter.exe

Re: exiter.exe

2009-10-21T04:24:29Z

I've got things working correctly, but by default this and the extras running should not be there. For gameserver admins that do not have remote desktop access to their servers ( due to them having ranked servers BF2, BF2142, ETQW, etc. ) I have to make manual changes to their server in order for them to run a first strike server without the extra stuff running causing problems. The mod is one of the best there is for 2142, but these extras are killing it performance wise for those running the game in a dedicated server environment.

Server side nothing should need to be modified (except a command line or configuration files if needed) to run 2142 mods except for copying required files from the default directory to the mod directory if needed.

Re: exiter.exe

2009-10-20T17:06:46Z

Just turn it off with taskmanager -> processes once the server is up to date. At least, I am led to belive that is how the BlackIntel server admins did it, I'll double check then post back.

Re: exiter.exe

2009-10-20T16:30:42Z

Can the exiter.exe application be removed, as it is not necessary and causes extreme performance problems in a production gameservers environment. Along with the additional changes that were made that are out of the norm for regular mods updates, and general running of dedicated servers.

Re: exiter.exe

2009-04-19T15:38:25Z

I'll look into it, but Gwynzer feel free to explain how you set it up to run without it. I think you had it update, then just turned off the updater, right?

Re: exiter.exe

2009-04-19T04:30:33Z

Everything runs nice and smooth until the exiter application starts going crazy. then requires a manual closing of the application (restart of the gameserver) then things run as normal again. It's a random occurance and nothing unusual is going on when this happens.

Re: exiter.exe

2009-04-19T04:14:07Z

It was running on BlackIntel's WinXP (x64) Server, massive memory loss, we shut it off manually with no problems.... server restarts itself fine aswell after a crash...

Re: exiter.exe

2009-04-19T04:00:46Z

Windows 2003 Server
Q6600
4GBs of RAM
100Mb connection
250GB HDD

=====
BF2142_w32ded.exe.log
=====
Traceback (most recent call last):
File "bf2142_w32ded.py", line 2297, in
OSError: [Errno 2] No such file or directory
Traceback (most recent call last):
File "bf2142_w32ded.py", line 2297, in
OSError: [Errno 2] No such file or directory
Traceback (most recent call last):
File "bf2142_w32ded.py", line 2241, in
File "bf2142_w32ded.py", line 1059, in fetchDownload
ValueError: need more than 1 value to unpack
Traceback (most recent call last):
File "bf2142_w32ded.py", line 2241, in
File "bf2142_w32ded.py", line 1059, in fetchDownload
ValueError: need more than 1 value to unpack
Traceback (most recent call last):
File "bf2142_w32ded.py", line 2241, in
File "bf2142_w32ded.py", line 1059, in fetchDownload
ValueError: need more than 1 value to unpack
Traceback (most recent call last):
File "bf2142_w32ded.py", line 2241, in
File "bf2142_w32ded.py", line 1059, in fetchDownload
ValueError: need more than 1 value to unpack
=====

exiter.exe.log this error repeats multiple times
=====
Traceback (most recent call last):
File "exiter.py", line 13, in
File "wmi.pyo", line 1190, in connect
File "wmi.pyo", line 189, in handle_com_error
wmi.x_wmi: -0x7ff8fff2 - Not enough storage is available to complete this operation.
=====

Can this application be removed it's hurting the performance of our gameservers, as the problems starts to happen with and without players on the server, then rises in memory usage until I close it and restart it again?

Re: exiter.exe

2009-04-17T22:49:27Z

So far I've been unable to reproduce this issue, give me any and all information you have on it to aid in efforts to solve it.

Re: exiter.exe

2009-04-17T20:17:54Z

Any updates?
As it's still causing memory leaks, as most battlefield 2/2142 servers are run on Windows Server 2003/2008 or Linux operating systems in console mode on dedicated servers.

Re: exiter.exe

2009-03-25T13:26:25Z

The exiter does one thing only, monitors if your 2142 server crashes and then kills the updater on vista systems because XP doesn't support the python code to do this from within the updater itself. this is the first I've heard about a memory leak, I'll look into it.

Re: exiter.exe

2009-03-25T11:21:27Z

A vanilla problem?

exiter is not part of the vanilla BF2142 Server Installation, the problem appears to be the exiter application taking up 2GB+ at times even when the server is idle when the python wmi error messages are generated.

Would it be possible to add timestamps to the error log exiter application and more information about what it is doing before, during and after the errors appear?

Re: exiter.exe

2009-03-22T13:15:48Z

I think that is a Vanilla problem that we can't fix. I am not sure though.

Re: exiter.exe

2009-03-22T09:24:56Z

Will there be a fix for the massive memory usage for this application and cpu peaking from 0 to 17/20 percent every few seconds?

Free Space on server 100GBs+

Memory usage:
2GBs / 2,045,60K and more at times, seems to be a memory leak that almost uses up all of the systems RAM.

----
Traceback (most recent call last):
File "exiter.py", line 13, in
File "wmi.pyo", line 1190, in connect
File "wmi.pyo", line 189, in handle_com_error
wmi.x_wmi: -0x7ff8fff2 - Not enough storage is available to complete this operation.
----

Re: exiter.exe

2009-01-07T01:36:01Z

Re: exiter.exe

2009-01-07T00:35:19Z

this file is in the 1.4 updater zip file that you are supposed to copy into your main folder.