AWstats updates work fine for all other domains on the server. The cron task is there and is correct. Manually running from command line completes very fast (2-3 seconds).

Among a ton of other reasons, AWstats may fail to run if a previous collection crashed while running and left the lock active.

Look for /tmp/awstats.domain.tld.lock. If that file exists and you are sure no process is currently running for that domain, delete the file.

Afterwards automatic update of the stats via cron or manually running the command should succeed. A manual run for all domains on a Virtualmin system can be called with:


Leave a Reply