[hlds_linux] Matchmaking connecting us to sv_lan 1 servers
There are lots of times we tried to play a game through match making, and it finds a sv_lan 1 server and still tries to connect us. It gives us the LAN servers are restricted to local client (Class C) error. Then we tried again, and it connected us to an other sv_lan 1 server. We had to retry many times before finding a server we could play on. Please make the matchmaking ignore sv_lan 1 servers! AnAkIn ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] L4D fork
That's why i said if it's released. 2008/11/9 AnAkIn . [EMAIL PROTECTED] Yes, sv_public doesn't exist. 2008/11/9 Joseph Laws [EMAIL PROTECTED] I believe sv_public isn't a real cvar. That was a suggestion I made to the VALVe devs. ;p [EMAIL PROTECTED] wrote: -nomaster on the command line will stop your server from telling the master servers about itself, which is what sv_public does. Or set sv_search_key, which has the added bonus of not stopping your servers show up in the old-style server browser. -Original Message- From: [EMAIL PROTECTED] [mailto:hlds_linux- [EMAIL PROTECTED] On Behalf Of Flubber Sent: 09 November 2008 01:54 To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] L4D fork There is so many bug with the windows (browser, console, password request not being shown or disapearing behind one and each other) that make the experience so boring. Anyway if the sv_public 0/1 is really released it would be a relief, I passworded my servers for my community only but it's clearly not my favorite way since even with 1500 members the servers are not 100% of time full and i don't like to waste :p. 2008/11/9 Joseph Laws [EMAIL PROTECTED] You mean a browser like the one you open from the console presently? It looks like the same server browser used for other games...it just isn't auto-loaded and hasn't had its full functionality added yet. Flubber wrote: Not yet. I hope valve doesn't want to let the server system has it is actually, since the mailing list isn't barking anymore :). The game clearly need a real servr browser and a clean client interface to use it properly. 2008/11/9 Saint K. [EMAIL PROTECTED] When you use the '-fork' option, can you still specify a cfg per fork? Cheers, ___ 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 ___ 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 ___ 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
[hlds_linux] L4D Not VAC'd up
Hi My L4D is not showing up as VAC secured. Here is my server.cfg Can anyone spot if i have made a mistake please? I have commented some var's out that i dont think i need: // server name hostname (=*CBC*=) Cream Bun Clan - L4D Private Server // rcon passsword rcon_password passwrd sv_password //allow non-lobby people to join //sv_allow_lobby_connect_only 0 //Unreserve slots, aka fix the dumbass hibernating bug //sv_unreserve //Let people know they can join ANY time! //sv_tags Server Browser Join Enabled // Difficulty of the current game (Easy, Normal, Hard, Impossible) z_difficulty impossible sv_alltalk 1 sv_pausable 0 sv_cheats 0 sv_consistency 0 sv_voiceenable 1 // this will allow your server to be listed in the server browser setmaster add 68.142.72.250:27011 setmaster add 72.165.61.189:27011 setmaster add 69.28.151.162:27011 setmaster add 68.142.72.250:27011 // this will allows you to find a server through matchmaking with a specific search string sv_search_key cream_bun_clan // server logging log off sv_logbans 0 sv_logecho 1 sv_logfile 1 sv_log_onefile 0 // operation sv_lan 0 sv_region 3 // execute ban files exec banned_user.cfg exec banned_ip.cfg Thans in advance, Patrick ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
[hlds_linux] The 1000fps problem
Hi. I am really bothered, what is it that makes hlds NOT to use max resources from the server? A gameserver reaches 1000fps sometimes.. but mostly its about 970-985fps. Here's a paste from a server. http://paste.prco23.org/32971 This is a single server on a Debian Lenny setup, Dual Quadcore 2.5Ghz, 8GB RAM, 73GB SAS 15krpm. Anyone got their server to run 1000fps stable.. with few drops? Regards. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Matchmaking connecting us to sv_lan 1 servers
Yes, sv_lan 0 = internet, and sv_lan 1 = LAN, so you can't connect to them. 2008/11/9 Patrick Shelley [EMAIL PROTECTED] sv_lan 0 means its an internet server right? On 11/9/08, AnAkIn . [EMAIL PROTECTED] wrote: There are lots of times we tried to play a game through match making, and it finds a sv_lan 1 server and still tries to connect us. It gives us the LAN servers are restricted to local client (Class C) error. Then we tried again, and it connected us to an other sv_lan 1 server. We had to retry many times before finding a server we could play on. Please make the matchmaking ignore sv_lan 1 servers! AnAkIn ___ 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
Re: [hlds_linux] L4D Not VAC'd up
OK - this worked for me on restart, thanks, Patrick On 11/9/08, Mike Kent [EMAIL PROTECTED] wrote: Run it with -secure in the start line. On 9 Nov 2008, at 10:37, Patrick Shelley wrote: Hi My L4D is not showing up as VAC secured. Here is my server.cfg Can anyone spot if i have made a mistake please? I have commented some var's out that i dont think i need: // server name hostname (=*CBC*=) Cream Bun Clan - L4D Private Server // rcon passsword rcon_password passwrd sv_password //allow non-lobby people to join //sv_allow_lobby_connect_only 0 //Unreserve slots, aka fix the dumbass hibernating bug //sv_unreserve //Let people know they can join ANY time! //sv_tags Server Browser Join Enabled // Difficulty of the current game (Easy, Normal, Hard, Impossible) z_difficulty impossible sv_alltalk 1 sv_pausable 0 sv_cheats 0 sv_consistency 0 sv_voiceenable 1 // this will allow your server to be listed in the server browser setmaster add 68.142.72.250:27011 setmaster add 72.165.61.189:27011 setmaster add 69.28.151.162:27011 setmaster add 68.142.72.250:27011 // this will allows you to find a server through matchmaking with a specific search string sv_search_key cream_bun_clan // server logging log off sv_logbans 0 sv_logecho 1 sv_logfile 1 sv_log_onefile 0 // operation sv_lan 0 sv_region 3 // execute ban files exec banned_user.cfg exec banned_ip.cfg Thans in advance, Patrick ___ 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
Re: [hlds_linux] -fork query issue's
Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:27015 0.0.0.0:* - L4D server 4951/srcds_i486 udp 332 0 0.0.0.0:27016 0.0.0.0:* - L4D server 4724/srcds_i486 udp 332 0 0.0.0.0:27017 0.0.0.0:* - L4D server 4856/srcds_i486 udp 664 0 0.0.0.0:27018 0.0.0.0:* - L4D server 4859/srcds_i486 udp0 0 0.0.0.0:27019 0.0.0.0:* - L4D server 5067/srcds_i486 udp0 0 0.0.0.0:27020 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27021 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27022 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27023 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27024 0.0.0.0:* 5067/srcds_i486 udp0428 0.0.0.0:27025 0.0.0.0:* 5033/srcds_i486 udp 1660 0 0.0.0.0:27026 0.0.0.0:* 5033/srcds_i486 udp 5312 0 0.0.0.0:26901 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26902 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26903 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26904 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26905 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26906 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26907 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26908 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26909 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26910 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26911 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26912 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26913 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26914 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26915 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26917 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27005 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27006 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27007 0.0.0.0:* 4856/srcds_i486 The rest of these ports are a mystery to me. I'd expect the 6th server to run off 27020, but nothing replies there. I don't understand what 27020-27026 is used for either. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 1:49 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue's If you run netstat -nlpu | grep srcds: (numeric, listening, show programs, UDP) You should see all the UDP ports your 7 srcds processes are listening on (6 servers and the master). Each will probably be listening on 3 ports. One of them will be the actual game port. On Sun, 9 Nov 2008 13:12:50 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, On our Linux machine we now use the -fork option to spawn the L4D servers. The problem here is we can externally only query port 27015. The servers running on 27016, 27017, 27018 and 27019 don't respond on external query's. The 6th server from the -fork option spawns at a random port, not 27020. I can't find which port it runs off, although the CPU load indicates the 6th server is also being used. Cheers, ___ 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
Re: [hlds_linux] -fork query issue's
Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:27015 0.0.0.0:* - L4D server 4951/srcds_i486 udp 332 0 0.0.0.0:27016 0.0.0.0:* - L4D server 4724/srcds_i486 udp 332 0 0.0.0.0:27017 0.0.0.0:* - L4D server 4856/srcds_i486 udp 664 0 0.0.0.0:27018 0.0.0.0:* - L4D server 4859/srcds_i486 udp0 0 0.0.0.0:27019 0.0.0.0:* - L4D server 5067/srcds_i486 udp0 0 0.0.0.0:27020 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27021 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27022 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27023 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27024 0.0.0.0:* 5067/srcds_i486 udp0428 0.0.0.0:27025 0.0.0.0:* 5033/srcds_i486 udp 1660 0 0.0.0.0:27026 0.0.0.0:* 5033/srcds_i486 udp 5312 0 0.0.0.0:26901 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26902 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26903 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26904 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26905 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26906 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26907 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26908 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26909 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26910 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26911 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26912 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26913 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26914 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26915 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26917 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27005 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27006 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27007 0.0.0.0:* 4856/srcds_i486 The rest of these ports are a mystery to me. I'd expect the 6th server to run off 27020, but nothing replies there. I don't understand what 27020-27026 is used for either. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 1:49 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue's If you run netstat -nlpu | grep srcds: (numeric, listening, show programs, UDP) You should see all the UDP ports your 7 srcds processes are listening on (6 servers and the master). Each will probably be listening on 3 ports. One of them will be the actual game port. On Sun, 9 Nov 2008 13:12:50 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, On our Linux machine we now use the -fork option to spawn the L4D servers. The problem here is we can externally only query port 27015. The servers running on 27016, 27017, 27018 and 27019 don't respond on external query's. The 6th server from the -fork option spawns at a random port, not 27020. I can't find which port it runs off, although the CPU load indicates the 6th server is also being used. Cheers, ___ 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
Re: [hlds_linux] -fork query issue's
If you run netstat -nlpu | grep srcds: (numeric, listening, show programs, UDP) You should see all the UDP ports your 7 srcds processes are listening on (6 servers and the master). Each will probably be listening on 3 ports. One of them will be the actual game port. On Sun, 9 Nov 2008 13:12:50 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, On our Linux machine we now use the -fork option to spawn the L4D servers. The problem here is we can externally only query port 27015. The servers running on 27016, 27017, 27018 and 27019 don't respond on external query's. The 6th server from the -fork option spawns at a random port, not 27020. I can't find which port it runs off, although the CPU load indicates the 6th server is also being used. Cheers, ___ 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
Re: [hlds_linux] Matchmaking connecting us to sv_lan 1 servers
sv_lan 0 means its an internet server right? On 11/9/08, AnAkIn . [EMAIL PROTECTED] wrote: There are lots of times we tried to play a game through match making, and it finds a sv_lan 1 server and still tries to connect us. It gives us the LAN servers are restricted to local client (Class C) error. Then we tried again, and it connected us to an other sv_lan 1 server. We had to retry many times before finding a server we could play on. Please make the matchmaking ignore sv_lan 1 servers! AnAkIn ___ 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
Re: [hlds_linux] -fork query issue's
Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9 Nov 2008 14:14:55 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:27015 0.0.0.0:* - L4D server 4951/srcds_i486 udp 332 0 0.0.0.0:27016 0.0.0.0:* - L4D server 4724/srcds_i486 udp 332 0 0.0.0.0:27017 0.0.0.0:* - L4D server 4856/srcds_i486 udp 664 0 0.0.0.0:27018 0.0.0.0:* - L4D server 4859/srcds_i486 udp0 0 0.0.0.0:27019 0.0.0.0:* - L4D server 5067/srcds_i486 udp0 0 0.0.0.0:27020 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27021 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27022 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27023 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27024 0.0.0.0:* 5067/srcds_i486 udp0428 0.0.0.0:27025 0.0.0.0:* 5033/srcds_i486 udp 1660 0 0.0.0.0:27026 0.0.0.0:* 5033/srcds_i486 udp 5312 0 0.0.0.0:26901 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26902 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26903 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26904 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26905 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26906 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26907 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26908 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26909 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26910 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26911 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26912 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26913 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26914 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26915 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26917 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27005 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27006 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27007 0.0.0.0:* 4856/srcds_i486 The rest of these ports are a mystery to me. I'd expect the 6th server to run off 27020, but nothing replies there. I don't understand what 27020-27026 is used for either. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 1:49 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue's If you run netstat -nlpu | grep srcds: (numeric, listening, show programs, UDP) You should see all the UDP ports your 7 srcds processes are listening on (6 servers and the master). Each will probably be listening on 3 ports. One of them will be the actual game port. On Sun, 9 Nov 2008 13:12:50 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, On our Linux machine we now use the -fork option to spawn the L4D servers. The problem here is we can externally only query port 27015. The servers running on 27016, 27017, 27018 and 27019 don't respond on external query's. The 6th server from the -fork option spawns at a random port, not 27020. I can't find which port it runs off, although the CPU load indicates the 6th server is also being used. Cheers, ___ 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 ___ To unsubscribe, edit your list preferences, or view the list archives, please visit:
Re: [hlds_linux] -fork query issue's
Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue's Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9 Nov 2008 14:14:55 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:27015 0.0.0.0:* - L4D server 4951/srcds_i486 udp 332 0 0.0.0.0:27016 0.0.0.0:* - L4D server 4724/srcds_i486 udp 332 0 0.0.0.0:27017 0.0.0.0:* - L4D server 4856/srcds_i486 udp 664 0 0.0.0.0:27018 0.0.0.0:* - L4D server 4859/srcds_i486 udp0 0 0.0.0.0:27019 0.0.0.0:* - L4D server 5067/srcds_i486 udp0 0 0.0.0.0:27020 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27021 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27022 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27023 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27024 0.0.0.0:* 5067/srcds_i486 udp0428 0.0.0.0:27025 0.0.0.0:* 5033/srcds_i486 udp 1660 0 0.0.0.0:27026 0.0.0.0:* 5033/srcds_i486 udp 5312 0 0.0.0.0:26901 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26902 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26903 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26904 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26905 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26906 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26907 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26908 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26909 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26910 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26911 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26912 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26913 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26914 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26915 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26917 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27005 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27006 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27007 0.0.0.0:* 4856/srcds_i486 The rest of these ports are a mystery to me. I'd expect the 6th server to run off 27020, but nothing replies there. I don't understand what 27020-27026 is used for either. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 1:49 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue's If you run netstat -nlpu | grep srcds: (numeric, listening, show programs, UDP) You should see all the UDP ports your 7 srcds processes are listening on (6 servers and the master). Each will probably be listening on 3 ports. One of them will be the actual game port. On Sun, 9 Nov 2008 13:12:50 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, On our Linux machine we now use the -fork option to spawn the L4D servers. The problem here is we can externally only query port 27015. The servers running on 27016, 27017, 27018 and 27019 don't respond on external query's. The 6th server from the -fork option spawns at a random port, not 27020. I can't find which port it runs off, although the CPU load indicates the 6th server is also being used. Cheers, ___ 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,
Re: [hlds_linux] -fork query issue's
Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue's Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9 Nov 2008 14:14:55 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:27015 0.0.0.0:* - L4D server 4951/srcds_i486 udp 332 0 0.0.0.0:27016 0.0.0.0:* - L4D server 4724/srcds_i486 udp 332 0 0.0.0.0:27017 0.0.0.0:* - L4D server 4856/srcds_i486 udp 664 0 0.0.0.0:27018 0.0.0.0:* - L4D server 4859/srcds_i486 udp0 0 0.0.0.0:27019 0.0.0.0:* - L4D server 5067/srcds_i486 udp0 0 0.0.0.0:27020 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27021 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27022 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27023 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27024 0.0.0.0:* 5067/srcds_i486 udp0428 0.0.0.0:27025 0.0.0.0:* 5033/srcds_i486 udp 1660 0 0.0.0.0:27026 0.0.0.0:* 5033/srcds_i486 udp 5312 0 0.0.0.0:26901 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26902 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26903 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26904 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26905 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26906 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26907 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26908 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26909 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26910 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26911 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26912 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26913 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26914 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26915 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26917 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27005 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27006 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27007 0.0.0.0:* 4856/srcds_i486 The rest of these ports are a mystery to me. I'd expect the 6th server to run off 27020, but nothing replies there. I don't understand what 27020-27026 is used for either. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 1:49 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue's If you run netstat -nlpu | grep srcds: (numeric, listening, show programs, UDP) You should see all the UDP ports your 7 srcds processes are listening on (6 servers and the master). Each will probably be listening on 3 ports. One of them will be the actual game port. On Sun, 9 Nov 2008 13:12:50 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, On our Linux machine we now use the -fork option to spawn the L4D servers. The problem here is we can externally only query port 27015. The servers running on 27016, 27017, 27018 and 27019 don't respond on external query's. The 6th server from the -fork option spawns at a random port, not 27020. I can't find which port it runs off, although the CPU load indicates the 6th server is also being used. Cheers, ___ 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,
Re: [hlds_linux] Matchmaking connecting us to sv_lan 1 servers
thanks On 11/9/08, AnAkIn . [EMAIL PROTECTED] wrote: Yes, sv_lan 0 = internet, and sv_lan 1 = LAN, so you can't connect to them. 2008/11/9 Patrick Shelley [EMAIL PROTECTED] sv_lan 0 means its an internet server right? On 11/9/08, AnAkIn . [EMAIL PROTECTED] wrote: There are lots of times we tried to play a game through match making, and it finds a sv_lan 1 server and still tries to connect us. It gives us the LAN servers are restricted to local client (Class C) error. Then we tried again, and it connected us to an other sv_lan 1 server. We had to retry many times before finding a server we could play on. Please make the matchmaking ignore sv_lan 1 servers! AnAkIn ___ 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 ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
[hlds_linux] -fork query issue's
Hi, On our Linux machine we now use the -fork option to spawn the L4D servers. The problem here is we can externally only query port 27015. The servers running on 27016, 27017, 27018 and 27019 don't respond on external query's. The 6th server from the -fork option spawns at a random port, not 27020. I can't find which port it runs off, although the CPU load indicates the 6th server is also being used. Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] My first dedicated server with some problems
It's Debian 4.0
debian32:~# uname -a
Linux debian32 2.6.18.8-xenU-32bit-prod-static #3 SMP Wed Aug 27
15:07:53 ART 2008 i686 GNU/Linux
It only happens with Half-Life Deatmatch (-game valve)
Other games like Counter-Strike 1.6 works well in vanila instalations,
but cannot run amxmodx.
El sáb, 08-11-2008 a las 11:15 -0800, J T escribió:
What distribution are you running and can you do uname -a and paste it?
I'm not too sure what the problem could be.
On Fri, Nov 7, 2008 at 4:43 PM, Nevermore [EMAIL PROTECTED] wrote:
Sory... now i understanded that those lines wont help because those are
too few...
Server stop responding but it keeps writing lines in strace.log
Now i have taken last 50 lines...
As i can see, this is repeting over and over...
i think connection timed out message is the key...
look:
17799 19:32:34 gettimeofday({1226104354, 948735}, NULL) = 0
17799 19:32:34 clock_gettime(CLOCK_REALTIME, {1226104354, 948787000}) =
0
17799 19:32:34 futex(0x8274b08, FUTEX_WAIT, 82563, {0, 49948000}) = -1
ETIMEDOUT (Connection timed out)
17799 19:32:35 futex(0x8274aec, FUTEX_WAKE, 1) = 0
17799 19:32:35 time(NULL) = 1226104355
17799 19:32:35 time([1226104355]) = 1226104355
17799 19:32:35 stat64(/etc/localtime, {st_mode=S_IFREG|0644,
st_size=1267, ...}) = 0
17799 19:32:35 stat64(/etc/localtime, {st_mode=S_IFREG|0644,
st_size=1267, ...}) = 0
17799 19:32:35 gettimeofday({1226104355, 43446}, NULL) = 0
17799 19:32:35 gettimeofday({1226104355, 43501}, NULL) = 0
17799 19:32:35 gettimeofday({1226104355, 43557}, NULL) = 0
17799 19:32:35 clock_gettime(CLOCK_REALTIME, {1226104355, 4361}) = 0
17799 19:32:35 futex(0x8274aec, FUTEX_WAKE, 1) = 0
17799 19:32:35 select(8, [7], [7], [7], {0, 0}) = 1 (out [7], left {0,
0})
17799 19:32:35 gettimeofday({1226104355, 43821}, NULL) = 0
17799 19:32:35 clock_gettime(CLOCK_REALTIME, {1226104355, 43873000}) = 0
17799 19:32:35 futex(0x8274b08, FUTEX_WAIT, 82567, {0, 49948000}) = -1
ETIMEDOUT (Connection timed out)
17799 19:32:35 futex(0x8274aec, FUTEX_WAKE, 1) = 0
17799 19:32:35 time(NULL) = 1226104355
17799 19:32:35 gettimeofday({1226104355, 99793}, NULL) = 0
17799 19:32:35 gettimeofday({1226104355, 99854}, NULL) = 0
17799 19:32:35 gettimeofday({1226104355, 99910}, NULL) = 0
17799 19:32:35 clock_gettime(CLOCK_REALTIME, {1226104355, 99962000}) = 0
17799 19:32:35 futex(0x8274aec, FUTEX_WAKE, 1) = 0
17799 19:32:35 select(8, [7], [7], [7], {0, 0}) = 1 (out [7], left {0,
0})
17799 19:32:35 gettimeofday({1226104355, 100154}, NULL) = 0
17799 19:32:35 clock_gettime(CLOCK_REALTIME, {1226104355, 100208000}) =
0
17799 19:32:35 futex(0x8274b08, FUTEX_WAIT, 82571, {0, 49946000}) = -1
ETIMEDOUT (Connection timed out)
17799 19:32:35 futex(0x8274aec, FUTEX_WAKE, 1) = 0
17799 19:32:35 time(NULL) = 1226104355
17799 19:32:35 gettimeofday({1226104355, 156462}, NULL) = 0
17799 19:32:35 gettimeofday({1226104355, 156523}, NULL) = 0
17799 19:32:35 gettimeofday({1226104355, 156578}, NULL) = 0
17799 19:32:35 clock_gettime(CLOCK_REALTIME, {1226104355, 156644000}) =
0
17799 19:32:35 futex(0x8274aec, FUTEX_WAKE, 1) = 0
17799 19:32:35 select(8, [7], [7], [7], {0, 0}) = 1 (out [7], left {0,
0})
17799 19:32:35 gettimeofday({1226104355, 156855}, NULL) = 0
17799 19:32:35 clock_gettime(CLOCK_REALTIME, {1226104355, 156907000}) =
0
17799 19:32:35 futex(0x8274b08, FUTEX_WAIT, 82575, {0, 49948000}) = -1
ETIMEDOUT (Connection timed out)
17799 19:32:35 futex(0x8274aec, FUTEX_WAKE, 1) = 0
17799 19:32:35 time(NULL) = 1226104355
17799 19:32:35 gettimeofday({1226104355, 252751}, NULL) = 0
17799 19:32:35 gettimeofday({1226104355, 252814}, NULL) = 0
17799 19:32:35 gettimeofday({1226104355, 252870}, NULL) = 0
17799 19:32:35 clock_gettime(CLOCK_REALTIME, {1226104355, 252924000}) =
0
17799 19:32:35 futex(0x8274aec, FUTEX_WAKE, 1) = 0
17799 19:32:35 select(8, [7], [7], [7], {0, 0}) = 1 (out [7], left {0,
0})
17799 19:32:35 gettimeofday({1226104355, 253120}, NULL) = 0
17799 19:32:35 clock_gettime(CLOCK_REALTIME, {1226104355, 253172000}) =
0
17799 19:32:35 futex(0x8274b08, FUTEX_WAIT, 82579, {0, 49948000}
unfinished ...
El vie, 07-11-2008 a las 22:32 -0200, Nevermore escribió:
This is tail of strace.log, at this time server stopped responding but
process was still running:
17799 19:22:26 time(NULL) = 1226103746
17799 19:22:26 gettimeofday({1226103746, 799424}, NULL) = 0
17799 19:22:26 gettimeofday({1226103746, 799484}, NULL) = 0
17799 19:22:26 gettimeofday({1226103746, 799539}, NULL) = 0
17799 19:22:26 clock_gettime(CLOCK_REALTIME, {1226103746, 799604000}) =
0
17799 19:22:26 futex(0x8274aec, FUTEX_WAKE, 1) = 0
17799 19:22:26 select(8, [7], [7], [7], {0, 0}) = 1 (out [7], left {0,
0})
17799 19:22:26 gettimeofday({1226103746, 799794}, NULL) = 0
17799
Re: [hlds_linux] -fork query issue s
My guess is that they want queries to always run through the master server, since its controlling the forks. Could also be for simplified firewall rules for admins, etc. Kevin Saint K. wrote: Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9 Nov 2008 14:14:55 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:27015 0.0.0.0:* - L4D server 4951/srcds_i486 udp 332 0 0.0.0.0:27016 0.0.0.0:* - L4D server 4724/srcds_i486 udp 332 0 0.0.0.0:27017 0.0.0.0:* - L4D server 4856/srcds_i486 udp 664 0 0.0.0.0:27018 0.0.0.0:* - L4D server 4859/srcds_i486 udp0 0 0.0.0.0:27019 0.0.0.0:* - L4D server 5067/srcds_i486 udp0 0 0.0.0.0:27020 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27021 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27022 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27023 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27024 0.0.0.0:* 5067/srcds_i486 udp0428 0.0.0.0:27025 0.0.0.0:* 5033/srcds_i486 udp 1660 0 0.0.0.0:27026 0.0.0.0:* 5033/srcds_i486 udp 5312 0 0.0.0.0:26901 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26902 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26903 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26904 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26905 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26906 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26907 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26908 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26909 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26910 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26911 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26912 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26913 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26914 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26915 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26917 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27005 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27006 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27007 0.0.0.0:* 4856/srcds_i486 The rest of these ports are a mystery to me. I'd expect the 6th server to run off 27020, but nothing replies there. I don't understand what 27020-27026 is used for either. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 1:49 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue's If you run netstat -nlpu | grep srcds: (numeric, listening, show programs, UDP) You should see all the UDP ports your 7 srcds processes are listening on (6 servers and the master). Each will probably be listening on 3 ports. One of them will be the actual game port. On Sun, 9 Nov 2008 13:12:50 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, On our Linux machine we now use the -fork option to spawn the L4D servers. The problem here is we can externally only query port 27015. The servers running on 27016, 27017, 27018 and 27019 don't respond on external query's. The 6th server from the -fork option spawns at a random port, not 27020. I can't find which port it runs off, although the CPU load indicates the 6th server is also being used. Cheers, ___ To unsubscribe, edit your list preferences, or view the
Re: [hlds_linux] -fork query issue s
Hmm, didn't pick up on the can't query them aspect before. I certainly can with my own. Try running hlsw, typing in your IP, and appending :27016, 7, 8, 9 in sequence, until you get to about :30 I should also point out that I've had servers jump ports on restart. On Sun, 09 Nov 2008 08:25:58 -0700, Kevin J. Anderson [EMAIL PROTECTED] wrote: My guess is that they want queries to always run through the master server, since its controlling the forks. Could also be for simplified firewall rules for admins, etc. Kevin Saint K. wrote: Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9 Nov 2008 14:14:55 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:27015 0.0.0.0:* - L4D server 4951/srcds_i486 udp 332 0 0.0.0.0:27016 0.0.0.0:* - L4D server 4724/srcds_i486 udp 332 0 0.0.0.0:27017 0.0.0.0:* - L4D server 4856/srcds_i486 udp 664 0 0.0.0.0:27018 0.0.0.0:* - L4D server 4859/srcds_i486 udp0 0 0.0.0.0:27019 0.0.0.0:* - L4D server 5067/srcds_i486 udp0 0 0.0.0.0:27020 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27021 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27022 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27023 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27024 0.0.0.0:* 5067/srcds_i486 udp0428 0.0.0.0:27025 0.0.0.0:* 5033/srcds_i486 udp 1660 0 0.0.0.0:27026 0.0.0.0:* 5033/srcds_i486 udp 5312 0 0.0.0.0:26901 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26902 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26903 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26904 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26905 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26906 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26907 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26908 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26909 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26910 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26911 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26912 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26913 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26914 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26915 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26917 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27005 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27006 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27007 0.0.0.0:* 4856/srcds_i486 The rest of these ports are a mystery to me. I'd expect the 6th server to run off 27020, but nothing replies there. I don't understand what 27020-27026 is used for either. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 1:49 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue's If you run netstat -nlpu | grep srcds: (numeric, listening, show programs, UDP) You should see all the UDP ports your 7 srcds processes are listening on (6 servers and the master). Each will probably be listening on 3 ports. One of them will be the actual game port. On Sun, 9 Nov 2008 13:12:50 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, On our Linux machine we now use the -fork option to spawn the L4D servers. The problem here is we can externally only query port 27015. The servers running on 27016,
Re: [hlds_linux] -fork query issue s
Well, I can see them online in HLSW, but I can't communicate with it terms of sending commands / receiving output. If you try and setup a connection with HLSW, or our query's from the website, the error reads; Connection failed (No connection could be made because the target machine actively refused it. ) It only works on the first of the 6 servers in the fork, at 27015. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:47 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, didn't pick up on the can't query them aspect before. I certainly can with my own. Try running hlsw, typing in your IP, and appending :27016, 7, 8, 9 in sequence, until you get to about :30 I should also point out that I've had servers jump ports on restart. On Sun, 09 Nov 2008 08:25:58 -0700, Kevin J. Anderson [EMAIL PROTECTED] wrote: My guess is that they want queries to always run through the master server, since its controlling the forks. Could also be for simplified firewall rules for admins, etc. Kevin Saint K. wrote: Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9 Nov 2008 14:14:55 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:27015 0.0.0.0:* - L4D server 4951/srcds_i486 udp 332 0 0.0.0.0:27016 0.0.0.0:* - L4D server 4724/srcds_i486 udp 332 0 0.0.0.0:27017 0.0.0.0:* - L4D server 4856/srcds_i486 udp 664 0 0.0.0.0:27018 0.0.0.0:* - L4D server 4859/srcds_i486 udp0 0 0.0.0.0:27019 0.0.0.0:* - L4D server 5067/srcds_i486 udp0 0 0.0.0.0:27020 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27021 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27022 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27023 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27024 0.0.0.0:* 5067/srcds_i486 udp0428 0.0.0.0:27025 0.0.0.0:* 5033/srcds_i486 udp 1660 0 0.0.0.0:27026 0.0.0.0:* 5033/srcds_i486 udp 5312 0 0.0.0.0:26901 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26902 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26903 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26904 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26905 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26906 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26907 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26908 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26909 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26910 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26911 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26912 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26913 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26914 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26915 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26917 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27005 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27006 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27007 0.0.0.0:* 4856/srcds_i486 The rest of these ports are a mystery to me. I'd expect the 6th server to run off 27020, but nothing replies there. I don't understand what 27020-27026 is used for either. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 1:49 PM To:
Re: [hlds_linux] -fork query issue s
Well, I can see them online in HLSW, but I can't communicate with it terms of sending commands / receiving output. If you try and setup a connection with HLSW, or our query's from the website, the error reads; Connection failed (No connection could be made because the target machine actively refused it. ) It only works on the first of the 6 servers in the fork, at 27015. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:47 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, didn't pick up on the can't query them aspect before. I certainly can with my own. Try running hlsw, typing in your IP, and appending :27016, 7, 8, 9 in sequence, until you get to about :30 I should also point out that I've had servers jump ports on restart. On Sun, 09 Nov 2008 08:25:58 -0700, Kevin J. Anderson [EMAIL PROTECTED] wrote: My guess is that they want queries to always run through the master server, since its controlling the forks. Could also be for simplified firewall rules for admins, etc. Kevin Saint K. wrote: Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9 Nov 2008 14:14:55 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:27015 0.0.0.0:* - L4D server 4951/srcds_i486 udp 332 0 0.0.0.0:27016 0.0.0.0:* - L4D server 4724/srcds_i486 udp 332 0 0.0.0.0:27017 0.0.0.0:* - L4D server 4856/srcds_i486 udp 664 0 0.0.0.0:27018 0.0.0.0:* - L4D server 4859/srcds_i486 udp0 0 0.0.0.0:27019 0.0.0.0:* - L4D server 5067/srcds_i486 udp0 0 0.0.0.0:27020 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27021 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27022 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27023 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27024 0.0.0.0:* 5067/srcds_i486 udp0428 0.0.0.0:27025 0.0.0.0:* 5033/srcds_i486 udp 1660 0 0.0.0.0:27026 0.0.0.0:* 5033/srcds_i486 udp 5312 0 0.0.0.0:26901 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26902 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26903 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26904 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26905 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26906 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26907 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26908 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26909 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26910 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26911 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26912 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26913 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26914 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26915 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26917 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27005 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27006 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27007 0.0.0.0:* 4856/srcds_i486 The rest of these ports are a mystery to me. I'd expect the 6th server to run off 27020, but nothing replies there. I don't understand what 27020-27026 is used for either. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 1:49 PM To:
Re: [hlds_linux] -fork query issue s
try netstat -nlpt | grep srcds as rcon is tcp not udp if you aren't using the -netconport option, the only ports which should be found are the rcon listening ports. I wonder if it's possible for the udp and tcp ports to end up different, somehow? On Sun, 9 Nov 2008 16:51:36 +0100, Saint K. [EMAIL PROTECTED] wrote: Well, I can see them online in HLSW, but I can't communicate with it terms of sending commands / receiving output. If you try and setup a connection with HLSW, or our query's from the website, the error reads; Connection failed (No connection could be made because the target machine actively refused it. ) It only works on the first of the 6 servers in the fork, at 27015. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:47 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, didn't pick up on the can't query them aspect before. I certainly can with my own. Try running hlsw, typing in your IP, and appending :27016, 7, 8, 9 in sequence, until you get to about :30 I should also point out that I've had servers jump ports on restart. On Sun, 09 Nov 2008 08:25:58 -0700, Kevin J. Anderson [EMAIL PROTECTED] wrote: My guess is that they want queries to always run through the master server, since its controlling the forks. Could also be for simplified firewall rules for admins, etc. Kevin Saint K. wrote: Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9 Nov 2008 14:14:55 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:27015 0.0.0.0:* - L4D server 4951/srcds_i486 udp 332 0 0.0.0.0:27016 0.0.0.0:* - L4D server 4724/srcds_i486 udp 332 0 0.0.0.0:27017 0.0.0.0:* - L4D server 4856/srcds_i486 udp 664 0 0.0.0.0:27018 0.0.0.0:* - L4D server 4859/srcds_i486 udp0 0 0.0.0.0:27019 0.0.0.0:* - L4D server 5067/srcds_i486 udp0 0 0.0.0.0:27020 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27021 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27022 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27023 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27024 0.0.0.0:* 5067/srcds_i486 udp0428 0.0.0.0:27025 0.0.0.0:* 5033/srcds_i486 udp 1660 0 0.0.0.0:27026 0.0.0.0:* 5033/srcds_i486 udp 5312 0 0.0.0.0:26901 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26902 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26903 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26904 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26905 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26906 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26907 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26908 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26909 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26910 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26911 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26912 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26913 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26914 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26915 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26917 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27005 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27006 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27007 0.0.0.0:*
Re: [hlds_linux] -fork query issue s
Hi, There are only 2 TCP ports listening. tcp0 0 0.0.0.0:27015 0.0.0.0:* LISTEN 6107/srcds_i486 tcp0 0 0.0.0.0:90000.0.0.0:* LISTEN 463/srcds_i486 So now the big question rises, how to external query the other servers in the fork, trough 27015? I'm not quite sure btw on what is port 9000 doing. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:56 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s try netstat -nlpt | grep srcds as rcon is tcp not udp if you aren't using the -netconport option, the only ports which should be found are the rcon listening ports. I wonder if it's possible for the udp and tcp ports to end up different, somehow? On Sun, 9 Nov 2008 16:51:36 +0100, Saint K. [EMAIL PROTECTED] wrote: Well, I can see them online in HLSW, but I can't communicate with it terms of sending commands / receiving output. If you try and setup a connection with HLSW, or our query's from the website, the error reads; Connection failed (No connection could be made because the target machine actively refused it. ) It only works on the first of the 6 servers in the fork, at 27015. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:47 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, didn't pick up on the can't query them aspect before. I certainly can with my own. Try running hlsw, typing in your IP, and appending :27016, 7, 8, 9 in sequence, until you get to about :30 I should also point out that I've had servers jump ports on restart. On Sun, 09 Nov 2008 08:25:58 -0700, Kevin J. Anderson [EMAIL PROTECTED] wrote: My guess is that they want queries to always run through the master server, since its controlling the forks. Could also be for simplified firewall rules for admins, etc. Kevin Saint K. wrote: Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9 Nov 2008 14:14:55 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:27015 0.0.0.0:* - L4D server 4951/srcds_i486 udp 332 0 0.0.0.0:27016 0.0.0.0:* - L4D server 4724/srcds_i486 udp 332 0 0.0.0.0:27017 0.0.0.0:* - L4D server 4856/srcds_i486 udp 664 0 0.0.0.0:27018 0.0.0.0:* - L4D server 4859/srcds_i486 udp0 0 0.0.0.0:27019 0.0.0.0:* - L4D server 5067/srcds_i486 udp0 0 0.0.0.0:27020 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27021 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27022 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27023 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27024 0.0.0.0:* 5067/srcds_i486 udp0428 0.0.0.0:27025 0.0.0.0:* 5033/srcds_i486 udp 1660 0 0.0.0.0:27026 0.0.0.0:* 5033/srcds_i486 udp 5312 0 0.0.0.0:26901 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26902 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26903 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26904 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26905 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26906 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26907 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26908 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26909 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26910 0.0.0.0:* 4856/srcds_i486 udp0
Re: [hlds_linux] -fork query issue s
Hi, There are only 2 TCP ports listening. tcp0 0 0.0.0.0:27015 0.0.0.0:* LISTEN 6107/srcds_i486 tcp0 0 0.0.0.0:90000.0.0.0:* LISTEN 463/srcds_i486 So now the big question rises, how to external query the other servers in the fork, trough 27015? I'm not quite sure btw on what is port 9000 doing. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:56 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s try netstat -nlpt | grep srcds as rcon is tcp not udp if you aren't using the -netconport option, the only ports which should be found are the rcon listening ports. I wonder if it's possible for the udp and tcp ports to end up different, somehow? On Sun, 9 Nov 2008 16:51:36 +0100, Saint K. [EMAIL PROTECTED] wrote: Well, I can see them online in HLSW, but I can't communicate with it terms of sending commands / receiving output. If you try and setup a connection with HLSW, or our query's from the website, the error reads; Connection failed (No connection could be made because the target machine actively refused it. ) It only works on the first of the 6 servers in the fork, at 27015. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:47 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, didn't pick up on the can't query them aspect before. I certainly can with my own. Try running hlsw, typing in your IP, and appending :27016, 7, 8, 9 in sequence, until you get to about :30 I should also point out that I've had servers jump ports on restart. On Sun, 09 Nov 2008 08:25:58 -0700, Kevin J. Anderson [EMAIL PROTECTED] wrote: My guess is that they want queries to always run through the master server, since its controlling the forks. Could also be for simplified firewall rules for admins, etc. Kevin Saint K. wrote: Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9 Nov 2008 14:14:55 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:27015 0.0.0.0:* - L4D server 4951/srcds_i486 udp 332 0 0.0.0.0:27016 0.0.0.0:* - L4D server 4724/srcds_i486 udp 332 0 0.0.0.0:27017 0.0.0.0:* - L4D server 4856/srcds_i486 udp 664 0 0.0.0.0:27018 0.0.0.0:* - L4D server 4859/srcds_i486 udp0 0 0.0.0.0:27019 0.0.0.0:* - L4D server 5067/srcds_i486 udp0 0 0.0.0.0:27020 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27021 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27022 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27023 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27024 0.0.0.0:* 5067/srcds_i486 udp0428 0.0.0.0:27025 0.0.0.0:* 5033/srcds_i486 udp 1660 0 0.0.0.0:27026 0.0.0.0:* 5033/srcds_i486 udp 5312 0 0.0.0.0:26901 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26902 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26903 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26904 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26905 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26906 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26907 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26908 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26909 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26910 0.0.0.0:* 4856/srcds_i486 udp0
Re: [hlds_linux] -fork query issue s
Hmm, on my setup I get a tcp port per game instance. I think the port 9000 thing is related to netconport - even though you don't have that enabled, the master server still seems to be listening (you can't do anything with the master server yet, though; apparently you may be able to in future) only other thing I can think of is doing, say, netstat -napt | grep 27016 (numeric, all, show program, tcp) and seeing if something else is nicking the port. I'd expect the server to die in that case, though. There's 3 issues here: - The linux l4d demo server grabs more udp ports than it needs to - When using -fork, you lose the little control over port assignments you had (Control over this is something Chris has said he's looking at) - In your setup, most of the servers don't seem to be listening on the rcon ports at all (I'm surprised they work) Sorry I can't help further On Sun, 9 Nov 2008 17:03:14 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, There are only 2 TCP ports listening. tcp0 0 0.0.0.0:27015 0.0.0.0:* LISTEN 6107/srcds_i486 tcp0 0 0.0.0.0:90000.0.0.0:* LISTEN 463/srcds_i486 So now the big question rises, how to external query the other servers in the fork, trough 27015? I'm not quite sure btw on what is port 9000 doing. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:56 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s try netstat -nlpt | grep srcds as rcon is tcp not udp if you aren't using the -netconport option, the only ports which should be found are the rcon listening ports. I wonder if it's possible for the udp and tcp ports to end up different, somehow? On Sun, 9 Nov 2008 16:51:36 +0100, Saint K. [EMAIL PROTECTED] wrote: Well, I can see them online in HLSW, but I can't communicate with it terms of sending commands / receiving output. If you try and setup a connection with HLSW, or our query's from the website, the error reads; Connection failed (No connection could be made because the target machine actively refused it. ) It only works on the first of the 6 servers in the fork, at 27015. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:47 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, didn't pick up on the can't query them aspect before. I certainly can with my own. Try running hlsw, typing in your IP, and appending :27016, 7, 8, 9 in sequence, until you get to about :30 I should also point out that I've had servers jump ports on restart. On Sun, 09 Nov 2008 08:25:58 -0700, Kevin J. Anderson [EMAIL PROTECTED] wrote: My guess is that they want queries to always run through the master server, since its controlling the forks. Could also be for simplified firewall rules for admins, etc. Kevin Saint K. wrote: Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9 Nov 2008 14:14:55 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:27015 0.0.0.0:* - L4D server 4951/srcds_i486 udp 332 0 0.0.0.0:27016 0.0.0.0:* - L4D server 4724/srcds_i486 udp 332 0 0.0.0.0:27017 0.0.0.0:* - L4D server 4856/srcds_i486 udp 664 0 0.0.0.0:27018 0.0.0.0:* - L4D server 4859/srcds_i486 udp0 0 0.0.0.0:27019 0.0.0.0:* - L4D server 5067/srcds_i486 udp0 0 0.0.0.0:27020 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27021 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27022 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27023
Re: [hlds_linux] -fork query issue s
Hi, On the command it returns no results. Only on a netstat -a I get results on port 27016. udp 664 0 *:27016 *:* May I ask what the command line looks like you boot your servers with? Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 5:14 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, on my setup I get a tcp port per game instance. I think the port 9000 thing is related to netconport - even though you don't have that enabled, the master server still seems to be listening (you can't do anything with the master server yet, though; apparently you may be able to in future) only other thing I can think of is doing, say, netstat -napt | grep 27016 (numeric, all, show program, tcp) and seeing if something else is nicking the port. I'd expect the server to die in that case, though. There's 3 issues here: - The linux l4d demo server grabs more udp ports than it needs to - When using -fork, you lose the little control over port assignments you had (Control over this is something Chris has said he's looking at) - In your setup, most of the servers don't seem to be listening on the rcon ports at all (I'm surprised they work) Sorry I can't help further On Sun, 9 Nov 2008 17:03:14 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, There are only 2 TCP ports listening. tcp0 0 0.0.0.0:27015 0.0.0.0:* LISTEN 6107/srcds_i486 tcp0 0 0.0.0.0:90000.0.0.0:* LISTEN 463/srcds_i486 So now the big question rises, how to external query the other servers in the fork, trough 27015? I'm not quite sure btw on what is port 9000 doing. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:56 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s try netstat -nlpt | grep srcds as rcon is tcp not udp if you aren't using the -netconport option, the only ports which should be found are the rcon listening ports. I wonder if it's possible for the udp and tcp ports to end up different, somehow? On Sun, 9 Nov 2008 16:51:36 +0100, Saint K. [EMAIL PROTECTED] wrote: Well, I can see them online in HLSW, but I can't communicate with it terms of sending commands / receiving output. If you try and setup a connection with HLSW, or our query's from the website, the error reads; Connection failed (No connection could be made because the target machine actively refused it. ) It only works on the first of the 6 servers in the fork, at 27015. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:47 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, didn't pick up on the can't query them aspect before. I certainly can with my own. Try running hlsw, typing in your IP, and appending :27016, 7, 8, 9 in sequence, until you get to about :30 I should also point out that I've had servers jump ports on restart. On Sun, 09 Nov 2008 08:25:58 -0700, Kevin J. Anderson [EMAIL PROTECTED] wrote: My guess is that they want queries to always run through the master server, since its controlling the forks. Could also be for simplified firewall rules for admins, etc. Kevin Saint K. wrote: Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9 Nov 2008 14:14:55 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:27015 0.0.0.0:* - L4D server 4951/srcds_i486 udp 332 0 0.0.0.0:27016 0.0.0.0:* - L4D server 4724/srcds_i486 udp 332 0 0.0.0.0:27017 0.0.0.0:* -
Re: [hlds_linux] -fork query issue s
Why is it binding to all the interfaces? Are you specifying -ip? Sent from my iPhone On 9-Nov-08, at 9:42 AM, Saint K. [EMAIL PROTECTED] wrote: Hi, On the command it returns no results. Only on a netstat -a I get results on port 27016. udp 664 0 *:27016 *:* May I ask what the command line looks like you boot your servers with? Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 5:14 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, on my setup I get a tcp port per game instance. I think the port 9000 thing is related to netconport - even though you don't have that enabled, the master server still seems to be listening (you can't do anything with the master server yet, though; apparently you may be able to in future) only other thing I can think of is doing, say, netstat -napt | grep 27016 (numeric, all, show program, tcp) and seeing if something else is nicking the port. I'd expect the server to die in that case, though. There's 3 issues here: - The linux l4d demo server grabs more udp ports than it needs to - When using -fork, you lose the little control over port assignments you had (Control over this is something Chris has said he's looking at) - In your setup, most of the servers don't seem to be listening on the rcon ports at all (I'm surprised they work) Sorry I can't help further On Sun, 9 Nov 2008 17:03:14 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, There are only 2 TCP ports listening. tcp0 0 0.0.0.0:27015 0.0.0.0:* LISTEN 6107/srcds_i486 tcp0 0 0.0.0.0:90000.0.0.0:* LISTEN 463/srcds_i486 So now the big question rises, how to external query the other servers in the fork, trough 27015? I'm not quite sure btw on what is port 9000 doing. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:56 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s try netstat -nlpt | grep srcds as rcon is tcp not udp if you aren't using the -netconport option, the only ports which should be found are the rcon listening ports. I wonder if it's possible for the udp and tcp ports to end up different, somehow? On Sun, 9 Nov 2008 16:51:36 +0100, Saint K. [EMAIL PROTECTED] wrote: Well, I can see them online in HLSW, but I can't communicate with it terms of sending commands / receiving output. If you try and setup a connection with HLSW, or our query's from the website, the error reads; Connection failed (No connection could be made because the target machine actively refused it. ) It only works on the first of the 6 servers in the fork, at 27015. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:47 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, didn't pick up on the can't query them aspect before. I certainly can with my own. Try running hlsw, typing in your IP, and appending :27016, 7, 8, 9 in sequence, until you get to about :30 I should also point out that I've had servers jump ports on restart. On Sun, 09 Nov 2008 08:25:58 -0700, Kevin J. Anderson [EMAIL PROTECTED] wrote: My guess is that they want queries to always run through the master server, since its controlling the forks. Could also be for simplified firewall rules for admins, etc. Kevin Saint K. wrote: Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9 Nov 2008 14:14:55 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0
Re: [hlds_linux] -fork query issue s
Hi, Adding the +ip parameter fixed it. I can now send query's to the servers and get a response. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jt Sent: Sunday, November 09, 2008 7:20 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Why is it binding to all the interfaces? Are you specifying -ip? Sent from my iPhone On 9-Nov-08, at 9:42 AM, Saint K. [EMAIL PROTECTED] wrote: Hi, On the command it returns no results. Only on a netstat -a I get results on port 27016. udp 664 0 *:27016 *:* May I ask what the command line looks like you boot your servers with? Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 5:14 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, on my setup I get a tcp port per game instance. I think the port 9000 thing is related to netconport - even though you don't have that enabled, the master server still seems to be listening (you can't do anything with the master server yet, though; apparently you may be able to in future) only other thing I can think of is doing, say, netstat -napt | grep 27016 (numeric, all, show program, tcp) and seeing if something else is nicking the port. I'd expect the server to die in that case, though. There's 3 issues here: - The linux l4d demo server grabs more udp ports than it needs to - When using -fork, you lose the little control over port assignments you had (Control over this is something Chris has said he's looking at) - In your setup, most of the servers don't seem to be listening on the rcon ports at all (I'm surprised they work) Sorry I can't help further On Sun, 9 Nov 2008 17:03:14 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, There are only 2 TCP ports listening. tcp0 0 0.0.0.0:27015 0.0.0.0:* LISTEN 6107/srcds_i486 tcp0 0 0.0.0.0:90000.0.0.0:* LISTEN 463/srcds_i486 So now the big question rises, how to external query the other servers in the fork, trough 27015? I'm not quite sure btw on what is port 9000 doing. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:56 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s try netstat -nlpt | grep srcds as rcon is tcp not udp if you aren't using the -netconport option, the only ports which should be found are the rcon listening ports. I wonder if it's possible for the udp and tcp ports to end up different, somehow? On Sun, 9 Nov 2008 16:51:36 +0100, Saint K. [EMAIL PROTECTED] wrote: Well, I can see them online in HLSW, but I can't communicate with it terms of sending commands / receiving output. If you try and setup a connection with HLSW, or our query's from the website, the error reads; Connection failed (No connection could be made because the target machine actively refused it. ) It only works on the first of the 6 servers in the fork, at 27015. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:47 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, didn't pick up on the can't query them aspect before. I certainly can with my own. Try running hlsw, typing in your IP, and appending :27016, 7, 8, 9 in sequence, until you get to about :30 I should also point out that I've had servers jump ports on restart. On Sun, 09 Nov 2008 08:25:58 -0700, Kevin J. Anderson [EMAIL PROTECTED] wrote: My guess is that they want queries to always run through the master server, since its controlling the forks. Could also be for simplified firewall rules for admins, etc. Kevin Saint K. wrote: Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9
Re: [hlds_linux] Matchmaking suggestion
I think, we need only serwer browser and something like sv_deny_lobby_connect, so we can make our public servers with no password. I bet, there will be no enough servers for players after premiere because of lobby idea and passworded serwers. - Original Message - From: Raphael Hehl [EMAIL PROTECTED] To: 'Half-Life dedicated Linux server mailing list' hlds_linux@list.valvesoftware.com Sent: Sunday, November 09, 2008 8:51 AM Subject: [hlds_linux] Matchmaking suggestion Matchmaking is good, but one thing requires a change, the automatic server search should get replaced with a server browser. And additional it should be possible to connect to a own server who get automatic or manual reserverd by the server owner if he want to play. Then it makes sense, to host a server. -Raphael ___ 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
Re: [hlds_linux] -fork query issue's
What's your cmdline args? Sent from my iPhone On 9-Nov-08, at 5:39 AM, Saint K. [EMAIL PROTECTED] wrote: Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue's Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9 Nov 2008 14:14:55 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:27015 0.0.0.0:* - L4D server 4951/srcds_i486 udp 332 0 0.0.0.0:27016 0.0.0.0:* - L4D server 4724/srcds_i486 udp 332 0 0.0.0.0:27017 0.0.0.0:* - L4D server 4856/srcds_i486 udp 664 0 0.0.0.0:27018 0.0.0.0:* - L4D server 4859/srcds_i486 udp0 0 0.0.0.0:27019 0.0.0.0:* - L4D server 5067/srcds_i486 udp0 0 0.0.0.0:27020 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27021 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27022 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27023 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27024 0.0.0.0:* 5067/srcds_i486 udp0428 0.0.0.0:27025 0.0.0.0:* 5033/srcds_i486 udp 1660 0 0.0.0.0:27026 0.0.0.0:* 5033/srcds_i486 udp 5312 0 0.0.0.0:26901 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26902 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26903 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26904 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26905 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26906 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26907 0.0.0.0:* 4951/srcds_i486 udp 2656 0 0.0.0.0:26908 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26909 0.0.0.0:* 4724/srcds_i486 udp 2656 0 0.0.0.0:26910 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26911 0.0.0.0:* 5067/srcds_i486 udp 2988 0 0.0.0.0:26912 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:26913 0.0.0.0:* 4859/srcds_i486 udp 2656 0 0.0.0.0:26914 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:26915 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:26917 0.0.0.0:* 4856/srcds_i486 udp0 0 0.0.0.0:27005 0.0.0.0:* 4951/srcds_i486 udp0 0 0.0.0.0:27006 0.0.0.0:* 4724/srcds_i486 udp0 0 0.0.0.0:27007 0.0.0.0:* 4856/srcds_i486 The rest of these ports are a mystery to me. I'd expect the 6th server to run off 27020, but nothing replies there. I don't understand what 27020-27026 is used for either. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 1:49 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue's If you run netstat -nlpu | grep srcds: (numeric, listening, show programs, UDP) You should see all the UDP ports your 7 srcds processes are listening on (6 servers and the master). Each will probably be listening on 3 ports. One of them will be the actual game port. On Sun, 9 Nov 2008 13:12:50 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, On our Linux machine we now use the -fork option to spawn the L4D servers. The problem here is we can externally only query port 27015. The servers running on 27016, 27017, 27018 and 27019 don't respond on external query's. The 6th server from the -fork option spawns at a random port, not 27020. I can't find which port it runs off, although the CPU load indicates the 6th server is also being used. Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit:
Re: [hlds_linux] The 1000fps problem
xLnT schrieb: Hi. I am really bothered, what is it that makes hlds NOT to use max resources from the server? A gameserver reaches 1000fps sometimes.. but mostly its about 970-985fps. Here's a paste from a server. http://paste.prco23.org/32971 This is a single server on a Debian Lenny setup, Dual Quadcore 2.5Ghz, 8GB RAM, 73GB SAS 15krpm. Anyone got their server to run 1000fps stable.. with few drops? Regards. You should test your server with 10 players. I think no one then reaches stable 950FPS. - Marcel ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable
I fixed it on my Debian Etch AMD64 server. I used this package: http://packages.debian.org/lenny/libc6-i386 wget http://ftp.nl.debian.org/debian/pool/main/g/glibc/libc6-i386_2.7-15_amd64.deb ar x libc6-i386_2.7-15_amd64.deb tar xvzf data.tar.gz Then LD_PRELOAD the lib like this: export LD_PRELOAD=/home/l4d/tmp/lib32/libc-2.7.so (ofcourse your path to that file) Run that before you start your server. It seems to run fine :) On Fri, Nov 7, 2008 at 9:41 PM, Jordy van Wolferen [EMAIL PROTECTED] wrote: If you do find a way to make a deb, let us know, so we can use it too :) On Fri, 2008-11-07 at 11:37 -0800, J T wrote: Debian Etch is the latest stable. The main reason why it has libc6 2.3 is because 2.3 still supports kernel 2.4, in the next release of lenny it will ship with libc6 2.7 which should correct the problem. If you have the choice of installing a new OS, choose ubuntu, since they seem to have newer version of most packages. Debian is sometimes doesn't include newer packages. I'm looking at possibly trying to get glibc into a .dpkg so I don't have to run debootstrap. Cheers. On Fri, Nov 7, 2008 at 11:22 AM, [EMAIL PROTECTED] wrote: No and yes... it's the most recent stable release of debian. -Original Message- From: [EMAIL PROTECTED] [mailto:hlds_linux- [EMAIL PROTECTED] On Behalf Of CNU Sent: 07 November 2008 19:20 To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable Are everyone running Debian Etch here or something? Isn't it like...ancient? -- CNU ___ 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
Re: [hlds_linux] The 1000fps problem
At 05:52 AM 11/9/2008, xLnT wrote: Hi. I am really bothered, what is it that makes hlds NOT to use max resources from the server? A gameserver reaches 1000fps sometimes.. but mostly its about 970-985fps. You're not going to able be able to run it that high all the time.. Interrupt latency, scheduler latency, and a bunch of other things cause the drops. G. Monk Stanley gary at summit-servers dot com | gary at DragonflyBSD dot org http://leaf.dragonflybsd.org/~gary There currently are 7 different ways to get time from a computer. All of them can't agree on how long a second is supposed to be -Me ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] The 1000fps problem
At 05:52 AM 11/9/2008, xLnT wrote: Hi. I am really bothered, what is it that makes hlds NOT to use max resources from the server? A gameserver reaches 1000fps sometimes.. but mostly its about 970-985fps. You're not going to able be able to run it that high all the time.. Interrupt latency, scheduler latency, and a bunch of other things cause the drops. G. Monk Stanley gary at summit-servers dot com | gary at DragonflyBSD dot org http://leaf.dragonflybsd.org/~gary There currently are 7 different ways to get time from a computer. All of them can't agree on how long a second is supposed to be -Me ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable
Never mind :) Relised i forgot to extract the .deb file, however still doesnt work running http://ftp.de.debian.org/debian/pool/main/g/glibc/libc6_2.7-15_i386.deb Just segmentation faults on start up, Anyideas? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, 10 November 2008 4:20 PM To: 'Half-Life dedicated Linux server mailing list' Subject: Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable Few questions for you, a) how do you remove the LD_PRELOAD paramater? b) output of my console now Could not locate steam binary:./steam, ignoring. ERROR: ld.so: object '/usr/games/l4d/temp/libc6_2.7-15_i386.deb' from LD_PRELOAD cannot be preloaded: ignored. Failed to open bin/dedicated_i486.so (/lib/tls/libc.so.6: version `GLIBC_2.4' not found (required by bin/dedicated_i486.so)) Add -debug to the ./srcds_run command line to generate a debug.log to help with solving this problem ERROR: ld.so: object '/usr/games/l4d/temp/libc6_2.7-15_i386.deb' from LD_PRELOAD cannot be preloaded: ignored. Mon Nov 10 16:18:51 EST 2008: Server restart in 10 seconds ERROR: ld.so: object '/usr/games/l4d/temp/libc6_2.7-15_i386.deb' from LD_PRELOAD cannot be preloaded: ignored. Dual Core2 Quad Box running debian Thanks in advance -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jordy van Wolferen Sent: Monday, 10 November 2008 12:14 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable I fixed it on my Debian Etch AMD64 server. I used this package: http://packages.debian.org/lenny/libc6-i386 wget http://ftp.nl.debian.org/debian/pool/main/g/glibc/libc6-i386_2.7-15_amd64.de b ar x libc6-i386_2.7-15_amd64.deb tar xvzf data.tar.gz Then LD_PRELOAD the lib like this: export LD_PRELOAD=/home/l4d/tmp/lib32/libc-2.7.so (ofcourse your path to that file) Run that before you start your server. It seems to run fine :) On Fri, Nov 7, 2008 at 9:41 PM, Jordy van Wolferen [EMAIL PROTECTED] wrote: If you do find a way to make a deb, let us know, so we can use it too :) On Fri, 2008-11-07 at 11:37 -0800, J T wrote: Debian Etch is the latest stable. The main reason why it has libc6 2.3 is because 2.3 still supports kernel 2.4, in the next release of lenny it will ship with libc6 2.7 which should correct the problem. If you have the choice of installing a new OS, choose ubuntu, since they seem to have newer version of most packages. Debian is sometimes doesn't include newer packages. I'm looking at possibly trying to get glibc into a .dpkg so I don't have to run debootstrap. Cheers. On Fri, Nov 7, 2008 at 11:22 AM, [EMAIL PROTECTED] wrote: No and yes... it's the most recent stable release of debian. -Original Message- From: [EMAIL PROTECTED] [mailto:hlds_linux- [EMAIL PROTECTED] On Behalf Of CNU Sent: 07 November 2008 19:20 To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable Are everyone running Debian Etch here or something? Isn't it like...ancient? -- CNU ___ 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 ___ 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
Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable
Did you keep the ia32-libs installed? You still need them On Mon, Nov 10, 2008 at 6:40 AM, [EMAIL PROTECTED] wrote: Never mind :) Relised i forgot to extract the .deb file, however still doesnt work running http://ftp.de.debian.org/debian/pool/main/g/glibc/libc6_2.7-15_i386.deb Just segmentation faults on start up, Anyideas? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, 10 November 2008 4:20 PM To: 'Half-Life dedicated Linux server mailing list' Subject: Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable Few questions for you, a) how do you remove the LD_PRELOAD paramater? b) output of my console now Could not locate steam binary:./steam, ignoring. ERROR: ld.so: object '/usr/games/l4d/temp/libc6_2.7-15_i386.deb' from LD_PRELOAD cannot be preloaded: ignored. Failed to open bin/dedicated_i486.so (/lib/tls/libc.so.6: version `GLIBC_2.4' not found (required by bin/dedicated_i486.so)) Add -debug to the ./srcds_run command line to generate a debug.log to help with solving this problem ERROR: ld.so: object '/usr/games/l4d/temp/libc6_2.7-15_i386.deb' from LD_PRELOAD cannot be preloaded: ignored. Mon Nov 10 16:18:51 EST 2008: Server restart in 10 seconds ERROR: ld.so: object '/usr/games/l4d/temp/libc6_2.7-15_i386.deb' from LD_PRELOAD cannot be preloaded: ignored. Dual Core2 Quad Box running debian Thanks in advance -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jordy van Wolferen Sent: Monday, 10 November 2008 12:14 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable I fixed it on my Debian Etch AMD64 server. I used this package: http://packages.debian.org/lenny/libc6-i386 wget http://ftp.nl.debian.org/debian/pool/main/g/glibc/libc6-i386_2.7-15_amd64.de b ar x libc6-i386_2.7-15_amd64.deb tar xvzf data.tar.gz Then LD_PRELOAD the lib like this: export LD_PRELOAD=/home/l4d/tmp/lib32/libc-2.7.so (ofcourse your path to that file) Run that before you start your server. It seems to run fine :) On Fri, Nov 7, 2008 at 9:41 PM, Jordy van Wolferen [EMAIL PROTECTED] wrote: If you do find a way to make a deb, let us know, so we can use it too :) On Fri, 2008-11-07 at 11:37 -0800, J T wrote: Debian Etch is the latest stable. The main reason why it has libc6 2.3 is because 2.3 still supports kernel 2.4, in the next release of lenny it will ship with libc6 2.7 which should correct the problem. If you have the choice of installing a new OS, choose ubuntu, since they seem to have newer version of most packages. Debian is sometimes doesn't include newer packages. I'm looking at possibly trying to get glibc into a .dpkg so I don't have to run debootstrap. Cheers. On Fri, Nov 7, 2008 at 11:22 AM, [EMAIL PROTECTED] wrote: No and yes... it's the most recent stable release of debian. -Original Message- From: [EMAIL PROTECTED] [mailto:hlds_linux- [EMAIL PROTECTED] On Behalf Of CNU Sent: 07 November 2008 19:20 To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable Are everyone running Debian Etch here or something? Isn't it like...ancient? -- CNU ___ 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 ___ 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
Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable
Its a 32bit intel box, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jordy van Wolferen Sent: Monday, 10 November 2008 5:17 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable Did you keep the ia32-libs installed? You still need them On Mon, Nov 10, 2008 at 6:40 AM, [EMAIL PROTECTED] wrote: Never mind :) Relised i forgot to extract the .deb file, however still doesnt work running http://ftp.de.debian.org/debian/pool/main/g/glibc/libc6_2.7-15_i386.deb Just segmentation faults on start up, Anyideas? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, 10 November 2008 4:20 PM To: 'Half-Life dedicated Linux server mailing list' Subject: Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable Few questions for you, a) how do you remove the LD_PRELOAD paramater? b) output of my console now Could not locate steam binary:./steam, ignoring. ERROR: ld.so: object '/usr/games/l4d/temp/libc6_2.7-15_i386.deb' from LD_PRELOAD cannot be preloaded: ignored. Failed to open bin/dedicated_i486.so (/lib/tls/libc.so.6: version `GLIBC_2.4' not found (required by bin/dedicated_i486.so)) Add -debug to the ./srcds_run command line to generate a debug.log to help with solving this problem ERROR: ld.so: object '/usr/games/l4d/temp/libc6_2.7-15_i386.deb' from LD_PRELOAD cannot be preloaded: ignored. Mon Nov 10 16:18:51 EST 2008: Server restart in 10 seconds ERROR: ld.so: object '/usr/games/l4d/temp/libc6_2.7-15_i386.deb' from LD_PRELOAD cannot be preloaded: ignored. Dual Core2 Quad Box running debian Thanks in advance -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jordy van Wolferen Sent: Monday, 10 November 2008 12:14 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable I fixed it on my Debian Etch AMD64 server. I used this package: http://packages.debian.org/lenny/libc6-i386 wget http://ftp.nl.debian.org/debian/pool/main/g/glibc/libc6-i386_2.7-15_amd64.de b ar x libc6-i386_2.7-15_amd64.deb tar xvzf data.tar.gz Then LD_PRELOAD the lib like this: export LD_PRELOAD=/home/l4d/tmp/lib32/libc-2.7.so (ofcourse your path to that file) Run that before you start your server. It seems to run fine :) On Fri, Nov 7, 2008 at 9:41 PM, Jordy van Wolferen [EMAIL PROTECTED] wrote: If you do find a way to make a deb, let us know, so we can use it too :) On Fri, 2008-11-07 at 11:37 -0800, J T wrote: Debian Etch is the latest stable. The main reason why it has libc6 2.3 is because 2.3 still supports kernel 2.4, in the next release of lenny it will ship with libc6 2.7 which should correct the problem. If you have the choice of installing a new OS, choose ubuntu, since they seem to have newer version of most packages. Debian is sometimes doesn't include newer packages. I'm looking at possibly trying to get glibc into a .dpkg so I don't have to run debootstrap. Cheers. On Fri, Nov 7, 2008 at 11:22 AM, [EMAIL PROTECTED] wrote: No and yes... it's the most recent stable release of debian. -Original Message- From: [EMAIL PROTECTED] [mailto:hlds_linux- [EMAIL PROTECTED] On Behalf Of CNU Sent: 07 November 2008 19:20 To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable Are everyone running Debian Etch here or something? Isn't it like...ancient? -- CNU ___ 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 ___ 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 ___ To unsubscribe, edit
Re: [hlds_linux] -fork query issue s
Hi, On the command it returns no results. Only on a netstat -a I get results on port 27016. udp 664 0 *:27016 *:* May I ask what the command line looks like you boot your servers with? Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 5:14 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, on my setup I get a tcp port per game instance. I think the port 9000 thing is related to netconport - even though you don't have that enabled, the master server still seems to be listening (you can't do anything with the master server yet, though; apparently you may be able to in future) only other thing I can think of is doing, say, netstat -napt | grep 27016 (numeric, all, show program, tcp) and seeing if something else is nicking the port. I'd expect the server to die in that case, though. There's 3 issues here: - The linux l4d demo server grabs more udp ports than it needs to - When using -fork, you lose the little control over port assignments you had (Control over this is something Chris has said he's looking at) - In your setup, most of the servers don't seem to be listening on the rcon ports at all (I'm surprised they work) Sorry I can't help further On Sun, 9 Nov 2008 17:03:14 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, There are only 2 TCP ports listening. tcp0 0 0.0.0.0:27015 0.0.0.0:* LISTEN 6107/srcds_i486 tcp0 0 0.0.0.0:90000.0.0.0:* LISTEN 463/srcds_i486 So now the big question rises, how to external query the other servers in the fork, trough 27015? I'm not quite sure btw on what is port 9000 doing. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:56 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s try netstat -nlpt | grep srcds as rcon is tcp not udp if you aren't using the -netconport option, the only ports which should be found are the rcon listening ports. I wonder if it's possible for the udp and tcp ports to end up different, somehow? On Sun, 9 Nov 2008 16:51:36 +0100, Saint K. [EMAIL PROTECTED] wrote: Well, I can see them online in HLSW, but I can't communicate with it terms of sending commands / receiving output. If you try and setup a connection with HLSW, or our query's from the website, the error reads; Connection failed (No connection could be made because the target machine actively refused it. ) It only works on the first of the 6 servers in the fork, at 27015. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:47 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, didn't pick up on the can't query them aspect before. I certainly can with my own. Try running hlsw, typing in your IP, and appending :27016, 7, 8, 9 in sequence, until you get to about :30 I should also point out that I've had servers jump ports on restart. On Sun, 09 Nov 2008 08:25:58 -0700, Kevin J. Anderson [EMAIL PROTECTED] wrote: My guess is that they want queries to always run through the master server, since its controlling the forks. Could also be for simplified firewall rules for admins, etc. Kevin Saint K. wrote: Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9 Nov 2008 14:14:55 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, What can we make of this? udp0 0 0.0.0.0:27008 0.0.0.0:* 4859/srcds_i486 udp0 0 0.0.0.0:27009 0.0.0.0:* 5067/srcds_i486 udp0 0 0.0.0.0:27010 0.0.0.0:* 5033/srcds_i486 udp0 0 0.0.0.0:27015 0.0.0.0:* - L4D server 4951/srcds_i486 udp 332 0 0.0.0.0:27016 0.0.0.0:* - L4D server 4724/srcds_i486 udp 332 0 0.0.0.0:27017 0.0.0.0:* -
Re: [hlds_linux] -fork query issue
Either a bug or sloppy coding Sent from my iPhone On 9-Nov-08, at 11:09 AM, Saint K. [EMAIL PROTECTED] wrote: Hi, Adding the +ip parameter fixed it. I can now send query's to the servers and get a response. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jt Sent: Sunday, November 09, 2008 7:20 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Why is it binding to all the interfaces? Are you specifying -ip? Sent from my iPhone On 9-Nov-08, at 9:42 AM, Saint K. [EMAIL PROTECTED] wrote: Hi, On the command it returns no results. Only on a netstat -a I get results on port 27016. udp 664 0 *:27016 *:* May I ask what the command line looks like you boot your servers with? Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 5:14 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, on my setup I get a tcp port per game instance. I think the port 9000 thing is related to netconport - even though you don't have that enabled, the master server still seems to be listening (you can't do anything with the master server yet, though; apparently you may be able to in future) only other thing I can think of is doing, say, netstat -napt | grep 27016 (numeric, all, show program, tcp) and seeing if something else is nicking the port. I'd expect the server to die in that case, though. There's 3 issues here: - The linux l4d demo server grabs more udp ports than it needs to - When using -fork, you lose the little control over port assignments you had (Control over this is something Chris has said he's looking at) - In your setup, most of the servers don't seem to be listening on the rcon ports at all (I'm surprised they work) Sorry I can't help further On Sun, 9 Nov 2008 17:03:14 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, There are only 2 TCP ports listening. tcp0 0 0.0.0.0:27015 0.0.0.0:* LISTEN 6107/srcds_i486 tcp0 0 0.0.0.0:90000.0.0.0:* LISTEN 463/srcds_i486 So now the big question rises, how to external query the other servers in the fork, trough 27015? I'm not quite sure btw on what is port 9000 doing. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:56 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s try netstat -nlpt | grep srcds as rcon is tcp not udp if you aren't using the -netconport option, the only ports which should be found are the rcon listening ports. I wonder if it's possible for the udp and tcp ports to end up different, somehow? On Sun, 9 Nov 2008 16:51:36 +0100, Saint K. [EMAIL PROTECTED] wrote: Well, I can see them online in HLSW, but I can't communicate with it terms of sending commands / receiving output. If you try and setup a connection with HLSW, or our query's from the website, the error reads; Connection failed (No connection could be made because the target machine actively refused it. ) It only works on the first of the 6 servers in the fork, at 27015. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:47 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, didn't pick up on the can't query them aspect before. I certainly can with my own. Try running hlsw, typing in your IP, and appending :27016, 7, 8, 9 in sequence, until you get to about :30 I should also point out that I've had servers jump ports on restart. On Sun, 09 Nov 2008 08:25:58 -0700, Kevin J. Anderson [EMAIL PROTECTED] wrote: My guess is that they want queries to always run through the master server, since its controlling the forks. Could also be for simplified firewall rules for admins, etc. Kevin Saint K. wrote: Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some
Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable
Few questions for you, a) how do you remove the LD_PRELOAD paramater? b) output of my console now Could not locate steam binary:./steam, ignoring. ERROR: ld.so: object '/usr/games/l4d/temp/libc6_2.7-15_i386.deb' from LD_PRELOAD cannot be preloaded: ignored. Failed to open bin/dedicated_i486.so (/lib/tls/libc.so.6: version `GLIBC_2.4' not found (required by bin/dedicated_i486.so)) Add -debug to the ./srcds_run command line to generate a debug.log to help with solving this problem ERROR: ld.so: object '/usr/games/l4d/temp/libc6_2.7-15_i386.deb' from LD_PRELOAD cannot be preloaded: ignored. Mon Nov 10 16:18:51 EST 2008: Server restart in 10 seconds ERROR: ld.so: object '/usr/games/l4d/temp/libc6_2.7-15_i386.deb' from LD_PRELOAD cannot be preloaded: ignored. Dual Core2 Quad Box running debian Thanks in advance -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jordy van Wolferen Sent: Monday, 10 November 2008 12:14 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable I fixed it on my Debian Etch AMD64 server. I used this package: http://packages.debian.org/lenny/libc6-i386 wget http://ftp.nl.debian.org/debian/pool/main/g/glibc/libc6-i386_2.7-15_amd64.de b ar x libc6-i386_2.7-15_amd64.deb tar xvzf data.tar.gz Then LD_PRELOAD the lib like this: export LD_PRELOAD=/home/l4d/tmp/lib32/libc-2.7.so (ofcourse your path to that file) Run that before you start your server. It seems to run fine :) On Fri, Nov 7, 2008 at 9:41 PM, Jordy van Wolferen [EMAIL PROTECTED] wrote: If you do find a way to make a deb, let us know, so we can use it too :) On Fri, 2008-11-07 at 11:37 -0800, J T wrote: Debian Etch is the latest stable. The main reason why it has libc6 2.3 is because 2.3 still supports kernel 2.4, in the next release of lenny it will ship with libc6 2.7 which should correct the problem. If you have the choice of installing a new OS, choose ubuntu, since they seem to have newer version of most packages. Debian is sometimes doesn't include newer packages. I'm looking at possibly trying to get glibc into a .dpkg so I don't have to run debootstrap. Cheers. On Fri, Nov 7, 2008 at 11:22 AM, [EMAIL PROTECTED] wrote: No and yes... it's the most recent stable release of debian. -Original Message- From: [EMAIL PROTECTED] [mailto:hlds_linux- [EMAIL PROTECTED] On Behalf Of CNU Sent: 07 November 2008 19:20 To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] [hlds] Left 4 Dead Demo Dedicated Server filesavailable Are everyone running Debian Etch here or something? Isn't it like...ancient? -- CNU ___ 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 ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] -fork query issue s
Hi, Adding the +ip parameter fixed it. I can now send query's to the servers and get a response. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jt Sent: Sunday, November 09, 2008 7:20 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Why is it binding to all the interfaces? Are you specifying -ip? Sent from my iPhone On 9-Nov-08, at 9:42 AM, Saint K. [EMAIL PROTECTED] wrote: Hi, On the command it returns no results. Only on a netstat -a I get results on port 27016. udp 664 0 *:27016 *:* May I ask what the command line looks like you boot your servers with? Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 5:14 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, on my setup I get a tcp port per game instance. I think the port 9000 thing is related to netconport - even though you don't have that enabled, the master server still seems to be listening (you can't do anything with the master server yet, though; apparently you may be able to in future) only other thing I can think of is doing, say, netstat -napt | grep 27016 (numeric, all, show program, tcp) and seeing if something else is nicking the port. I'd expect the server to die in that case, though. There's 3 issues here: - The linux l4d demo server grabs more udp ports than it needs to - When using -fork, you lose the little control over port assignments you had (Control over this is something Chris has said he's looking at) - In your setup, most of the servers don't seem to be listening on the rcon ports at all (I'm surprised they work) Sorry I can't help further On Sun, 9 Nov 2008 17:03:14 +0100, Saint K. [EMAIL PROTECTED] wrote: Hi, There are only 2 TCP ports listening. tcp0 0 0.0.0.0:27015 0.0.0.0:* LISTEN 6107/srcds_i486 tcp0 0 0.0.0.0:90000.0.0.0:* LISTEN 463/srcds_i486 So now the big question rises, how to external query the other servers in the fork, trough 27015? I'm not quite sure btw on what is port 9000 doing. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:56 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s try netstat -nlpt | grep srcds as rcon is tcp not udp if you aren't using the -netconport option, the only ports which should be found are the rcon listening ports. I wonder if it's possible for the udp and tcp ports to end up different, somehow? On Sun, 9 Nov 2008 16:51:36 +0100, Saint K. [EMAIL PROTECTED] wrote: Well, I can see them online in HLSW, but I can't communicate with it terms of sending commands / receiving output. If you try and setup a connection with HLSW, or our query's from the website, the error reads; Connection failed (No connection could be made because the target machine actively refused it. ) It only works on the first of the 6 servers in the fork, at 27015. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 4:47 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Hmm, didn't pick up on the can't query them aspect before. I certainly can with my own. Try running hlsw, typing in your IP, and appending :27016, 7, 8, 9 in sequence, until you get to about :30 I should also point out that I've had servers jump ports on restart. On Sun, 09 Nov 2008 08:25:58 -0700, Kevin J. Anderson [EMAIL PROTECTED] wrote: My guess is that they want queries to always run through the master server, since its controlling the forks. Could also be for simplified firewall rules for admins, etc. Kevin Saint K. wrote: Hi, Good guess! It is indeed on 27025! Thanks. It still doesn't explain thought why we can't query those other servers at the gameports their running on. Maybe VALVe can shed some light on how this thing works. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Sent: Sunday, November 09, 2008 2:35 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] -fork query issue s Eliminating all the entries relating to the 5 servers you know about, I think your 6th is listening on 27025 or 27026. I'm not sure what's going on with the extra ports - it may be related to htlv going by errors I get trying to start individual servers - but it's the reason why some people aren't having much luck forking more than about 5 servers at a time On Sun, 9
