Here's an interesting one I hope someone has run across before.

I have one domain on one server that is going gangbusters. To the point that the access_log and access_log.processed are ending up over the 2 gig mark every day. Which of course causes Webalizer to fail for that domain.

Now for the moment I can manually delete the .processed log or run /usr/local/psa/admin/sbin/statistics a couple of times per day so that they don't get too large between statistics runs. But I really don't want/like to do that because it runs the stats for every domain on the server Especially since this single site is only going to get busier and busier for the next 5 months.

I'm wondering if anyone knows if there are any commands I can append to the end of /usr/local/psa/admin/sbin/statistics that will tell webalizer run on just the specific domain in question. If there is, then I could at least set it up as a cron job to run a few times per day without creating undue server load.

I tried doing a search here, the Plesk forums and on the 'Net, but no dice.

hi,

first of all you should tweak your logrotation for the site in question so that you limit it to a certain size. When this size reaches logrotate should tak care of it. This can be done from plesk.
Second, if you wish to run webalizer for a single domain you can do that from the command line

# webalizer -d -o

test the above command and then you can setup a cron job for it.

Thanks karnash. I figured there was a way to run the stats on a single domain, just hadn't had the need yet.

I've already tweaked the log rotation and it's fine for the moment as the compressed access_log.processed only ends up being 30-50M. But the fear is, and it's gonna happen based upon historical data, that by late next month through the end of June the access_log alone is going to be over 2 gigs each day. LOL No way around that problem other than to run the stats more often.