Am 27.02.2017 um 09:51 schrieb Stephan Sokolow (You actually CAN reply):
> I'm not sure if it's relevant, but I managed to get similar connection
> timeouts (specifically, `systemctl` consistently failing with timeouts
> on `org.freedesktop.systemd1`) when I ran `apt-get install systemd-cron`
> and
Am 27.02.2017 um 11:04 schrieb Vincent Danjean:
> I forgot to update this bug report.
> On my machine, I did some cleanup (apt-get autoremove + manual
> removal of package that are not available in stretch any more).
> This solve the problem: the machine boots correctly without
> any problema
Le 27/02/2017 à 09:51, Stephan Sokolow (You actually CAN reply) a écrit :
> I'm not sure if it's relevant, but I managed to get similar
> connection timeouts (specifically, `systemctl` consistently failing
> with timeouts on `org.freedesktop.systemd1`) when I ran `apt-get
> install systemd-cron` an
I'm not sure if it's relevant, but I managed to get similar connection
timeouts (specifically, `systemctl` consistently failing with timeouts
on `org.freedesktop.systemd1`) when I ran `apt-get install systemd-cron`
and then changed my mind after I realized my systemd was too early to
support ho
Le 10/02/2017 à 16:47, Vincent Danjean a écrit :
> Looking at the logs ("journalctl -b"), the first errors I see are:
Here is the start of "journalctl -b" (got as:
socat EXEC:"journalctl --no-pager -b",pty GOPEN:boot.log
so "less -R boot.log" show colors)
Regards,
Vincent
--
Vincent D
