I've found that the order in which you start up the HL1 and HL2 servers is extremely important, depending especially on how you specify ports in the launch properties.
1. It's always important to launch servers with the target port in the launch properties, although on an all SRCDS servers they will auto search for a free port if one is taken, it's still best to make sure that they all launch on their intended port (keeps your regulars a lot happier too). 2. Start all servers in incrementing port sequence (this seems to help keep things clean). 3. Never start all servers at once, always start servers 30 to 60 seconds apart, at the very minimum wait until they successfully log onto the steam servers. 4. all servers should have unique -sport specified (VAC port) - you can skip specifying this you only run HL2 servers but if you mix and match it's very important to specify them. 5. make sure for SRCDS servers that the port is open for TCP as well as UDP in the firewall/router if you want RCON to work 6. Ideally, all HLDS services must be restarted at least once before you start a server on the next port ... don't ask me why but all HLDS servers that haven't been restarted at least once are sure to act strangely and starting the next server when the previous one hasn't been restarted may well also start acting weird. This is one setup I find work the best for me: a. SRCDS on port 27015 should be started first with -port 27015 -sport 26902 in the launch properties b. HLDS on port 27016 should be started second with -port 27016 -sport 26904 in the launch properties On my linux server, If I start HLDS first, then one or more SRCDS processes this seems to work ok without specifying the -sport, but if I start an SRCDS and then an HLDS server, HLDS gets very confused and will act weird. I mostly believe that the problem here is SRCDS will look for ports it needs and if they are not available it will automatically try the next in sequence, but HLDS is not able to search at all and instead of complaining that it's unable to acquire a needed port it just stalls there. Just a last gotcha note, if you have to shut down the HLDS server and restart it (or it crashes, etc) you may find that weirdness will return when it restarts again in a system with SRCDS servers already running. Specifying both ports appears to help this, but the HLDS server must be restarted at least once to get it clean. (By restart I mean in HLDS issuing the "restart" command or any changelevel <mapname>) ----- Original Message ----- From: "Andreas Kang Schøyen" To: <[email protected]> Sent: Tuesday, April 24, 2007 12:41 AM Subject: [hlds_linux] Problems running SRCDS and HLDS at the same server Are there any known issues to run HLDS and SRCDS at the same server? I have bought a "super server" capable of running many servers, but I have met some errors along the way. It seems that the SRCDS interfere with the Steam Validation for hlds? Sometimes the hlds servers can't validate steamids and all the new players get steamid pending. And for the source servers.. they just get offline and no error message is printed to the console for the server. I have learned that SRCDS uses port 27020 -> for source TV and that's why I run hlds on port 27015-27019 and SRCDS on ports 27035-> The server has extern IP and all ports that HLDS and VAC need are opened up. Maybe get another IP to the server and run hlds on eth0 and srcds on eth0:1 ? Anyone? _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
