Re: [cobalt-users] SUMMARY: backup.cgi script getting out-of-memory errors

[Brent Sims <bs@xxxxxxxxxxx>]

On Thu, 28 Mar 2002, Evans, Tim wrote:

} First, the individual asked me if my ISP/colocator was one of a couple of
} specific ones.  Then, he/she *told* me my ISP *is* one of those two specific
} ones and that was the problem.
}
} Duh-uh, I do know who my ISP is--and it is not (as I told this individual)
} one of the named ones.

Hi Tim,

	I've been battling a similar problem on a couple of RAQs
here. First off, you simply may not have enough memory to handle a
complete backup at this point in time. As your backups get bigger
and bigger more and more system resources are required to make them
and, obviously, there is only a finite amount of system resources
available. You might consider adding more memory and/or switching to
a less taxing tool for backing up your server like rsync or
something along those lines.

	Then again, you may be able to correct the problem in the
same manner we did here - by taking some, or all, of the scripts out
of the /ect/crond.daily directory and activating them individually
with a carefully engineered standard crontab. By "carefully
engineered" I mean scheduling the events so that the server has a
bit of time to breath a bit between the events and so that none of
them overlap. While it took a few days, I managed to get the RAQs
that were giving us trouble to settle down in this manner. This will
most certainly break your warranty though...

	Peace be with you,

	Brent Sims
	WebOkay Internet Services, LLC
	http://www.WebOkay.net
	mailto: Brent@xxxxxxxxxxx
	(719) 595-1427 (Voice/Fax)

P.S. I doubt your colo provider is at fault here but the butler may
very well be...