Hey all, I know there have been a few threads on connection issues already, but these all seem to be due to issues with map groups or player slots. I am attempting all of the below on 64 bit Debian 6 with a mostly vanilla set up (no plugins, no custom config files other than ones that won't get executed until a client asks, e.g. 5on5.cfg). I didn't experience this problem before the last two updates. I don't experience this problem on 64 bit Ubuntu 12.04 LTS - I may not have the *exact* same files set up on it though.
*The Problem:* When I first launch the server I am not able to connect to it through the console or the server browser, the client times out when connecting until I get the pop up "Disconnected \nConnection failed after 10 retries.". Sample output below: 4038.293: Sending UDP connect to public IP 46.38.163.156:27015 Retrying public(46.38.163.156:27015) ... etc. I am however able to see the server in the server browser and it responds to pings/status correctly. I am also able to run commands on it via RCON. My start up line: ./srcds_run -game csgo -port 27015 -tickrate 128 -console -usercon +game_type 0 +game_mode 1 +mapgroup mg_bomb +map de_inferno -maxplayers_override 12 Changing the port, maxplayers, tickrate and map (at least any de_*) in the start up line does not change the behaviour. I have not experimented with the game type or mode yet. To keep things simple *I have not edited* gamemodes.txt or created a gamemodes_server.txt file and I do not have a server.cfg (although I still experience these issues when I have a basic server.cfg). *The (Hacky) Solutions:* *Option 1: Patience* After about 15 minutes or so the server will get it's act together and let people join, without me touching anything or sending any commands. It is possible to know exactly when this is by watching the output of the server; it finally says "Connection to Steam servers successful." and gives the public IP. I've put the output on Pastebin and noted where the delay is in case anyone is interested: http://pastebin.com/pejzjsx7 *Option 2: Change the map a couple of times* * * Yeah, really. I can't remember why I thought it would be a good idea to try this, but it works. I wouldn't call my results scientific, but changing the map to a de_*_se map seems to fix the server first time 100% of the time, however given the specified map group of mg_bomb it is necessary to change it back to a non de_*_se map before people are able to connect of course. Changing the map to a non de_*_se map can take up to three map changes (I've not seen it take any more but that may just be down to chance) before the server lets people join - simply reloading the existing map does the trick too. As with option 1, we can tell when people are able to connect to the server by watching for the output "Connection to Steam servers successful." I have uploaded example console output from this method as well: http://pastebin.com/RCmjEJn6 *Thoughts:* I have no idea what is causing the issue described in this email, but I thought I would share my findings with others in case someone else is experiencing this, or knows of a better solution, but also because it is weird and therefore interesting. It is possibly something to do with the two lines, pasted below, right at the start of the server booting up. I don't get them on my Ubuntu set up, which runs the server correctly as mentioned above. ./srcds_run: 446: pushd: not found ./srcds_run: 446: popd: not found These are used in the srcds_run bash script that acts as a wrapper around the srcds_linux executable. However if I execute srcds_linux directly I still have the same issues. If anyone has any ideas/suggestions/comments please do speak up! All the best, Chris
_______________________________________________ Csgo_servers mailing list [email protected] https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers
