edit: installed 2.0h and things seem to work fine. have you changed modmanager.con in any way? what's your settings for mm_rcon.rconIp and mm_rcon.rconPort?

edit2: if you haven't rebooted the server you're running the 2142 server on, try doing that. the ip/port might have gotten tied up due to one of the previous script versions.

[2010-09-23 13:55:57] Error: Failed to bind rcon socket, only in-game rcon will be enabled ((98, 'Address already in use'))
[2010-09-23 13:55:57] Error: Traceback (most recent call last):
  File "admin/modules/mm_rcon.py", line 921, in openSocket
    self.__socket.bind( ( self.__config['rconIp'] , self.__config['rconPort'] ) )
  File "<string>", line 1, in bind
error: (98, 'Address already in use')

and bf2142cc cant login

tested it with the default admin script and there it works , have access through BF2ra
but cannot use bf2142cc since it needs modmanager

the server runs now withouth mm, cause autoupdate should work now too

this is weird. i just started up my test server and it correctly shut down and updated.

also weird. external rcon connections works fine for me. if you start the script, wait for the server to fully load, and then immediately try to connect to rcon, does it still not work?

not sure i fully understand the problem. with the -noauto option, the server should not interfere with rcon in any way, it does not make use of it. only the auto updater does

had the server run with the new script on autoupdate, but it didnt update to 1017 automatically, did a restart today then it updated

external rcon also dont work yet

and seems a problem with the -noauto parameter, bf2142cc still dont work with, you have to change pass or port in default.cfg to something else than the right one, then it works
using latest modmanager (2.0h), not the default one btw

LINK

but server is now running with enabled autoupdater, I will tell you then with next hotfix

main problem is anyway, the extern rcon port is blocked with that function, so you dont have any access from outside to the server, only with console and ingame rcon

I've got an updated script that reinstates the auto-update function, but makes it optional. If you could try to run it with the auto-update function enabled (it is on by default). We should have a new hotfix out pretty soon.

I've tested it with both python 2.5 and 2.6 and it should be fine.

LINK

Usage: FirstStrikeServer.py <options> <server args>

Options:
-noauto
Disables the auto-updating function. Server will no 
longer periodically check for new updates and install them. 
It will still check for updates every time it crashes or is exited out of.

-log
Will generate a file log in the Battlefield 2142 server folder 
with the name FirstStrikeServer<timestamp>.log

NOTE
Add any additional server arguments after the options.

To exit script, shut down server and while the script 
waits to restart it, press Ctrl-C to terminate script.

good job

edit: did find one possible error, updated script. will continue to check it, and get myself 2.5 to see if i can replicate the error.

i missed you by 10 minutes on IRC, was busy with something else.

LINK

edit:
no still same, saw you removed the try expect
and even more strange is, when I start it over and over it does work

maybe something with my python ? its ver 2.5.2

i updated the script, the new one should hopefully give you an error message.

LINK

server updates now correctly
but another problem now, it dont start the server
all i get is this:

[Mon Sep  6 20:53:35 2010] Checking for new updates..
[Mon Sep  6 20:53:36 2010] New versions: []
[Mon Sep  6 20:53:36 2010] No new versions
[Mon Sep  6 20:53:36 2010] Launching server...
[Mon Sep  6 20:53:36 2010] /home/bf2pr/server2/bf2142

then the script close itself

The new script can be found HERE

If you run the script while your FirstStrike server is already running, you will get a prompt to restart it. Also this script currently does not periodically check to see if any updates are available. However exiting the server will make it check for updates and start again. Other than that it should behave just as the old one (minus the not working part)