Package: cron Version: 3.0pl1-127 Severity: normal After a lot of investigation, I'm now pretty sure that cron @reboot jobs are misteriously dying when the cron package gets upgraded. Which makes that nice functionality pretty useless. I'm not yet sure that it happens in 100% of cases, that's why it was so hard to track, yet I'm sure it's the reason why some of my long lived processes started from cron eventually misteriously die.
The last example is the perl script which is properly daemonized upon startup, it closes stdin/out/err, forks, parent exits, setsid() is called and child process proceeds. Yet, this is what I see in lastcomm today: systemctl F X root pts/2 0.00 secs Sun Oct 26 10:51 milter F X user __ 246.56 secs Mon Oct 6 01:49 cron S X root __ 0.90 secs Mon Oct 6 01:49 systemctl S root pts/2 0.00 secs Sun Oct 26 10:51 systemd F root __ 0.00 secs Sun Oct 26 10:51 Both processes exited when the cron package got upgraded and cron restarted (milter is the @reboot job in question, if it's not obvious). And as the events are surrounded with many systemd calls, this might turn up to be systemd bug eventually. Or lack of functionality? Dunno... What I know is that I'll have to revert to starting my stuff from /etc/rc.local instead of cron @reboot, unless there's some idea how to fix this issue. -- Package-specific info: --- EDITOR: not set --- /usr/bin/editor: /usr/bin/vim.tiny --- /usr/bin/crontab: -rwxr-sr-x 1 root crontab 36008 Oct 26 00:04 /usr/bin/crontab --- /var/spool/cron: drwxr-xr-x 5 root root 4096 Apr 21 2012 /var/spool/cron --- /var/spool/cron/crontabs: drwx-wx--T 2 root crontab 4096 Oct 25 12:38 /var/spool/cron/crontabs --- /etc/cron.d: drwxr-xr-x 2 root root 4096 Oct 26 10:10 /etc/cron.d --- /etc/cron.daily: drwxr-xr-x 2 root root 4096 Oct 26 10:10 /etc/cron.daily --- /etc/cron.hourly: drwxr-xr-x 2 root root 4096 Oct 26 10:10 /etc/cron.hourly --- /etc/cron.monthly: drwxr-xr-x 2 root root 4096 Oct 26 10:10 /etc/cron.monthly --- /etc/cron.weekly: drwxr-xr-x 2 root root 4096 Oct 26 10:10 /etc/cron.weekly -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.17.0+ (SMP w/2 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages cron depends on: ii adduser 3.113+nmu3 ii debianutils 4.4 ii dpkg 1.17.21 ii init-system-helpers 1.21 ii libc6 2.19-12 ii libpam-runtime 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii libselinux1 2.3-2 ii lsb-base 4.1+Debian13+nmu1 Versions of packages cron recommends: ii postfix [mail-transport-agent] 2.11.2-1 Versions of packages cron suggests: pn anacron <none> pn checksecurity <none> ii logrotate 3.8.7-1 Versions of packages cron is related to: pn libnss-ldap <none> pn libnss-ldapd <none> pn libpam-ldap <none> pn libpam-mount <none> pn nis <none> pn nscd <none> -- Configuration Files: /etc/crontab changed: SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin 0 * * * * root cd / && run-parts --report /etc/cron.hourly 25 4 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) 47 4 * * 6 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ) 52 4 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly ) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
