Printable View
Hi there everyone. It's been a long time since i created a thread on RZ.
I was wondering,anyone know how to fix the GlobalMgrSvr that crashes every 12 hours +?
I tried searching seems can't find an answer.I tried looking at the other thread saying cannot connect to the mssql,but it has database connect success.
Did anyone notice this problem? .. cheers :):
I have the same problem
this problem is since we all set up our own test/public server :): still no one giving a answer.there are some who already fix this but you know people are to "SELFISH" they dont want to share it..
So even i've posted this help thread.Nobody is going to share and help then?
I thought that the people who shared EP8 was going to expand this cabal knowledge,but in the end still ended up the same thing.
try to use crond
Add to file /etc/crontab this string (Checks services every minute):
*/1 * * * * root /home/cabal/check_daemon.sh
The log file of autostarts will be /home/cabal/check_daemon.log
(run chmod 0700 /home/cabal/check_daemon.log if you dont see him)
Over the past two days in the log file is only one record of the autostart (Mon Feb 25 15:58:01 MSK 2013: GlobalMgrSvr starting)
So far (since Sun Feb 24 20:00:01 MSK 2013) server runs stably without service interruption.
I hope that this will solve the problem
i can't see etc/crontab , are you saying etc/cron.d ?Quote:
Originally Posted by vanushka
PS: ops! i saw the crontab, its not a folder, its a file :P
File /etc/crontab, yes it is not folder :):
As well, these commands are available in the /etc/cron.d/chk_cabal, but in my case, for some reason, do not work.
Therefore, I add them to the main list (/etc/crontab)
Yeah i understand now. but this */1 * * * * root /home/cabal/check_daemon.sh forcing the service to start every minute.Quote:
Originally Posted by vanushka
I've posted a same topic. http://forum.ragezone.com/f451/chatn...unning-910334/
And base on the replies on that thread, it seems that there's no solution yet to prevent these services from crashing other than checking and restarting services regularly. And not because nobody wants to share the fix.. just my opinion.
It stops exactly every 32 hours, sitting idle and with 1024MB ram when it fills up.
Try to increase the ram first and then after you increased ram, disable the service logs and see what happens.
I have not tried to do so yet.
As you can see it has something to do with resources running out, so monitor it closely.Quote:
Originally Posted by jaguar666
For now, all of this is speculation.
check master folder and u see core.12331, this is dumped ram and processor
I doubt its RAM usage. I have 24 gigs of ram yet it happens.
Yes it's a RAM usage.
First off, why did you put an "a" there? Second, it can't be. Memory caching is disabled (I disabled it). And my memory foot print doesent go over 2gbQuote:
Originally Posted by Drav3n
How Much RAM Did You Use With Your CentOS Of Your 24GB RAM? Did You Go Over The Red Line?Quote:
Originally Posted by Extornia