[SERVER-33320] Changes to systemd script but no reload of unit files Created: 14/Feb/18  Updated: 29/Oct/23  Resolved: 29/Mar/18

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.4.11, 3.4.12, 3.4.13
Fix Version/s: 3.7.4

Type: Bug Priority: Minor - P4
Reporter: Max Allan Assignee: Mathew Robinson (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-33319 Systemd startup should not always be ... Closed
Backwards Compatibility: Fully Compatible
Operating System: Linux
Backport Requested:
v3.6
Steps To Reproduce:

Install a version of mongo before 3.4.11.
Use yum/rpm to upgrade to 3.4.11/12/13.
Use systemctl to stop/start mongo and it will not do so until you do the daemon-reload.
Which is fine for humans, but when your mongo installation is controlled by scripts, they get very confused that the start/stop script no longer does what it should.

Participants:
Case:

 Description   

In SERVER-31225 the systemd script was changed. But the RPM package did not get updated to add a daemon-reload

# systemctl start mongod
Warning: mongod.service changed on disk. Run 'systemctl daemon-reload' to reload units.



 Comments   
Comment by Githook User [ 29/Mar/18 ]

Author:

{'email': 'chasinglogic@gmail.com', 'name': 'Mathew Robinson', 'username': 'chasinglogic'}

Message: SERVER-33320 Run systemctl daemon-reload on upgrade
Branch: master
https://github.com/mongodb/mongo/commit/abc831b3b8c91b2f1d47777abcb8d205a987e036

Comment by Mark Agarunov [ 14/Feb/18 ]

Hello maxallan,

Thank you for the report. I've set the fixVersion to "Needs Triage" for this new feature to be scheduled against our currently planned work. Updates will be posted on this ticket as they happen.

Thanks,
Mark

Comment by Max Allan [ 14/Feb/18 ]

Apologies. I have no edit permission and couldn't set the OS field to "RedHat" when creating the ticket. Could someone with privs update it?

Generated at Thu Feb 08 04:33:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.