This can happen in the course of normal log rotation... for example, if you just have a heavy day or 2 of web traffic your logs will be larger... if you are getting this constantly, rotate the logs more often as suggested. If your traffic is going to go back down to a normal rate, the logs will most likely cure themselves... this is my experience on a CentOS 4.x system without doing any changes to logging.
On 12/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
get some logrotate utility to rotate your apache logs every once in a while instead of letting them grow indeffinately. Jason On Thu, Dec 28, 2006 at 08:43:19AM -0500, Roy Vestal wrote: > I'm getting the following error from my cron for Webalizer. I thought I > had fixed it but it doesn't appear so: > > /etc/cron.daily/00webalizer: > > Error: Skipping oversized log record > > I've run this through google a few times but never got a really good > answer. Suggestions? > > TIA, > Roy > -- > TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug > TriLUG Organizational FAQ : http://trilug.org/faq/ > TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ -- ================================================ | Jason Welsh [EMAIL PROTECTED] | | http://monsterjam.org DSS PGP: 0x5E30CC98 | | gpg key: http://monsterjam.org/gpg/ | ================================================ -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
-- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
