Found this in my logs: (full /var/log/cron/notice attached) cron.daily not completed May 3 00:02:00 kashyyk fcron[28454]: Job run-parts /etc/cron.daily started for user root (pid 28455)
Fcron update from 2.9.5.1 to 2.9.6 (tsl3.0 backport) May 9 18:45:34 kashyyk fcron[12790]: SIGTERM signal received May 9 18:45:35 kashyyk fcron[12790]: Exiting with code 0 May 9 18:45:36 kashyyk fcron[20490]: fcron[20490] 2.9.6 started cron.daily not completed (zombie) May 11 00:02:00 kashyyk fcron[28392]: Job run-parts /etc/cron.daily started for user root (pid 28393) 20490 ? Ss 0:00 fcron 28392 ? S 0:00 \_ fcron 28393 ? Z 0:00 \_ [run-parts] <defunct> fcron restart: (repeated exec of daily job, thats ok, since first try failed) May 11 23:13:59 kashyyk fcron[20490]: SIGTERM signal received May 11 23:14:03 kashyyk fcron[22976]: fcron[22976] 2.9.6 started May 11 23:14:03 kashyyk fcron[22976]: updating configuration from /var/spool/fcron May 11 23:14:03 kashyyk fcron[22976]: adding file root May 11 23:14:23 kashyyk fcron[22984]: Job run-parts /etc/cron.daily started for user root (pid 22985) May 11 23:14:42 kashyyk fcron[22984]: Job run-parts /etc/cron.daily completed (mailing output) all ok: May 12 00:02:01 kashyyk fcron[25075]: Job run-parts /etc/cron.daily started for user root (pid 25076) May 12 00:02:12 kashyyk fcron[25075]: Job run-parts /etc/cron.daily completed (mailing output) again restart: May 12 00:09:00 kashyyk fcron[25316]: fcron[25316] 2.9.6 started May 12 00:09:00 kashyyk fcron[25316]: updating configuration from /var/spool/fcron May 12 00:09:00 kashyyk fcron[25316]: adding file root all ok: May 13 00:02:00 kashyyk fcron[20656]: Job run-parts /etc/cron.daily started for user root (pid 20657) May 13 00:02:24 kashyyk fcron[20656]: Job run-parts /etc/cron.daily completed (mailing output) cron.daily not completed (creates new zombie AND old detects that old zombie died..) May 14 00:02:00 kashyyk fcron[16569]: Job run-parts /etc/cron.daily started for user root (pid 16570) May 14 00:04:19 kashyyk fcron[28392]: Job run-parts /etc/cron.daily completed (mailing output) 25316 ? Ss 0:00 fcron 16569 ? S 0:00 \_ fcron 16570 ? Z 0:00 \_ [run-parts] <defunct> cron.daily not started (old job still exists..) May 15 00:01:00 kashyyk fcron[12144]: Job run-parts /etc/cron.hourly started for user root (pid 12145) May 15 00:01:00 kashyyk fcron[12144]: Job run-parts /etc/cron.hourly completed May 15 00:22:00 kashyyk fcron[13023]: Job run-parts /etc/cron.weekly started for user root (pid 13024) May 15 00:22:00 kashyyk fcron[13023]: Job run-parts /etc/cron.weekly completed May 15 01:01:00 kashyyk fcron[14672]: Job run-parts /etc/cron.hourly started for user root (pid 14673) May 15 01:01:00 kashyyk fcron[14672]: Job run-parts /etc/cron.hourly completed fcron restart: (repeated exec of daily job, which is ok) May 15 17:50:24 kashyyk fcron[25316]: SIGTERM signal received May 15 17:50:28 kashyyk fcron[24586]: fcron[24586] 2.9.6 started May 15 17:50:28 kashyyk fcron[24586]: updating configuration from /var/spool/fcron May 15 17:50:28 kashyyk fcron[24586]: adding file root May 15 17:50:47 kashyyk fcron[24590]: Job run-parts /etc/cron.daily started for user root (pid 24591) May 15 17:51:27 kashyyk fcron[24590]: Job run-parts /etc/cron.daily completed (mailing output) ps fax just after restart: (note that the "old" zombie is still there, and will die in some days?!) 16569 ? S 0:00 fcron 16570 ? Z 0:00 \_ [run-parts] <defunct> 24586 ? Ss 0:00 fcron 24590 ? S 0:00 \_ fcron 24591 ? S 0:00 \_ /bin/bash /usr/bin/run-parts /etc/cron.daily 24657 ? S 0:00 \_ /bin/bash /etc/cron.daily/swup.cron 24658 ? D 0:00 \_ /usr/bin/python /usr/bin/swup --upgrade Any Ideas? Upstream bug? Olaf
_______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
