Hi there,
I have had a similar problem...
I noticed that a few crons were running, for whatever reason.
Try to do a
/etc/init.d/cron stop
pkill cron (Make sure no cron processes are left.)
Edit your crontab (crontab -e) and save it again.
Then restart cron: /etc/init.d/cron start
Worked fine here...
Regards,
~jm

I've followed these instructions too. Do I now need to wait 24hrs to give cron a chance to run again?

Also, it mentions editing crontab (crontab -e) and save again. Is there something I need to 'edit' or just re-save? I'm having the same issue of stats not compiling & not access at www.domain.com/stats/ (404 Error)

I've followed these instructions too. Do I now need to wait 24hrs to give cron a chance to run again?

Click to expand...

You have to wait until your cron job is scheduled to run the next time, so if you have a cron job that is run once a day, then you have to wait 24h in the worst case.

kuyaedz said:

Also, it mentions editing crontab (crontab -e) and save again. Is there something I need to 'edit' or just re-save? I'm having the same issue of stats not compiling & not access at www.domain.com/stats/ (404 Error)

This is just to redirect any output that the scripts produce (status messages, etc.) to /dev/null because otherwise you'd get an email with the output everytime a cron job runs which can be quite annoying after some time.
It does not mean that the statistics that webalizer produces are sent to /dev/null!