[SERVER-17389] YAML pidFilePath not handled correctly on RHEL / CentOS 6 Created: 26/Feb/15 Updated: 12/Mar/15 Resolved: 26/Feb/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Packaging |
| Affects Version/s: | 3.0.0-rc8, 3.0.0-rc9, 3.0.0-rc10, 3.0.0-rc11 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthieu Rigal | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | centos, rhel6 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS / RHEL 6 (and maybe 7) |
||
| Issue Links: |
|
||||||||||||
| Operating System: | Linux | ||||||||||||
| Steps To Reproduce: | in mongod.conf, under RHEL 6 (maybe also 7), set (as described in the docs): To "fix" it, one needs to define the value without the ticks, like: Thus defining a string without the ticks, resulting in an invalid YAML file |
||||||||||||
| Participants: | |||||||||||||
| Description |
|
In RHEL 6, when setting up a YAML configuration file, if you enter the expected string value for pidFilePath, as described in the docs(http://docs.mongodb.org/manual/reference/configuration-options/#processManagement.pidFilePath), mongo won't start. the awk parsing or the subsequent 'dirname' call will cause the $PIDDIR variable to have a trailing tick The following: ' "$CONFIGFILE" | tr -d '[:blank:]'` PIDDIR=`dirname $PIDFILEPATH` which obviously causes the /etc/init.d/mongod to crash and avoids mongo to start |