-
Type: Bug
-
Resolution: Fixed
-
Priority: Critical - P2
-
Affects Version/s: 3.4.22, 4.0.11
-
Component/s: Packaging
-
None
-
Fully Compatible
-
ALL
-
v4.0, v3.6, v3.4
-
- Install version 4.0.11 of mongodb-org-server
- Check the file /lib/systemd/system/mongod.service
- Note the `After` and "WantedBy" target.
- Compare with 4.0.10
-
(copied to CRM)
I have noticed that in the version 4.0.11 the service file for systemd changed and introduced a cyclic dependcy.
As it seems the "After" target has been changed in this version. Previously it was
After=network.target
and now it is
After=multi-user.target
This is an issue because the multi-user target is also set as the wanted by target:
WantedBy=multi-user.target
This creates cyclic depencies and from what I have noticed the order in which systemd fixes this cyclic depency seems to be somewhat random. This prevents all services depending on mongod.service to start at all and also seems to be randomly preventing other services from starting.
Once the system is up, all services can be started manully by hand, so it "only" affects the startup order. But since this definately breaks systems I've given it the priority "Critical - P2"
- is caused by
-
SERVER-36043 systemd unit for mongod starts before multi.user target
- Closed
- is duplicated by
-
SERVER-42716 Incorrect dependency on multi-user.target causes dependency loop for systemd
- Closed