Re: [systemd-devel] Strange problem: Failed to get properties: Failed to activate service
On Thu, Oct 18, 2018 at 3:29 PM Cecil Westerhof wrote: > I found out that in reality no reboot had taken place. For one reason or > another that did not work. Doing: > systemctl reboot > systemctl poweroff > init 0 > halt > > All did not work. Those gave messages like: > Transport endpoint is not connected This is very familiar to me. Try this: 1) Boot the computer. 2) Run "systemctl daemon-reexec" as root. 3) Run "dmesg" as root. 4) Look for a pid 1 segfault or a message that says "Freezing execution". If you see a SIGSEGV, let me know. Note that this problem is *not* present in the upstream code base. Cheers, -- Jan Synacek Software Engineer, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Strange problem: Failed to get properties: Failed to activate service
On Do, 18.10.18 15:14, Cecil Westerhof (cldwester...@gmail.com) wrote: > I found out that in reality no reboot had taken place. For one reason or > another that did not work. Doing: > systemctl reboot > systemctl poweroff > init 0 > halt > > All did not work. Those gave messages like: > Transport endpoint is not connected > > I did a hard reset and that seems to have solved my problem. > > My problems started after an update of VirtualBox (and one other package). > Why I do not know. The above suggests PID 1 is dead for some rason. What does "pstack 1" as root print (with gdb installed)? Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Strange problem: Failed to get properties: Failed to activate service
Op wo 17 okt. 2018 om 20:06 schreef Cecil Westerhof : > Since this morning I have a strange problem, when I execute: > systemctl status cups > > I get: > Failed to get properties: Failed to activate service > 'org.freedesktop.systemd1': timed out > > This is with every service, not just cups. > > I tried 'everything', even rebooting the system. > What could be the problem. > This is with: > systemd 239 > +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP > +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS > +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid > > On: > Distributor ID: Debian > Description:Debian GNU/Linux 9.5 (stretch) > Release:9.5 > Codename: stretch > I found out that in reality no reboot had taken place. For one reason or another that did not work. Doing: systemctl reboot systemctl poweroff init 0 halt All did not work. Those gave messages like: Transport endpoint is not connected I did a hard reset and that seems to have solved my problem. My problems started after an update of VirtualBox (and one other package). Why I do not know. -- Cecil Westerhof ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Strange problem: Failed to get properties: Failed to activate service
On Mi, 17.10.18 20:06, Cecil Westerhof (cldwester...@gmail.com) wrote: > Since this morning I have a strange problem, when I execute: > systemctl status cups > > I get: > Failed to get properties: Failed to activate service > 'org.freedesktop.systemd1': timed out > > This is with every service, not just cups. This suggests systemd for some reason is not on the bus. That's almost certainly a bug. No idea how that can happen, there might be something in the logs explaining why it disconnected from the bus. Usually "systemctl daemon-reexec" should make systemd reconnect to the bus. Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Strange problem: Failed to get properties: Failed to activate service
Since this morning I have a strange problem, when I execute: systemctl status cups I get: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out This is with every service, not just cups. I tried 'everything', even rebooting the system. What could be the problem. This is with: systemd 239 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid On: Distributor ID: Debian Description:Debian GNU/Linux 9.5 (stretch) Release:9.5 Codename: stretch -- Cecil Westerhof ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
