[xdimension]

Hi,
We have recently added the xRedirect plugin to 5 of our CZ servers,

1. Assault 1 - System 1
2. Dust2 1- System 1
3. Assault 2 - System 2
4. Assault 3 - System 2
5. Assault 4 - System 2

The redirect plugin works beautifully. However, after 5-6 hours Assault servers 2 and 3 start having a hissy fit and will only show them selves when the /server command is used, basicly, redirecting to itself. While at the same time, all the other servers will happily redirect to the 2 servers having problems.

I checked out the error logs, and came across this in the AMX logs;

AMXModX

L 08/23/2009 - 080:48: -------- Mapchange to cs_assault -------- L 08/23/2009 - 080:48: [xredirect.amxx] Loaded server Assault Server #1 (85.8.130.158:27015) L 08/23/2009 - 080:48: [xredirect.amxx] Loaded server Assault Server #2 (85.8.132.200:27025) L 08/23/2009 - 080:48: [xredirect.amxx] Loaded server Assault Server #3 (85.8.132.200:27035) L 08/23/2009 - 080:48: [xredirect.amxx] Loaded server Assault Server #4 (85.8.132.200:27045) L 08/23/2009 - 080:48: [xredirect.amxx] Loaded server Dust2 Server #1 (85.8.130.158:27025) L 08/23/2009 - 09:21:26: -------- Mapchange to cs_assault -------- L 08/23/2009 - 09:21:26: [xredirect.amxx] Loaded server Assault Server #1 (85.8.130.158:27015) L 08/23/2009 - 09:21:26: [xredirect.amxx] Loaded server Assault Server #2 (85.8.132.200:27025) L 08/23/2009 - 09:21:26: [xredirect.amxx] Loaded server Assault Server #3 (85.8.132.200:27035) L 08/23/2009 - 09:21:26: [xredirect.amxx] Loaded server Assault Server #4 (85.8.132.200:27045) L 08/23/2009 - 09:21:26: [xredirect.amxx] Loaded server Dust2 Server #1 (85.8.130.158:27025) L 08/23/2009 - 10:11:40: -------- Mapchange to cs_assault -------- L 08/23/2009 - 10:11:40: [xredirect.amxx] Loaded server Assault Server #1 (85.8.130.158:27015) L 08/23/2009 - 10:11:40: [xredirect.amxx] Loaded server Assault Server #2 (85.8.132.200:27025) L 08/23/2009 - 10:11:40: [xredirect.amxx] Loaded server Assault Server #3 (85.8.132.200:27035) L 08/23/2009 - 10:11:40: [xredirect.amxx] Loaded server Assault Server #4 (85.8.132.200:27045) L 08/23/2009 - 10:11:40: [xredirect.amxx] Loaded server Dust2 Server #1 (85.8.130.158:27025) L 08/23/2009 - 10:11:59: [xredirect.amxx] ERROR: Socket error 1 on socket for server 0 L 08/23/2009 - 10:11:59: [xredirect.amxx] ERROR: Socket error 1 on socket for server 2 L 08/23/2009 - 10:11:59: [xredirect.amxx] ERROR: Socket error 1 on socket for server 3 L 08/23/2009 - 10:11:59: [xredirect.amxx] ERROR: Socket error 1 on socket for server 4 L 08/23/2009 - 10:12:19: [xredirect.amxx] ERROR: Socket error 1 on socket for server 0 L 08/23/2009 - 10:12:19: [xredirect.amxx] ERROR: Socket error 1 on socket for server 2 L 08/23/2009 - 10:12:19: [xredirect.amxx] ERROR: Socket error 1 on socket for server 3 L 08/23/2009 - 10:12:19: [xredirect.amxx] ERROR: Socket error 1 on socket for server 4 L 08/23/2009 - 10:129: [xredirect.amxx] ERROR: Socket error 1 on socket for server 0 L 08/23/2009 - 10:129: [xredirect.amxx] ERROR: Socket error 1 on socket for server 2 L 08/23/2009 - 10:129: [xredirect.amxx] ERROR: Socket error 1 on socket for server 3 L 08/23/2009 - 10:129: [xredirect.amxx] ERROR: Socket error 1 on socket for server 4

Serverlist.ini

[Assault Server #1] address=85.8.130.158 port=27015 cmdbackup=5 [Assault Server #2] address=85.8.132.200 port=27025 cmdbackup=5 [Assault Server #3] address=85.8.132.200 port=27035 cmdbackup=5 [Assault Server #4] address=85.8.132.200 port=27045 cmdbackup=5 [Dust2 Server #1] address=85.8.130.158 port=27025 cmdbackup=5 noauto=1

I cant get my head around why it works for a few hours on all servers, then a socket error appears on 2 of the servers (while the 3rd server on same system is fine).

All of the servers have the exact same configs (aside from settings that need to be different such as IP, Port, Hostname etc etc), and same plugins running.

AMXModX Plugins

11:56:52 Currently loaded plugins: name version author file status [ 1] Advanced Bans 0.8 Exolent advanced_bans.a running [ 2] Admin Base 1.8.1.3746 AMXX Dev Team admin.amxx running [ 3] Admin Commands 1.8.1.3746 AMXX Dev Team admincmd.amxx running [ 4] Admin Help 1.8.1.3746 AMXX Dev Team adminhelp.amxx running [ 5] Slots Reservation 1.8.1.3746 AMXX Dev Team adminslots.amxx running [ 6] Multi-Lingual System 1.8.1.3746 AMXX Dev Team multilingual.am running [ 7] Menus Front-End 1.8.1.3746 AMXX Dev Team menufront.amxx running [ 8] Commands Menu 1.8.1.3746 AMXX Dev Team cmdmenu.amxx running [ 9] Players Menu 1.8.1.3746 AMXX Dev Team plmenu.amxx running [ 10] Plugin Menu 1.8.1.3746 AMXX Dev Team pluginmenu.amxx running [ 11] Admin Chat 1.8.1.3746 AMXX Dev Team adminchat.amxx running [ 12] Anti Flood 1.8.1.3746 AMXX Dev Team antiflood.amxx running [ 13] Info. Messages 1.8.1.3746 AMXX Dev Team imessage.amxx running [ 14] Admin Votes 1.8.1.3746 AMXX Dev Team adminvote.amxx running 11:56:52 [ 15] TimeLeft 1.8.1.3746 AMXX Dev Team timeleft.amxx running [ 16] Pause Plugins 1.8.1.3746 AMXX Dev Team pausecfg.amxx running [ 17] Stats Configuration 1.8.1.3746 AMXX Dev Team statscfg.amxx running [ 18] StatsX 1.8.1.3746 AMXX Dev Team statsx.amxx running [ 19] High Ping Kicker 1.2 Teh Lemon hpk.amxx running [ 20] Map Spawns Editor 1.0.16 iG_os Map_Spawns_Edit running [ 21] AWP/AUTO Limit (Team/W 1.52 SuicideDog/MattO sniperlimit.amx running [ 22] AMX Super 4.2 Bmann_420 amx_super.amxx running [ 23] AMX_Super Menu 0.8.1 Yami Kaitou amx_super_menu. running [ 24] ObjectMover 1.2 ArtemusOD objectmover.amx running [ 25] xREDIRECT 1.0.3.2 x0R xredirect.amxx running 25 plugins, 25 running

MetaMod Plugins

11:568 meta list 11:568 Currently loaded plugins: description stat pend file vers src load unlod [ 1] AMX Mod X RUN - amxmodx_mm_i386. v1.8.1.3 ini Start ANY [ 2] sbsrv RUN - sbsrv_mm_i386.so v4.0.0 ini ANY ANY [ 3] Fun RUN - fun_amxx_i386.so v1.8.1.3 pl1 ANY ANY [ 4] Engine RUN - engine_amxx_i386 v1.8.1.3 pl1 ANY ANY [ 5] FakeMeta RUN - fakemeta_amxx_i3 v1.8.1.3 pl1 ANY ANY [ 6] CStrike RUN - cstrike_amxx_i38 v1.8.1.3 pl1 ANY ANY [ 7] CSX RUN - csx_amxx_i386.so v1.8.1.3 pl1 ANY ANY [ 8] Ham Sandwich RUN - hamsandwich_amxx v1.8.1.3 pl1 ANY ANY 8 plugins, 8 running

Restarting the dedicated server fixes the problem, but after 5-6 hours it happens again, always on the same two game servers. Can anyone shed some light into what is happening, is it just me being a total retard and overlooking something, or is there something a bit more complex?

Thanks in advance.

[xOR]

socket errors are most of the time problems with the server's network or firewall. it's hard to do any diagnosis from here. what you should do first is try to find out what connects the two servers that have the problems and that doesn't apply to the other 3.

it seems that sometimes the local network especially doesn't like when a server connects to itself through the remote IP. so e.g. server "Assault Server #1" will send to itself when it queries "Dust2 Server #1" on 85.8.130.158 (ofc on a different port).
so the solution could be to set xREDIRECT to query these servers through the local IP. this is getting quite complicated because you will be forced to have different serverlist.ini settings on each server, but you should give it a try. e.g. if "Assault Server #1" is the server with the socket problems, then on this server edit the serverlist.ini and add an entry for the server "Dust2 Server #1":
localaddress=192.168.0.1

replace that IP by the real local IP the server has. you could also try, as an alternative, to use localaddress=127.0.0.1.
then do the same on in the serverlist.ini of "Dust2 Server #1" for "Assault Server #1" and see if it helps. also make sure to use the newest version of xREDIRECT, earlier versions are not capable of using the local IP for server queries.

[xdimension]

Thanks for the response.

Unfortunately the problem has now occured on all servers. Server 1 and 2 are hosted on the same dedicated system that our primary webserver is run from, and the AMXX Sockets module has now started causing problems with our webserver (mainly the SQL sockets which is preventing our sites from connecting to SQL). As a result of this, we are forced to remove the plugin and disable the sockets module on the servers.
Shame really as this is a very handy plugin to have running on the servers.

Maybe we will look at alternative ways to get the plugin working (possibly move servers around), but until then, we have to remove it.

Keep up the good work with this plugin, we hope to be using it again when we can sort our problem out.