Web Hosting Talk







View Full Version : Raqbackup.sh Memory & other issues


StartAnISP
12-15-2002, 05:56 AM
We have been using Raqbackup.sh for a few months and for the most part it's great.

Thing is, every day that we run it we seem to get these emails from the server saying that the memory is at 97 percent or so. We doubled the memory in the server and still get the emails.

We have also noticed that this script seems to tax the system so much that once in a while it takes the whole machine out.. I means the machine dies essentially, it's pingable but no services respond until we reboot. We have pretty much been able to narrow this problem down to the timeframe when the backup was happening.

Is anyone else experiencing these issues when using this utility?

Thanks in advance for any advice here..

dnid
12-15-2002, 07:54 AM
If you still use CMU 2.27 please upgrade to the newest beta from ftp://ftp-eng.cobalt.com/pub/users/jeffb/cmu/beta - this will solve some load- and RAM-issues.

Daniel

StartAnISP
12-15-2002, 03:18 PM
Thank You, I will give this a shot.

StartAnISP
12-16-2002, 01:06 PM
Just to give you an update..

I loaded the new CMU and still today got this:

Memory on the Sun Cobalt server is heavily used.
The Sun Cobalt server needs more memory than it currently has.
Consider adding more DRAM to the server.

Total memory is: 389092 KB
Used memory is: 381128 KB
Free memory is: 7964 KB
Percent used is: 97

dnid
12-16-2002, 01:45 PM
are you sure that this is related to raqbackup.sh? I think this could be a analog/parsereport-issue (this job is done prior the execution of raqbackup.sh)

See this posting:
http://www.webhostingtalk.com/showthread.php?s=&threadid=27564&goto=nextnewest

HTH
Daniel

StartAnISP
12-16-2002, 02:39 PM
I will check out the post you referenced.. The reason we suspect this is that it did nto start until the exact day we started schedule the script. When we stop it from running for a few days the errors and problems go away. Also, the errors come at the exact times that the script runs every day without fail. I would say this is a pretty good indicator that the script, CMU or both is causing the problem. Just my opinion of course..