[DOCS-15869] [SERVER] Error with systemctl Created: 03/Feb/23  Updated: 13/Nov/23  Resolved: 13/Mar/23

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: 6.2.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Critical - P2
Reporter: Backlog - Core Eng Program Management Team Assignee: Dave Cuthbert (Inactive)
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-70121 Ubuntu 18 packaging tests shows error... Closed
Participants:
Days since reply: 1 year, 5 days ago

 Description   

ORIGINAL TITLE: [SERVER] Investigate changes in SERVER-70121: Ubuntu 18 packaging tests shows error with systemctl

Original Downstream Change Summary

We need to ensure that our documentation reflects the following changes in this ticket:

  • fork and pidFilePath are removed from mongod.conf
  • PIDFile and type=forking are removed from mongod.service
  • Adding fork to mongod.conf is an incompatible change under systemd, since it will disrupt systemd's ability to track the service state. Unfortunately, we don't have a good programmatic way of checking this.
  • Requesting the service PID and state should be done via systemctl instead of PID files

    Description of Linked Ticket

    https://github.com/10gen/mongo/pull/7730#discussion_r984027371

[2022/09/29 19:51:53.645] /var/lib/dpkg/info/mongodb-enterprise-unstable-server.postinst: 44: /var/lib/dpkg/info/mongodb-enterprise-unstable-server.postinst: systemctl: not found

 

Probs just needs the systemd dependency

This is probably happening for more than just this test and we should make sure it is fixed everywhere



 Comments   
Comment by Sarah Olson [ 03/Feb/23 ]

Increasing priority on this one and triaging to Ready for Work to ensure we get these changed into our documentation for the 6.2.0 release or shortly thereafter. 

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