Bug#757213: systemd becomes non-responsive, connection refused to /run/systemd/private

[Guus Sliepen]

I had the same problem yesterday, I noticed it when trying to apt-get
upgrade a debian testing system. Fuser showed no process owning
/run/systemd/private, and ls /proc/1/fd showed that all filedescriptors
were closed, except 0, 1 and 2 which were linked to /dev/null.

After rebooting that problem seemed to be gone, except it kept the root
filesystem read-only and failed to start several services.
Unfortunately, it's on a machine that needs to be up and running, so I
didn't have the opportunity to debug the problem, and installed sysvinit
instead. If there is anything I should look for in the syslog, let me
know.

-- 
Met vriendelijke groet / with kind regards,
      Guus Sliepen <guus at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140827/78b2fd32/attachment-0002.sig>