I've read through the forums on this problem and tried several things to get this to work.

On Feb. 6 Webalizer seems to have stopped processing logs. I noticed that my access_log for each domain was increasing, and since I depended upon Webalizer to rotate my logs after processing that has become a problem.

Typically I run Urchin web stats at 0400 and then Webalizer at 0407, which allows time for Urchin to complete processing before Webalizer runs and rotates the files.

In case the log files were too large, I ran Urchin for each domain and then deleted all files and restarted apache to create empty log files. I then run Webalizer just like the cron function in Plesk:

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

It hung (even with basically empty logs) and did nothing. I also tried just running "webalizer" from the command line, and it also did nothing.

Since all I really want to do is rotate logs after Urchin is done, I tried running logrotate:
/usr/bin/logrotate
but that didn't rotate the access_logs for the domains.

Any ideas?

bump

if u search around here and other forums u would know this happen quite often

Yes I know, which is why I prefaced my post with "I've read through the forums on this problem and tried several things to get this to work."

The thing is it seems that it could not be solve? Even at Plesk forum people are stuck with that.

I had that problem long ago and what I did at one point of time is only to stop it at the domain settings at Plesk, then restart it and it suddenly just works. But the funny thing is some of the domains still doesn't.

So I decided to give all my clients URCHIN instead.