Vitality first of all thanks for telling about this as up till now I thought it was strictportbind command which wasn't working but I found out there's another command now. If there is proper detailed documentation on startup commands then we can utilize the servers better without asking help here alot. Also, many bugs still remain which valve needs to fix like occasional vote map being available to some users by pressing escape even through if its disabled etc On 24 Nov 2015 01:19, "Vitaliy Genkin" <[email protected]> wrote:
> FYI: If your game server specifies exact server ports on the command line > (using +hostport XXXX +clientport YYYY +tv_port ZZZZ -steamport NNNN) then > you should also add -net_port_try 1: this will prevent the second instance, > even if launched by mistake, from trying to “port-climb” attempting to find > vacant ports bigger than requested and the second instance will immediately > exit before attempting to log in with the same GSLT and kicking the main > server instance. > > > > Best of course is to find the real reason why the second instance is > launched by mistake, but running with -net_port_try 1 is going to guarantee > reliable port assignment across multiple server instances on the same > machine. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Marcin Paterek > *Sent:* Monday, November 23, 2015 6:15 AM > *To:* [email protected] > *Subject:* Re: [Csgo_servers] Connection to Steam servers lost (result 34) > > > > Thanks, Nicholas. > > > > 2015-11-23 14:59 GMT+01:00 Nicholas Hastings <[email protected]>: > > The "34 error" is a symptom of your issue, not the cause. > > EResult 34 is LogonSessionReplaced, which is exactly what's happening when > you have a second instance start with the same token. > > -- > Nicholas Hastings > AlliedMods.net <http://www.alliedmods.net> > > > > > *Marcin Paterek* <[email protected]> > > Monday, November 23, 2015 8:08 AM > > Yeah, we're investigating it together. Still, we can't find what exactly > causes the bug and we hoped it may be connected to that 34 error. If that's > not the case... ehh, we're going to look further into. > > > > _______________________________________________ > Csgo_servers mailing list > [email protected] > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers > > *Don Park* <[email protected]> > > Monday, November 23, 2015 8:02 AM > > This sounds like something you should talk with your service provider. > I'd suggest you talk with them about it as this is probably outside the > scope of this email list. Either have them disable/prevent the second > instance from starting up or something. > > > > > > _______________________________________________ > Csgo_servers mailing list > [email protected] > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers > > *Marcin Paterek* <[email protected]> > > Monday, November 23, 2015 7:56 AM > > As long as there is only one instance, my server works fine. But when the > second instance appears out of the blue, it 'overtakes' the token - you > cannot connect to the first instance (though there may be people still > playing) until I kill both of them and start the server normally again. I'm > kind of confused, because we can't find what's causing a second instance to > start. We've tried to disable SM, run vanilla server, disable GOTV - no > luck at all. > > > > _______________________________________________ > Csgo_servers mailing list > [email protected] > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers > > *Don Park* <[email protected]> > > Monday, November 23, 2015 7:15 AM > > That's the bug. > > > > Only 1 instance can be connected at a time. So your provider having an > issue with running a second instance is an issue with their deployment. > Because this is what it sounds like. > > > > Step 1: You start your server, your GSLT connects to Valve's servers and > gives your server the go-ahead. > > Step 2: Wait a little bit. > > Step 3: The second instance logs on, connects via the same GSLT and > connects to Valve's servers and gives the second instance the go-ahead. > > Step 3.5: Valve's servers stops communicating with your server (therefore > result 34) and you get the error > > Step 4: You restart your server, which then goes back to Step 1. > > > > I'd suggest for you to diagnose it, consider running your server IP > against Valve's API. > > > > > http://api.steampowered.com/ISteamApps/GetServersAtAddress/v0001?addr=203.189.71.xxx > > > > Of course, add your own IP to the end there. So run that when it's > working, and then run it again when it's not. If ""success": false," for > the second time running, then you can kinda suggest/think it's the GSLT > that's causing the issue. > > > > Also, may or may not be stating the obvious, but can your server connect > to Steam servers? > > > > > > _______________________________________________ > Csgo_servers mailing list > [email protected] > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers > > *Marcin Paterek* <[email protected]> > > Monday, November 23, 2015 6:32 AM > > I know, but that doesn't help me to find the bug. > > > > _______________________________________________ > Csgo_servers mailing list > [email protected] > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers > > > > > _______________________________________________ > Csgo_servers mailing list > [email protected] > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers > > > > _______________________________________________ > Csgo_servers mailing list > [email protected] > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers >
_______________________________________________ Csgo_servers mailing list [email protected] https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers
