Help - Search - Members - Calendar
Full Version: How to fix webalizer on psa 6.0
The Planet Forums > Control Panels > Plesk > Plesk HOWTOs
mahiraminc
Everything was working fine until... I noticed the webalizer has stopped shows stats after November 6.

This is what I got on November 11 in mail.

Subject:

Cron run-parts /etc/cron.daily

Message:

/etc/cron.daily/00webalizer:

Warning: Truncating oversized request field [239]

Please help to fix this problem so server can resume showing stats.
mirage
This is the how to section. I believe the mods will most likely move your post to the appropriate section.
mahiraminc
Yes, please do.

For the keen ones...

the problem was... my log file was over 2 GB and webalizer stopped working.

Now, after downloading the file or processing it... everything seems to work fine icon_smile.gif
Manuel
QUOTE
Now, after downloading the file or processing it... everything seems to work fine


What exactly you did to resolve it.. I am also receiving the same like

QUOTE
/etc/cron.daily/00webalizer:
Warning: Truncating oversized referrer field
Error: Skipping oversized log record
Manuel
icon_sad.gif icon_sad.gif ??????:confused: :confused: :confused:
Squire
Most likely you have an access_log on a site somewhere that is over the 2 gig limit Manual. Technically, this limit is in the statistics program, not Webalizer, but since statistics call webalizer it shows up as a symptom.

First you'll need to find the oversize file. The following should help you with that (log in as root and adjust the path as necessary for your Plesk installation):

CODE
ls -alh /home/httpd/vhosts/*/statistics/logs/access* | sort -n +4


Once you sort out which file or files are over 2 gigabytes you have a choice. If the stats aren't important to you, you can simply delete the oversized files and run webalizer manually. If the stats are important, you'll want to split the oversized file and run statistics a few times until you have things caught back up.

To run the statistics manually is

CODE
/usr/local/psa/admin/sbin/statistics


Pay attention for errrors being reported as it's running.

Once you have everything cleaned up the best way to prevent this sort of thing from happening in the future is to enable Log Rotation for all domains on the server. Your best bet it to have log rotation triggered by the filesize, rather than a date. You can do this right in Plesk. You'll also probably want to set it up so that your rotated log files are compressed since this will take these files down to around 5% of the size of the uncompressed version.

There are lots of posts over on the Plesk forums detailing different things you can do, depending upon what exactly is stopping webalizer in its tracks.
Manuel
What if I am using cPanel!!
Squire
Then you should post your question in the cPanel area of the forum. icon_wink.gif
Manuel
Oh.....!:eek:

I dont see it as I have searched for webalizer and posted it.

I am sorry for that
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.