Loading...

XML

Word

Printable

JSON

Operating System:
Linux
Steps To Reproduce:

Hide

in mongod.conf, under RHEL 6 (maybe also 7), set (as described in the docs):
pidFilePath: "/dir/to/pid.file"

To "fix" it, one needs to define the value without the ticks, like:
pidFilePath: /dir/to/pid.file

Thus defining a string without the ticks, resulting in an invalid YAML file

Show
in mongod.conf, under RHEL 6 (maybe also 7), set (as described in the docs): pidFilePath: "/dir/to/pid.file" To "fix" it, one needs to define the value without the ticks, like: pidFilePath: /dir/to/pid.file Thus defining a string without the ticks, resulting in an invalid YAML file

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:
PIDFILEPATH=`awk -F'[:=]' -v IGNORECASE=1 '/^[[:blank:]](processManagement\.)?pidfilepath[[:blank:]][:=][[:blank:]]*/

{print $2}

' "$CONFIGFILE" | tr -d '[:blank:]'`
results in
$PIDFILEPATH being "/dir/to/pid.file"

PIDDIR=`dirname $PIDFILEPATH`
results in
$PIDDIR being "dir/to

which obviously causes the /etc/init.d/mongod to crash and avoids mongo to start

duplicates

SERVER-17337 RPM Init script breaks with quotes in yaml config file

is duplicated by

SERVER-17546 RHEL init.d script does not handle pidFilePath with quotes