[Bug 963971] New: remote-fs-pre.target: Job remote-fs-pre.target/start delete to break ordering cycle starting with remote-fs.target/start

older
[Bug 964926] New: Missing Cantata...

bugzilla_noreply＠novell.com

28 Jan 2016 28 Jan '16

12:16

http://bugzilla.opensuse.org/show_bug.cgi?id=963971 Bug ID: 963971 Summary: remote-fs-pre.target: Job remote-fs-pre.target/start delete to break ordering cycle starting with remote-fs.target/start Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: manfred.h@gmx.net QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Since quite some time I see varying messages about systemd having issues with remote file systems vs. nfs related services vs. name resolution services. Sometimes my NFS(4) server doesn't even start. Here is an example on the latest TW version "openSUSE Tumbleweed (20160126) (x86_64)": # journalctl | grep deleted Jan 28 12:17:05 saturn systemd[1]: remote-fs-pre.target: Job remote-fs-pre.target/start delete to break ordering cycle starting with remote-fs.target/start On some other systems I see have this: nss-lookup.target: Job nss-lookup.target/start deleted to break ordering cycle starting with rpc-statd.service/start rpc-statd.service: Job rpc-statd.service/start deleted to break ordering cycle starting with nfs-server.service/start As this is not predictable and may lead to some important services not being started, I rate this rather important. -- You are receiving this mail because: You are on the CC list for the bug.

Attachments:

attachment.htm (text/html — 3.1 KB)

Show replies by date

bugzilla_noreply＠novell.com

28 Jan 28 Jan

12:16

New subject: [Bug 963971] remote-fs-pre.target: Job remote-fs-pre.target/start delete to break ordering cycle starting with remote-fs.target/start

http://bugzilla.opensuse.org/show_bug.cgi?id=963971 Manfred Hollstein changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manfred.h@gmx.net -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:12

New subject: [Bug 963971] remote-fs-pre.target: Job remote-fs-pre.target/start delete to break ordering cycle starting with remote-fs.target/start

http://bugzilla.opensuse.org/show_bug.cgi?id=963971 http://bugzilla.opensuse.org/show_bug.cgi?id=963971#c1 --- Comment #1 from Manfred Hollstein --- Just after a reboot of this otherwise up2date system I got this: # journalctl | grep deleted Jan 28 14:09:35 saturn systemd[1]: nss-lookup.target: Job nss-lookup.target/start deleted to break ordering cycle starting with rpc-statd.service/start So, it's really not predictable, which services wins the race... :( -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

4 Feb 4 Feb

11:42

New subject: [Bug 963971] remote-fs-pre.target: Job remote-fs-pre.target/start delete to break ordering cycle starting with remote-fs.target/start

http://bugzilla.opensuse.org/show_bug.cgi?id=963971 Bernhard Wiedemann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@suse.com Assignee|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

5 Feb 5 Feb

09:11

New subject: [Bug 963971] remote-fs-pre.target: Job remote-fs-pre.target/start delete to break ordering cycle starting with remote-fs.target/start

http://bugzilla.opensuse.org/show_bug.cgi?id=963971 http://bugzilla.opensuse.org/show_bug.cgi?id=963971#c3 --- Comment #3 from Manfred Hollstein --- (In reply to Dr. Werner Fink from comment #2)

...

IMHO ther is job which does *not* belong to systemd which cause this loop!

Show the full text around

journalctl | less +/deleted

Here are the requested logs (including a few lines _before_): Feb 05 10:04:57 saturn systemd-journald[173]: Received SIGTERM from PID 1 (systemd). Feb 05 10:04:57 saturn systemd[1]: nfs-server.service: Found dependency on remote-fs-pre.target /start Feb 05 10:04:57 saturn systemd[1]: nfs-server.service: Found dependency on nfs-server.service/s tart Feb 05 10:04:57 saturn systemd[1]: nfs-server.service: Breaking ordering cycle by deleting job rpc-statd.service/start Feb 05 10:04:57 saturn systemd[1]: rpc-statd.service: Job rpc-statd.service/start deleted to break ordering cycle starting with nfs-server.service/start Feb 05 10:04:57 saturn systemd[1]: basic.target: Found ordering cycle on basic.target/start Feb 05 10:04:57 saturn systemd[1]: basic.target: Found dependency on SuSEfirewall2_init.service/start Feb 05 10:04:57 saturn systemd[1]: basic.target: Found dependency on basic.target/start Feb 05 10:04:57 saturn systemd[1]: basic.target: Breaking ordering cycle by deleting job SuSEfirewall2_init.service/start Feb 05 10:04:57 saturn systemd[1]: SuSEfirewall2_init.service: Job SuSEfirewall2_init.service/start deleted to break ordering cycle starting with basic.target/start Feb 05 10:04:57 saturn systemd[1]: Stopped Switch Root. Feb 05 10:04:57 saturn systemd[1]: Cannot find unit for notify message of PID 173. Feb 05 10:04:57 saturn systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart. Feb 05 10:04:57 saturn systemd[1]: Stopped Journal Service. Feb 05 10:04:57 saturn systemd[1]: Mounting POSIX Message Queue File System... Feb 05 10:04:57 saturn systemd[1]: Listening on RPCbind Server Activation Socket. Feb 05 10:04:57 saturn systemd[1]: Reached target RPC Port Mapper. Feb 05 10:04:57 saturn systemd[1]: Mounting Huge Pages File System... Feb 05 10:04:57 saturn systemd[1]: Starting Load Kernel Modules... Feb 05 10:04:57 saturn systemd[1]: Created slice User and Session Slice. Feb 05 10:04:57 saturn systemd[1]: Listening on Syslog Socket. Feb 05 10:04:57 saturn systemd[1]: Starting Journal Service... Feb 05 10:04:57 saturn systemd[1]: Starting Create list of required static device nodes for the current kernel... Feb 05 10:04:57 saturn systemd[1]: Listening on udev Kernel Socket. Feb 05 10:04:57 saturn systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. Feb 05 10:04:57 saturn systemd[1]: Mounting Debug File System... Feb 05 10:04:57 saturn systemd[1]: Created slice system-getty.slice. Feb 05 10:04:57 saturn systemd[1]: Mounting NFSD configuration filesystem... Feb 05 10:04:57 saturn systemd[1]: Starting Rule generator for /dev/root symlink... Feb 05 10:04:57 saturn systemd[1]: Created slice system-systemd\x2dfsck.slice. Feb 05 10:04:57 saturn systemd[1]: Listening on udev Control Socket. Feb 05 10:04:57 saturn systemd[1]: Reached target Slices. Feb 05 10:04:57 saturn systemd[1]: Listening on Device-mapper event daemon FIFOs. ... and so on -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13 Feb 13 Feb

08:06

New subject: [Bug 963971] remote-fs-pre.target: Job remote-fs-pre.target/start delete to break ordering cycle starting with remote-fs.target/start

http://bugzilla.opensuse.org/show_bug.cgi?id=963971 http://bugzilla.opensuse.org/show_bug.cgi?id=963971#c5 --- Comment #5 from Manfred Hollstein --- FWIW, I updated my systems to snapshot 20160209 yesterday, but the behaviour remains unfortunately. It is absolutely random as to which service gets deleted, this time it was the nfs-server :( too bad. Here again an excerpt from the logs: Feb 13 08:51:05 melmac systemd[1]: Detected architecture x86-64. Feb 13 08:51:05 melmac audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=haveged comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Feb 13 08:51:05 melmac systemd[1]: Set hostname to <melmac>. Feb 13 08:51:05 melmac audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostnam e=? addr=? terminal=? res=success' Feb 13 08:51:05 melmac systemd[1]: nss-lookup.target: Dependency Before=nss-lookup.target dropped Feb 13 08:51:05 melmac audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname =? addr=? terminal=? res=success' Feb 13 08:51:05 melmac systemd[1]: gssproxy.service: Cannot add dependency job, ignoring: Unit gssproxy.service failed to load: No such file or directory. Feb 13 08:51:05 melmac audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=initrd-switch-root comm="systemd" exe="/usr/lib/systemd/systemd" hostn ame=? addr=? terminal=? res=success' Feb 13 08:51:05 melmac systemd[1]: remote-fs-pre.target: Found ordering cycle on remote-fs-pre.target/start Feb 13 08:51:05 melmac audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=initrd-switch-root comm="systemd" exe="/usr/lib/systemd/systemd" hostna me=? addr=? terminal=? res=success' Feb 13 08:51:05 melmac systemd[1]: remote-fs-pre.target: Found dependency on nfs-server.service/start Feb 13 08:51:05 melmac audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostnam e=? addr=? terminal=? res=success' Feb 13 08:51:05 melmac systemd[1]: remote-fs-pre.target: Found dependency on rpc-statd.service/start Feb 13 08:51:05 melmac audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname =? addr=? terminal=? res=success' Feb 13 08:51:05 melmac systemd[1]: remote-fs-pre.target: Found dependency on nss-lookup.target/start Feb 13 08:51:05 melmac audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dm-event comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr =? terminal=? res=success' Feb 13 08:51:05 melmac systemd[1]: remote-fs-pre.target: Found dependency on named.service/start Feb 13 08:51:05 melmac audit: CONFIG_CHANGE audit_enabled=1 old=1 auid=4294967295 ses=4294967295 res=1 Feb 13 08:51:05 melmac systemd[1]: remote-fs-pre.target: Found dependency on remote-fs.target/start Feb 13 08:51:05 melmac audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostn ame=? addr=? terminal=? res=success' Feb 13 08:51:05 melmac systemd[1]: remote-fs-pre.target: Found dependency on remote-fs-pre.target/start Feb 13 08:51:05 melmac audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hos tname=? addr=? terminal=? res=success' Feb 13 08:51:05 melmac systemd[1]: remote-fs-pre.target: Breaking ordering cycle by deleting job nfs-server.service/start Feb 13 08:51:05 melmac audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=kmod-static-nodes comm="systemd" exe="/usr/lib/systemd/systemd" hostna me=? addr=? terminal=? res=success' Feb 13 08:51:05 melmac systemd[1]: nfs-server.service: Job nfs-server.service/start deleted to break ordering cycle starting with remote-fs-pre.target/start -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:57

New subject: [Bug 963971] remote-fs-pre.target: Job remote-fs-pre.target/start delete to break ordering cycle starting with remote-fs.target/start

http://bugzilla.opensuse.org/show_bug.cgi?id=963971 http://bugzilla.opensuse.org/show_bug.cgi?id=963971#c6 --- Comment #6 from Manfred Hollstein --- Created attachment 665533 --> http://bugzilla.opensuse.org/attachment.cgi?id=665533&action=edit Patch to fix the ordering problem(s) Werner was spot on in comment #4. When I compared files between Tumbleweed and Leap_42.1 I found the following entry in bind's changelog interesting: * Mon Sep 28 2015 max@suse.com - Remove the start/stop dependency of named and lwresd on remote-fs to break a service dependency cycle (bsc#947483). With this small patch applied I do not see any ordering issues anymore and all services which should start at boot actually do so now ;) Please apply. -- You are receiving this mail because: You are on the CC list for the bug.

3003

Age (days ago)

3019

Last active (days ago)

List overview

Download

6 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com