On Mon, Mar 7, 2016 at 1:49 PM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
07.03.2016 21:41, Greg Freemyer пишет:
The destination does not exist (it used to).
But ignoring that rather big issue, why does a failed mount of a tertiary filesystem cause systemd to crash and burn.
Because all mount points in /etc/fstab are mandatory unless marked as optional. There is nothing new - countless number of times I had to "fix" server that stayed in "rescue mode" because someone removed access to SAN storage but forgot to edit fstab. Without any systemd involved.
Andrei, Would a bugzilla asking for a more descriptive error log be accepted? All I got was this one liner: Mar 06 19:14:51 cloud1 mount[1633]: mount: /srv_new/portal_backup_container: failed to setup loop device: No such file or directory It would be nice to see something like: "THE ABOVE FAILED MOUNT TRIGGERED SYSTEMD MAINTENANCE MODE:" Instead, the one liner was lost in a clutter of hundreds of lines of output in the journal. In fact I started with 500 lines of Journal logs that occurred near the failure. I whittled that down to these before I found the issue, but nothing in the below jumps out at me as a "MAJOR PROBLEM, MUST FIX BEFORE COMPUTER IS USABLE" type of log entry. In fact nothing in the logs even says systemd maintenance mode is being entered. ================ Mar 06 19:10:59 cloud1 clamd[1489]: SelfCheck: Database status OK. Mar 06 19:14:10 cloud1 sudo[1620]: gaf : TTY=pts/0 ; PWD=/home/gaf ; USER=root ; COMMAND=/usr/bin/vi /usr/lib/systemd/system/systemd-udev-root-symlink.service Mar 06 19:14:51 cloud1 systemd[1]: Cannot add dependency job for unit systemd-udev-root-symlink.service, ignoring: Unit systemd-udev-root-symlink.service failed to load: Invalid argument. See system logs and 'systemctl status systemd-udev-root-symlink.service' for details. Mar 06 19:14:51 cloud1 mount[1633]: mount: /srv_new/portal_backup_container: failed to setup loop device: No such file or directory Mar 06 19:14:51 cloud1 systemd[1]: Failed to mount /home/portal_backup/portal_backup. Mar 06 19:14:51 cloud1 systemd[1]: Dependency failed for Local File Systems. Mar 06 19:14:52 cloud1 xinetd[1015]: Exiting... Mar 06 19:14:52 cloud1 dbus[502]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' Mar 06 19:14:52 cloud1 dbus[502]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.login1.service': Refusing activation, D-Bus is shutting down. Mar 06 19:14:52 cloud1 login[1335]: pam_systemd(login:session): Failed to release session: Refusing activation, D-Bus is shutting down. Mar 06 19:14:53 cloud1 wickedd-dhcp4[565]: eth0: Request to release DHCPv4 lease with UUID 7ec4dc56-e344-0300-3702-000004000000 Mar 06 19:14:54 cloud1 systemd-journal[288]: Forwarding to syslog missed 1 messages. -- Subject: One or more messages could not be forwarded to syslog -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- One or more messages could not be forwarded to the syslog service -- running side-by-side with journald. This usually indicates that the -- syslog implementation has not been able to keep up with the speed of -- messages queued. Mar 06 19:14:54 cloud1 systemd[1379]: pam_unix(systemd-user:session): session closed for user gaf Mar 06 19:14:56 cloud1 wickedd[567]: ni_process_reap: process 1932 has not exited yet; now doing a blocking waitpid() Mar 06 19:14:56 cloud1 wicked[1640]: eth0 device-ready Mar 06 19:14:56 cloud1 wicked[1640]: eth1 device-ready Mar 06 19:14:57 cloud1 freshclam[1232]: Update process terminated Mar 06 19:16:31 cloud1 SuSEfirewall2[1974]: Not unloading firewall rules at system shutdown ============== Thanks Greg -- Greg Freemyer www.IntelligentAvatar.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org