Page 1 of 1

Steam / Valve update 06th May 2011

PostPosted: Fri May 06, 2011 8:13 pm
by IXL
Just checking before I spend hours going through logs and posts, has anyone updated there server this afternoon ( from approx 6pm uk gmt ) and updated there server?

Were having issues since, trying to get the servers up with soucemod, metamod and gungame.

Server was running fine yesterday.

Were using :
Event scripts : v2.1.1.360
Metamod : mmsource-1.8.6-linux.tar.gz
Sourcemod : sourcemod-1.3.7-linux.tar.gz

Any help would be lovely...

IXL

PostPosted: Fri May 06, 2011 10:26 pm
by daggerclan
Use this if you have sourcemod running on linux:
http://dl.dropbox.com/u/10968786/SM/hotfix.ext.zip

Use this if you have sourcemod running on windows:
http://forums.alliedmods.net/attachment.php?attachmentid=85666&d=1304690785

Put the files in your /extensions directory and restart your server.

Re: Steam / Valve update 06th May 2011

PostPosted: Sat May 07, 2011 1:39 am
by satoon101
IXL wrote:Event scripts : v2.1.1.360
If you really are still running 2.1.1.360, you should have been having crashes for the last 3 weeks or so. Please update to 2.1.1.366, as that is the current working version of EventScripts:
http://forums.eventscripts.com/viewtopi ... 28&t=40765

Also, make sure to update your SPE installation as well:
http://forums.eventscripts.com/viewtopi ... 81&t=29657

And if you aren't using the newest GunGame version (5.1.510), please update that, too:
http://addons.eventscripts.com/addons/view/gungame51

Satoon

PostPosted: Tue May 10, 2011 8:56 pm
by IXL
Thanks for the heads up fellas. However we havent had any crashes at all on the versions I mentioned what so ever ( in fact its been going beautifully ). Server has been the same in that form, since the february update and knive fix of es_xload autokick_disabler.

Its only since last Friday that the issue occured. All our servers update each morning at 4am, and although the server would start, it started to crash within a few minutes/seconds. After redoing the steam update manually (which we can only presume failed or timed out at some point, perhaps causing the issue mainly ), and then applying the 5.1.510 GG, seemed to solve the problem so far. ( we were on 5.1.506)

Anyway, much appreciated for your time and suggestions. Cheers fellas.

IXL