[SERVER-27241] Cannot write pid file to /var/run/mongodb/mongod.pid: No such file or directory Created: 30/Nov/16  Updated: 28/Nov/18  Resolved: 07/Dec/16

Status: Closed
Project: Core Server
Component/s: Packaging
Affects Version/s: 3.4.0
Fix Version/s: 3.4.1, 3.5.1

Type: Bug Priority: Major - P3
Reporter: Stephen Lynx Assignee: Brian Samek
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by DOCS-9417 Comment on: "manual/tutorial/install-... Closed
is duplicated by SERVER-27293 mongod.service fails to start after r... Closed
is duplicated by SERVER-27319 After reboot cannot write pid file to... Closed
is duplicated by SERVER-27453 mongod 3.4 and centos7 Closed
Related
related to SERVER-38232 Mongod on Ubuntu 16/18 does not creat... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Steps To Reproduce:

Install 3.4 on centOS 7, run systemctl enable mongod, restart the system.

Sprint: Build 2016-12-12
Participants:
Case:

 Description   

For some reason, CentOS 7 is deleting the /var/run/mongodb directory on reboot and mongodb isn't creating it before trying to boot.

So what happens is that it isn`t able to boot when the system does.



 Comments   
Comment by Githook User [ 07/Dec/16 ]

Author:

{u'username': u'bsamek', u'name': u'Brian Samek', u'email': u'brian.samek@mongodb.com'}

Message: SERVER-27241 Create runtime directory on service start

(cherry picked from commit e7a503b2b993a387a52133ad37e8976e9cd2ab07)
Branch: v3.4
https://github.com/mongodb/mongo/commit/b9705586bf64597f325539d4e065bb58603f11e5

Comment by Githook User [ 07/Dec/16 ]

Author:

{u'username': u'bsamek', u'name': u'Brian Samek', u'email': u'brian.samek@mongodb.com'}

Message: SERVER-27241 Create runtime directory on service start
Branch: master
https://github.com/mongodb/mongo/commit/e7a503b2b993a387a52133ad37e8976e9cd2ab07

Comment by Stephen Lynx [ 05/Dec/16 ]

Got it.

Comment by Ernie Hershey [ 05/Dec/16 ]

Hi stephenlynx - the "3.5 desired" version is basically only tracking where this issue fits into our current development release series plans. We'll probably have to fix this first in the 3.5 development release series and backport the fix to previous release series, such as 3.4, which would land the fix in a specific point release such as 3.4.1.

Comment by Stephen Lynx [ 02/Dec/16 ]

3.5 desired? Can't it make into a 3.4 patch? Like 3.4.1?

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