Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#830722: systemd: systemctl aborts with "No Such Method"
110 views
Skip to first unread message
Peter Gossner
Jul 10, 2016, 2:50:02 PM7/10/16
to
Package: systemd
Version: 230-7
Severity: important
Dear Maintainer,
Attempting to (re)understand systemd ...
~$ systemctl
Failed to list units: No such method 'ListUnitsFiltered'
other options also fail
e.g.
sudo systemctl try-restart exim4
Failed to try-restart exim4.service: No such method 'TryRestartUnit'
See system logs and 'systemctl status exim4.service' for details.
I also see logind errors and have been having dbus session issues which may all be related to a pam module.
At other times systemd has attempted to rename network interfaces, screw up diplay manager, hang without console access , fail to start real consoles at all deep fry kittens ...
Fortunately this is a humble home desktop and not a production server.
At some point soon I will do a fresh install, Its proabably something to do with my bent view of networking or black roosters or something.
-- Package-specific info:
-- System Information:
Debian Release: stretch/sid
APT prefers stable
APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 4.6.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages systemd depends on:
ii adduser 3.115
ii libacl1 2.2.52-3
ii libapparmor1 2.10.95-4
ii libaudit1 1:2.6.3-1
ii libblkid1 2.28-5
ii libc6 2.23-1
ii libcap2 1:2.25-1
ii libcap2-bin 1:2.25-1
ii libcryptsetup4 2:1.7.0-2
ii libgcc1 1:6.1.1-9
ii libgcrypt20 1.7.1-2
ii libgpg-error0 1.23-1
ii libidn11 1.32-3.1
ii libkmod2 22-1.1
ii liblzma5 5.1.1alpha+20120614-2.1
ii libmount1 2.28-5
ii libpam0g 1.1.8-3.3
ii libseccomp2 2.3.1-2
ii libselinux1 2.5-3
ii libsystemd0 230-7
ii mount 2.28-5
ii util-linux 2.28-5
Versions of packages systemd recommends:
ii dbus 1.10.8-1
ii libpam-systemd 230-7
Versions of packages systemd suggests:
ii policykit-1 0.105-15
ii systemd-container 230-7
ii systemd-ui 3-4
Versions of packages systemd is related to:
ii udev 230-6
-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
NAutoVTs=6
ReserveVT=6
KillUserProcesses=true
KillExcludeUsers=root
InhibitDelayMaxSec=5
HandlePowerKey=poweroff
IdleAction=ignore
RemoveIPC=yes
-- no debconf information
Version: 230-7
Severity: important
Dear Maintainer,
Attempting to (re)understand systemd ...
~$ systemctl
Failed to list units: No such method 'ListUnitsFiltered'
other options also fail
e.g.
sudo systemctl try-restart exim4
Failed to try-restart exim4.service: No such method 'TryRestartUnit'
See system logs and 'systemctl status exim4.service' for details.
I also see logind errors and have been having dbus session issues which may all be related to a pam module.
At other times systemd has attempted to rename network interfaces, screw up diplay manager, hang without console access , fail to start real consoles at all deep fry kittens ...
Fortunately this is a humble home desktop and not a production server.
At some point soon I will do a fresh install, Its proabably something to do with my bent view of networking or black roosters or something.
-- Package-specific info:
-- System Information:
Debian Release: stretch/sid
APT prefers stable
APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 4.6.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages systemd depends on:
ii adduser 3.115
ii libacl1 2.2.52-3
ii libapparmor1 2.10.95-4
ii libaudit1 1:2.6.3-1
ii libblkid1 2.28-5
ii libc6 2.23-1
ii libcap2 1:2.25-1
ii libcap2-bin 1:2.25-1
ii libcryptsetup4 2:1.7.0-2
ii libgcc1 1:6.1.1-9
ii libgcrypt20 1.7.1-2
ii libgpg-error0 1.23-1
ii libidn11 1.32-3.1
ii libkmod2 22-1.1
ii liblzma5 5.1.1alpha+20120614-2.1
ii libmount1 2.28-5
ii libpam0g 1.1.8-3.3
ii libseccomp2 2.3.1-2
ii libselinux1 2.5-3
ii libsystemd0 230-7
ii mount 2.28-5
ii util-linux 2.28-5
Versions of packages systemd recommends:
ii dbus 1.10.8-1
ii libpam-systemd 230-7
Versions of packages systemd suggests:
ii policykit-1 0.105-15
ii systemd-container 230-7
ii systemd-ui 3-4
Versions of packages systemd is related to:
ii udev 230-6
-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
NAutoVTs=6
ReserveVT=6
KillUserProcesses=true
KillExcludeUsers=root
InhibitDelayMaxSec=5
HandlePowerKey=poweroff
IdleAction=ignore
RemoveIPC=yes
-- no debconf information
Michael Biebl
Jul 10, 2016, 3:10:03 PM7/10/16
to
Am 10.07.2016 um 20:39 schrieb Peter Gossner:
> Package: systemd
> Version: 230-7
> Severity: important
>
> Dear Maintainer,
> Attempting to (re)understand systemd ...
> ~$ systemctl
> Failed to list units: No such method 'ListUnitsFiltered'
> other options also fail
> e.g.
> sudo systemctl try-restart exim4
> Failed to try-restart exim4.service: No such method 'TryRestartUnit'
> See system logs and 'systemctl status exim4.service' for details.
>
> I also see logind errors and have been having dbus session issues which may all be related to a pam module.
>
> At other times systemd has attempted to rename network interfaces, screw up diplay manager, hang without console access , fail to start real consoles at all deep fry kittens ...
interesting
> Package: systemd
> Version: 230-7
> Severity: important
>
> Dear Maintainer,
> Attempting to (re)understand systemd ...
> ~$ systemctl
> Failed to list units: No such method 'ListUnitsFiltered'
> other options also fail
> e.g.
> sudo systemctl try-restart exim4
> Failed to try-restart exim4.service: No such method 'TryRestartUnit'
> See system logs and 'systemctl status exim4.service' for details.
>
> I also see logind errors and have been having dbus session issues which may all be related to a pam module.
>
> At other times systemd has attempted to rename network interfaces, screw up diplay manager, hang without console access , fail to start real consoles at all deep fry kittens ...
> Init: sysvinit (via /sbin/init)
So, apparently you are still using sysvinit. Have you filed the bug
report from a different system then the one you experience the problems?
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Peter Gossner
Jul 11, 2016, 11:40:03 AM7/11/16
to
On Sun, 10 Jul 2016 22:04:14 +0200 Michael Biebl <bi...@debian.org>
wrote:
> Am 10.07.2016 um 21:26 schrieb Peter Gossner:
> > Sorry Michael this _is_ the same system,
> > I've probably failed to restore systemd after rolling back or
> > something.
> > (yes I can restart daemons with service foo or /etc/init.d )
> > I'll attempt a reinstall (with no version restrictions) and see
> > what happens.
>
>
> Ok, then your problem is actually related to *not* having systemd as
> PID 1. To fix that, run "apt install systemd-sysv".
>
> Regards,
> Michael
>
>
Did that and now systemd works as expected.
e.g.
3 [Tue Jul 12 12:48 AM] pete@mingus:~$ systemctl restart
exim4 ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to restart 'exim4.service'.
Authenticating as: Peter Gossner,2000,, (pete)
Password:
==== AUTHENTICATION COMPLETE ===
If there is a "bug" its in trying to roll back and my misunderstanding
of the shim package.
As I didn't attempt to do the roll back with any intelligence, planning
or thought at all ...
I will do nought but wonder how I got my system to that
situation.
I do bend this system a lot its sort of a test bed.
Thanks for _your help_.
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
-- Peter Gossner <gos...@internode.on.net>
Pete <pete.g...@gmail.com>
Tue 12 Jul 00:52:41 ACST 2016
"Resentment is like drinking poison and then hoping it will kill your
enemies." -- Nelson Mandela
wrote:
> Am 10.07.2016 um 21:26 schrieb Peter Gossner:
> > I've probably failed to restore systemd after rolling back or
> > something.
> > (yes I can restart daemons with service foo or /etc/init.d )
> > I'll attempt a reinstall (with no version restrictions) and see
> > what happens.
>
>
> Ok, then your problem is actually related to *not* having systemd as
> PID 1. To fix that, run "apt install systemd-sysv".
>
> Regards,
> Michael
>
>
Did that and now systemd works as expected.
e.g.
3 [Tue Jul 12 12:48 AM] pete@mingus:~$ systemctl restart
exim4 ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to restart 'exim4.service'.
Authenticating as: Peter Gossner,2000,, (pete)
Password:
==== AUTHENTICATION COMPLETE ===
If there is a "bug" its in trying to roll back and my misunderstanding
of the shim package.
As I didn't attempt to do the roll back with any intelligence, planning
or thought at all ...
I will do nought but wonder how I got my system to that
situation.
I do bend this system a lot its sort of a test bed.
Thanks for _your help_.
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
Pete <pete.g...@gmail.com>
Tue 12 Jul 00:52:41 ACST 2016
"Resentment is like drinking poison and then hoping it will kill your
enemies." -- Nelson Mandela
0 new messages