[Bug 811222] New: systemctl list-system-files fails on missing file
https://bugzilla.novell.com/show_bug.cgi?id=811222 https://bugzilla.novell.com/show_bug.cgi?id=811222#c0 Summary: systemctl list-system-files fails on missing file Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: i686 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jimc@math.ucla.edu QAContact: qa-bugs@suse.de Found By: Customer Blocker: --- I did systemctl list-system-files |& less; and it maundered on stderr: Failed to issue method call: No such file or directory All other readonly actions worked, like list-units. This could only be seen if I piped stdout and stderr to a pager or to a file. With the internally spawned pager it showed a blank screen and stderr didn't make it to my TTY either. After digging involving strace -p 1, which I'll not report in detail, I found that ENOENT was no lie: /lib/systemd/system/alsasound.service was a symlink to a no longer existing file. This was a failed attempt to override /etc/init.d/alsasound so it wouldn't fail on boot, and I didn't clean up all the mess I made. After I did systemctl disable alsasound.service rm /lib/systemd/system/alsasound.service systemctl daemon-reload systemctl list-unit-files once again worked. What I would like the developers to do: A. If systemctl list-unit-files (or other action) runs into trouble, it should list the units that aren't messed up, in addition to reporting the corruption found. systemd is the one that skipped sending the non-corrupt unit info. If it just closes the connection, my admin scripts can't rely on list-unit-files to list my unit files. B. It should report as much information as feasible about what's wrong. In this case, the pathname of the expected but non-found file would have led immediately to a fix, and I think I'm the only person in my organzation who could have done the forensics to drag the clue out of hiding. I want systemd to be widely accepted, but if people think it's impossible to debug screwups, they will suppress systemd and revert to SysVinit or (worse) upstart. C. When the internally spawned pager is in use, please redirect stderr to it as well as stdout, or at least ensure that the user sees the error message(s) one way or another. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=811222
https://bugzilla.novell.com/show_bug.cgi?id=811222#c
Christian Boltz
https://bugzilla.novell.com/show_bug.cgi?id=811222
https://bugzilla.novell.com/show_bug.cgi?id=811222#c1
--- Comment #1 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=811222
https://bugzilla.novell.com/show_bug.cgi?id=811222#c
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=811222
https://bugzilla.novell.com/show_bug.cgi?id=811222#c2
Thomas Blume
https://bugzilla.novell.com/show_bug.cgi?id=811222
https://bugzilla.novell.com/show_bug.cgi?id=811222#c3
James Carter
https://bugzilla.novell.com/show_bug.cgi?id=811222
https://bugzilla.novell.com/show_bug.cgi?id=811222#c4
Thomas Blume
participants (1)
-
bugzilla_noreply@novell.com