[SERVER-9706] Init scripts overwritten during upgrades Created: 16/May/13  Updated: 15/Nov/21  Resolved: 28/Oct/13

Status: Closed
Project: Core Server
Component/s: Packaging
Affects Version/s: 2.2.4, 2.4.3
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Dan Cooper Assignee: Ernie Hershey
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS 5/6


Backwards Compatibility: Fully Compatible
Operating System: Linux
Steps To Reproduce:

Change your init script and upgrade.

Participants:

 Description   

When you upgrade from 2.2.2 to 2.2.4 or 2.4.3, the init scripts are overwritten in /etc/init.d/mongod. Some people set options in here like the replset and --shardsvr or --cfgsvr with puppet like us. During an upgrade if mongod is started before puppet pushes the right config (or people who don't use puppet and lost their config you overwrote) the mongod will not know what it should be doing like being a config server or being part of a replset.



 Comments   
Comment by Scott Hernandez (Inactive) [ 16/May/13 ]

Are you putting these options in the init script, or config file? The config file is where these types of configuration settings are meant to go.

https://github.com/mongodb/mongo/blob/master/rpm/init.d-mongod

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