Try adding -strictportbind to each server's command line.
On 11/17/2013 5:15 AM, Кирилл Крылов wrote:
Hello Colleagues! Your updates are very pleasent for us, because they do our life more saturated, namely: after the last update from November 15 2013 we've got the problem - ANY FIRST running server CS:GO, (ecxept normal ports - 338xx, 269xx, 270xx, 270xx. 270xx), is using the port upd 27036. All the next running servers are using only standart five ports, but if you turn off the first server, then the next started server will take the freed port upd 27036. Why does that happen? We use this port for a different server, which can't start normaly if this port (27036) is already in use (busy). The Operation system - CentOS-6.4-x86_64 Core - 2.6.32-358.23.2.el6.x86_64 Library glibc - 2.12 We will be very grateful for any answer. _______________________________________________ Csgo_servers mailing list [email protected] https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers
--- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
_______________________________________________ Csgo_servers mailing list [email protected] https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers
