You probably have a source tv instance running on that port already.. If
i'm correct, your CS:S server will automatically claim the first
portnumber above that if the originally requested one is unavailable.
Probably the source tv port of you HL2MP server is causing (27017 +5 =
27022) this.. You could also do a netstat -nlu to see which udp ports
are in use.
On your command line specify all the three ports when you start your
server(s) as below, to avoid this kind of problem. Works for HL2 as well..
./srcds_run -game cstrike -port 27015 +tv_port 27020 +clientport 27005
+ip xxx..xxx.xxx.xxx +map de_dust +maxplayers 16 -autoupdate &

Hope this helps..
Regime

Hi List,
i have a strange problem, maybe someone can explain it to me:
My OS: SuSe 9.2 (german)
Running servers on it:
CS:S Servers @ port 27015
CS:S Server @ port 27022
HL2mp @ port 27017
DoD:S @ port 27024

i start every server with the "-ip xx.xx.xx.xx -port xxxxx" option.
Sometimes on of the CS-Servers, the one running on port 27022, started at
port 27023.
restarting the CS-Server or rebooting the whole linux-box dosen´t solve the
problem.

i didn´t installed a new application, i didn´t change anything on my server.
maybe the next day, after a scheduled daily reboot (@6:00am) of the server,
everything works fine again.
Sometimes the server runs 2~4 days at the "new" port and then he falls back
to the port he is configured.

Could someone explain this behavior to me ?


thank you
Ulf


--


_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux


_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux




_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux

Reply via email to