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

2014-11-17 Thread intrigeri
Control: tag -1 + moreinfo Hi, can any of you reproduce this on current testing/sid (that is, with systemd v215)? Cheers, -- intrigeri ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org

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

2014-11-17 Thread Debian Bug Tracking System
Processing control commands: tag -1 + moreinfo Bug #757213 [systemd] systemd becomes non-responsive, connection refused to /run/systemd/private Added tag(s) moreinfo. -- 757213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757213 Debian Bug Tracking System Contact ow...@bugs.debian.org

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

2014-11-17 Thread Iain M Conochie
Hey Since upgrading to systemd 215-5+b1, I have seen no further re-occurrences of this issue. Cheers Iain ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org

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

2014-09-06 Thread Iain M Conochie
Hey, I have the same situation. Seems like systemd froze 3 days ago. What got me to notice was an attempted apt-get upgrade on this jessie system: sudo ls /proc/1/fd [sudo] password for iain: 0 1 2 14:28:24 weezer:~$ sudo ls -l /proc/1/fd total 0 lrwx-- 1 root root 64 Aug 30 15:25 0 -

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

2014-08-27 Thread 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