Bug#798242: systemd: Failed to execute operation: Connection timed out

[James Cameron]

Martin Pitt wrote:
> James Cameron wrote:
> > The problem system is still in the state it was left in when
> > #798242 was raised.  We've been unable to take the risk of a
> > reboot; yet.  Can you speculate if reboot would be bad idea?
> 
> No, a reboot is probably the only thing which will reset the state
> properly. The "35 not upgraded" packages should be okay, and
> unconfigured systemd is ok as it only failed in the trigger. But
> leaving udev unconfigured could lead to boot troubles, so maybe try
> a round (or two) of "dpkg --configure -a" first?

Thanks.  Only rsyslog.postinst did hang, process tree shows;

 8781 pts/0    S+     0:00      \_ dpkg --configure -a
 8782 pts/0    S+     0:00          \_ /bin/sh /var/lib/dpkg/info/rsyslog.postinst configure 8.4.2-1
 8793 pts/0    S+     0:00              \_ /bin/sh /usr/sbin/invoke-rc.d rsyslog restart
 8812 pts/0    S+     0:00                  \_ systemctl restart rsyslog.service
 8813 pts/0    S+     0:00                      \_ /bin/systemd-tty-ask-password-agent --watch

System is up after reboot.

-- 
James Cameron
http://quozl.netrek.org/