[DM2] Save DB timed out

[eddy]

[dm2] m2server

Is this bad or not

just got this on m2server wot does it mean plz

[09/06/2007 23:56:47] [RunDB] Save DB Timed Out...
[09/06/2007 23:56:55] [RunDB] Save DB Timed Out...
[09/06/2007 23:56:56] [RunDB] Save DB Timed Out...
[09/06/2007 23:57:04] [RunDB] Save DB Timed Out...
[09/06/2007 23:57:06] [RunDB] Save DB Timed Out...
[09/06/2007 23:57:07] [RunDB] Save DB Timed Out...
[09/06/2007 23:57:15] [RunDB] Save DB Timed Out...
[09/06/2007 23:57:18] [RunDB] Save DB Timed Out...
[09/06/2007 23:57:26] [RunDB] Save DB Timed Out...
[09/06/2007 23:57:28] [RunDB] Save DB Timed Out...
[09/06/2007 23:57:36] [RunDB] Save DB Timed Out...

 

[koni]

are you playing on the pc that is running the files ?

whats the stats of ur pc ? for example cpu ? ram ?

normally these time outs are caused by low resources on the hosting machine, high ram usage, high cpu load or lots of programs running in the background

bear in mind that sql server uses quite alot of ram to work, the m2 server will use 300 odd meg + , windows will use a fair wack etc etc etc

a way around it is to do alt, ctrl and del to bring up the task manager, click the processes tab, then find the dbserver, right click it and raise its priority to high, then find the m2server , right click that and put its priority to low this will sort the problem on a temp basis but when you reboot ur pc and restart the files you will have to do it every time.

cheers

koni

 

[eddy]

thank m8 will try

 

[jamiedotco]

this is a bug in the programming of the Db server.

I have my server running on a quad core CPU with 4 gigs of ram, and i still get this every now and then for no reason at all.

 

[Dave85]

Quad core CPU and 4Gb of ram...you have too much money lol <3

I have found in many tests that the cause for the time outs are due to 1 thing, the M2Server, NOT the DBServer.

I looked at what/why i was getting these errors and then ended up spending too much custom building my server. What happens is The DBServer is happily minding its own business taking a small amount of ram and cpu then all of a sudden M2Servers opened, DBServers like oo whats that? As the M2Server *i call, warms up, loading your spawn file* the amount of resources are swallowed up by it and as the servers load *players* increase so does the cpu power needed for the DBServer and M2Server so they end up fighting over it. The M2Server is actually working in the same nature as a virus which is basicly that it will eat up all power it can to run at a high rate to deal with the information. So as i was saying the M2Server and DBServer are fighting over power of the cpu and the ram then all of a sudden M2Server pushes DBServer aside and take what it wants and more. It then gets to a point where the M2Server is eating up so much cpu and ram that the DBServer isn't getting enough so it then ends up shouting about it acting like a 5 year old...'I'm telling on you M2Server!' and then the DBServer starts having a paddy and says 'I want more power but the M2Servers being too F*****g greedy so im not gonna bother saving anything now and bugger up your DB that you spent so long putting together'.

in short the M2Server draws too much power of the cpu and ram, thus meaning there isn't enough for the DBServer.

P.S. Pongo Mir server childrens story books at all good stores near you soon with such classics as 'mummy my server self conbusted' and for the adults 'how having kids can benefit you, they have alot more energy so make them mine for you while you sleep!'