NFSd does not start due to systemd ordering cycle with setserial
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
setserial (Debian) |
Fix Released
|
Unknown
|
|||
setserial (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Vivid |
Fix Released
|
High
|
Unassigned | ||
Wily |
Fix Released
|
High
|
Martin Pitt |
Bug Description
NFSd does not start due to systemd ordering cycle.
Manually starting with "systemctl start nfs-kernel-server" after boot works fine.
here systemd lines from dmesg:
[ 43.569341] systemd[1]: Cannot add dependency job for unit gssproxy.service, ignoring: Unit gssproxy.service failed to load: No such file or directory.
[ 43.595080] systemd[1]: Found ordering cycle on nfs-server.
[ 43.620748] systemd[1]: Found dependency on network.
[ 43.646476] systemd[1]: Found dependency on NetworkManager.
[ 43.672292] systemd[1]: Found dependency on basic.target/start
[ 43.697952] systemd[1]: Found dependency on sockets.
[ 43.723381] systemd[1]: Found dependency on cups.socket/start
[ 43.748530] systemd[1]: Found dependency on sysinit.
[ 43.773533] systemd[1]: Found dependency on setserial.
[ 43.798185] systemd[1]: Found dependency on remote-
[ 43.822739] systemd[1]: Found dependency on remote-
[ 43.871768] systemd[1]: Found dependency on nfs-server.
[ 43.896442] systemd[1]: Breaking ordering cycle by deleting job network.
[ 43.921641] systemd[1]: Job network.
SRU test case
=============
- Install network-manager, nfs-kernel-server, and setserial into a clean vivid VM.
- Reboot, and you'll find the above ordering cycle (check "sudo journalctl -p warning"). "systemctl status nfs-server.service" will be not running (it could also be that the cycle gets broken on a different point, but that's the most likely one).
- With the fixed setserial package (upgrade, then reboot) there should be no cycle and all services start up normally.
- Double-check "systemctl status setserial" that the unit started and output from the init.d script looks reasonable.
Regression potential: The new .service has less strict startup dependencies/
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: nfs-kernel-server 1:1.2.8-9ubuntu8.1
Uname: Linux 4.1.0-040100rc1
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 7 12:26:09 2015
InstallationDate: Installed on 2012-12-22 (865 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
SourcePackage: nfs-utils
UpgradeStatus: Upgraded to vivid on 2015-04-23 (13 days ago)
tags: | added: systemd-boot |
Changed in setserial (Debian): | |
status: | Unknown → New |
Changed in setserial (Debian): | |
status: | New → Incomplete |
Changed in setserial (Debian): | |
status: | Incomplete → New |
Changed in setserial (Debian): | |
status: | New → Fix Released |
I wonder if some update arrived between the bug reporting...
After reboot: service/ start target/ start service/ start
[ 43.777385] systemd[1]: Found dependency on nfs-server.
[ 43.803123] systemd[1]: Found dependency on network.
[ 43.828678] systemd[1]: Breaking ordering cycle by deleting job NetworkManager.
the rpcinfo shows it started OK.