Error on server startup

[Floppy_Drive]

Hi all,

I'm trying to kick off my server with:

./ucc server CTF-Citadel.ut2?game=XGame.xCTFGame?mutator=XGame.MutI nstaGib -ini=UT2003.ini

But I get the following error:

[code:1:cc2654573d]TeamGame::InitGame : bBalanceTeams True
UdpServerQuery(crt): Port 7789 successfully bound.
Resolving master0.gamespy.com...
MasterServerUplink: MasterServerGameStats not found - stats uploading disabled.
FUdpLink::BindPort: Failed to bind UDP socket to port
Executing UObject::StaticShutdownAfterError
FUdpLink::BindPort: Failed to bind UDP socket to port

History:

Exiting due to error
Exiting.
Waiting for file streaming thread to finish...
Name subsystem shut down
[/code:1:cc2654573d]
Being new to the world of server admin (you guys never guessed that did you :sigh: ) I don't know what to change / check / throw out the window etc. All help will be greatly appreciated!!
How about you nice unrealadmin.org admins write an idiots guide to setting up a server? I'll start the first line of the tutorial off for you:

Step 1: Telnet to your shell, type in login and password...

:withstupid:

[Azazel]

You mean this one?
http://www.unrealadmin.org/modules.p...rticle&artid=8

[Floppy_Drive]

Nice tutorial there. Though it's not really a complete one... It doesn't mention that the user.ini file needs to be edited - specifically removing the lavagiant3 entry and adding maul. Nor does it point out what parts ot the ut2003.ini need to be altered etc. Though for sure I did learn from reading it Besides, this still leaves me wondering how to resolve the "Failed to bind UDP socket to port" error.

[fmonkey]

"Failed to bind UDP socket to port" is an OS-level error. It means the bind() function failed, which is usually one of two things. 1) You are not root and you are trying to bind to an emperical port (<1024), or 2) something is already bound to the port. Try running `netstat -an | grep LISTEN | grep <port number>" where port number is the port you are trying to bind to. If you don't know the port, which in this case it appears you might not, try `netstat -an | grep LISTEN | grep udp` and then use `lsof` to identify what programs are bound to those ports.

[Floppy_Drive]

fmonkey,

thanks for the reply, put me on track, and now the problem is solved