Me too, but it wasn't globally true.   I ran:

$ pdsh -lroot -g os=debian_linux '[ "$(lsb_release -cs)" = "jessie" ] && {
systemctl -q is-active cron.service || { echo CRON_NOT_RUNNING; systemctl
restart cron ;} ;}' | tee /tmp/jessie-cron.log
(i use PDSH to remote manage several hundred Debian systems, most still
Wheezy.)

and found a good chunk of my Jessie desktops with unattended-upgrades were
hit by this.
(but not all).  Also, my virtualbox Jessie instance here at home was
upgraded by apper via notifications interactively (not unattended-upgrades)
and 'cron' restarted fine there.  (perhaps the 'cron' package has already
been fixed?)

$ systemctl status cron
● cron.service - Regular background program processing daemon
   Loaded: loaded (/lib/systemd/system/cron.service; enabled)
   Active: active (running) since Sun 2015-09-06 10:56:34 MDT; 36min ago
     Docs: man:cron(8)
 Main PID: 12431 (cron)
   CGroup: /system.slice/cron.service
           └─12431 /usr/sbin/cron -f

--stephen

On Sun, Sep 6, 2015 at 4:30 AM, Joerg Schuetter <[email protected]> wrote:

>
>
>
> Dear debian release team
>
>
>
> On my debian systems (running Jessie) I have spotted that the cron daemon
> does not run after the automatic upgrade took place. I had to restart the
> cron job manually on all systems.
>
> To ease the upgrade the package "cron-apt" is used (download and install).
> This task worked well the last few years. Today was the first time where I
> spotted an issue with this upgrade mechanism.
>
>
>
> Best regards
>
>   Joerg
>
>
>



-- 
Stephen Dowdy  -  Systems Administrator  -  NCAR/RAL
303.497.2869   -  [email protected]        -  http://www.ral.ucar.edu/~sdowdy/

Reply via email to