Hi,
Adam Williamson at RedHat suggested I post here, so please don't be too hard on me.
I have a couple of systemd units which are reported as in error:
------------------------------------------ [palooka@f15 ~]$ systemctl list-units --all --no-pager|grep error ip6tables.service error inactive dead ip6tables.service livesys-late.service error inactive dead livesys-late.service [palooka@f15 ~]$ sudo systemctl disable ip6tables.service Couldn't find ip6tables.service. [palooka@f15 ~]$ sudo systemctl disable livesys-late.service Couldn't find livesys-late.service. [palooka@f15 ~]$ ------------------------------------------
ip6tables is not installed on my system, and I know that livesys-late is a remnant of having installed from a Live CD.
As can be seen above, when I try to "disable" them, systemctl tells me that it can't find these services. So what I want to know is why are they being reported as in error, and how can I delete them, or otherwise remove them from the scope of systemctl?
Adam suggested I look for broken symlinks in /etc/systemd/system, but I see nothing untoward there:
------------------------------------------- [palooka@f15 system]$ pwd /etc/systemd/system [palooka@f15 system]$ ls -lR .: total 24 lrwxrwxrwx. 1 root root 42 Apr 8 22:33 dbus-org.freedesktop.NetworkManager.service -> /lib/systemd/system/NetworkManager.service lrwxrwxrwx 1 root root 36 May 18 20:52 default.target -> /lib/systemd/system/graphical.target drwxr-xr-x. 2 root root 4096 Apr 8 22:33 default.target.wants drwxr-xr-x. 2 root root 4096 Apr 8 22:33 getty.target.wants drwxr-xr-x. 2 root root 4096 May 18 20:18 graphical.target.wants drwxr-xr-x. 2 root root 4096 May 21 22:43 multi-user.target.wants drwxr-xr-x. 2 root root 4096 Apr 8 22:33 network.target.wants drwxr-xr-x. 2 root root 4096 Apr 8 22:33 sysinit.target.wants
./default.target.wants: total 0 lrwxrwxrwx. 1 root root 53 Apr 8 22:33 systemd-readahead-collect.service -> /lib/systemd/system/systemd-readahead-collect.service lrwxrwxrwx. 1 root root 52 Apr 8 22:33 systemd-readahead-replay.service -> /lib/systemd/system/systemd-readahead-replay.service
./getty.target.wants: total 0 lrwxrwxrwx. 1 root root 34 Apr 8 22:33 getty@tty1.service -> /lib/systemd/system/getty@.service lrwxrwxrwx. 1 root root 34 Apr 8 22:33 getty@tty2.service -> /lib/systemd/system/getty@.service lrwxrwxrwx. 1 root root 34 Apr 8 22:33 getty@tty3.service -> /lib/systemd/system/getty@.service lrwxrwxrwx. 1 root root 34 Apr 8 22:33 getty@tty4.service -> /lib/systemd/system/getty@.service lrwxrwxrwx. 1 root root 34 Apr 8 22:33 getty@tty5.service -> /lib/systemd/system/getty@.service lrwxrwxrwx. 1 root root 34 Apr 8 22:33 getty@tty6.service -> /lib/systemd/system/getty@.service
./graphical.target.wants: total 0 lrwxrwxrwx. 1 root root 49 Apr 8 22:33 system-setup-keyboard.service -> /lib/systemd/system/system-setup-keyboard.service
./multi-user.target.wants: total 0 lrwxrwxrwx. 1 root root 33 Apr 8 22:33 crond.service -> /lib/systemd/system/crond.service lrwxrwxrwx 1 root root 38 May 18 21:27 irqbalance.service -> /lib/systemd/system/irqbalance.service lrwxrwxrwx. 1 root root 42 Apr 8 22:33 NetworkManager.service -> /lib/systemd/system/NetworkManager.service lrwxrwxrwx. 1 root root 35 Apr 8 22:33 ntpdate.service -> /lib/systemd/system/ntpdate.service lrwxrwxrwx 1 root root 32 May 21 22:43 ntpd.service -> /lib/systemd/system/ntpd.service lrwxrwxrwx. 1 root root 36 Apr 8 22:33 remote-fs.target -> /lib/systemd/system/remote-fs.target lrwxrwxrwx. 1 root root 35 Apr 8 22:33 rsyslog.service -> /lib/systemd/system/rsyslog.service
./network.target.wants: total 0 lrwxrwxrwx. 1 root root 42 Apr 8 22:33 NetworkManager.service -> /lib/systemd/system/NetworkManager.service
./sysinit.target.wants: total 0 lrwxrwxrwx. 1 root root 40 Apr 8 22:33 hwclock-load.service -> /lib/systemd/system/hwclock-load.service [palooka@f15 system]$ --------------------------------------
Is there a problem?
On 05/25/2011 04:05 PM, Paul Brewer wrote:
ip6tables is not installed on my system, and I know that livesys-late is a remnant of having installed from a Live CD.
I see livesys-late on my anaconda installed systems too.
I have some other fun ones:
VMware.service error inactive dead VMware.service
And various "target" ones:
ypbind.target error inactive dead ypbind.target
Definitely not using that (not installed).
On Wed, 25.05.11 23:05, Paul Brewer (walterhurry@gmail.com) wrote:
Hi,
Adam Williamson at RedHat suggested I post here, so please don't be too hard on me.
I have a couple of systemd units which are reported as in error:
[palooka@f15 ~]$ systemctl list-units --all --no-pager|grep error ip6tables.service error inactive dead ip6tables.service livesys-late.service error inactive dead livesys-late.service [palooka@f15 ~]$ sudo systemctl disable ip6tables.service Couldn't find ip6tables.service. [palooka@f15 ~]$ sudo systemctl disable livesys-late.service Couldn't find livesys-late.service. [palooka@f15 ~]$
Those services are simply referenced by other units, but we couldn't load them because they didnt exist on disk, which we indicate in the second column which is "error" for them. The second columns refers to the "load state", i.e. whether a unit could be loaded successfully.
To make this less confusing we actually hide them on output. But you turned that off by using "--all", i.e. you asked explicitly to see them.
BTW, systemctl is smart enough to detect whether it outputs on a terminal and will not do autopaging if you pipe it to something else, i.e. drop --no-pager in the command line above.
As can be seen above, when I try to "disable" them, systemctl tells me that it can't find these services. So what I want to know is why are they being reported as in error, and how can I delete them, or otherwise remove them from the scope of systemctl?
Is there a problem?
No. ;-)
Lennart