© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I am experiencing the same issue with a new Ubuntu 10.04LTS Server instance.
/var/log/syslog shows that cron.daily is being triggered:
Jun 4 04:57:01 zoidberg CRON[3861]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Jun 5 04:57:01 zoidberg CRON[12269]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Jun 6 04:57:01 zoidberg CRON[28089]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Jun 7 04:57:01 zoidberg CRON[20047]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Jun 8 04:57:01 zoidberg CRON[7968]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Jun 9 04:57:01 zoidberg CRON[23848]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
and running run-parts manually, executes all cron.daily scripts correctly:
matt@zoidberg:~$ sudo run-parts -v /etc/cron.daily
run-parts: executing /etc/cron.
run-parts: executing /etc/cron.
run-parts: executing /etc/cron.
run-parts: executing /etc/cron.
run-parts: executing /etc/cron.daily/ntp
run-parts: executing /etc/cron.
run-parts: executing /etc/cron.
If it makes any difference, this is on a new Parallels Virtuozzo/OpenVZ virtual server from Media Temple.