So, after double-checking the docs more carefully, I finally have a ‘good cron’ successfully running hourly. Archive.log shows the report, and is being regenerated when it’s supposed to be, every hour.
That’s the good news.
The bad news is that I’m still getting the hourly error emails like the one I pasted above. And they’re clearly coming from a second cron running somewhere else on my server - the emails have the same sender as the good cron - but I can’t find this broken cron, so I still don’t know where these error messages are coming from.
Supposedly this is how to find crons for all users:
for user in $(cut -f1 -d: /etc/passwd); do echo $user; crontab -u $user -l; done
But that doesn’t find /etc/cron.d/piwik, which is the good cron.
I also tried checking the running daemons:
But there was nothing overtly piwik-related in the results.
Any ideas on how I can find the broken cron to stop the hourly error spam?