Bug#753576: systemd stopped responding to dbus.socket connections

[Stephan Sokolow (You actually CAN reply)]

Oh, wait. I forgot step 0. Update and upgrade first. It's such a habit 
that I lump it in with importing the VMs.

On 17-02-27 04:04 AM, Stephan Sokolow (You actually CAN reply) wrote:
> I'm not sure if it's the same problem, but, I have something that at
> least has similar symptoms which may be easier to reproduce:
>
> Release: The VirtualBox version of the bento/debian-8.6 Vagrant VM
> Reproduction:
>
> 1. apt-get install systemd-cron
> 2. Futz around until you realize jessie's systemd is too old to support
>    hourly cronjobs.
> 3. apt-get install cron (without rebooting in between)
>
> On my VM, the attempt to reinstall started encountering timeouts when it
> attempted to setup the newly-installed packages and, from then on, any
> attempt to use `systemctl` resulted in `org.freedesktop.systemd1`
> timeouts. (To the point that Vagrant would error out unless I reset the
> VM because anything less drastic would die while trying to ask for a
> clean shutdown.)
>
> (I don't think my "trim it down further" ansible playbook touches
> anything relevant to this but it's also available on request.)

-- 
Stephan Sokolow

Note: My e-mail address IS valid. It's a little trick I use to fool
"smarter" spambots and remind friends and family to use the custom
aliases I gave them.