-
-
Notifications
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong "pidFilePath:" setting in /etc/mongodb.conf
on Debian
#647
Comments
An update to 4.2.0 has now overwritten my workaround and thus has put the This means that the handling of this setting is still broken in 4.2.0. Can this please be fixed? |
Is there a pull request for this? |
The diff is in the description above. |
I think it would be better to fix this line: puppet-mongodb/manifests/params.pp Line 60 in 94cbca3
Since we only support Debian versions that use systemd, |
/etc/mongodb.conf
on Debian
Yeah, as I wrote: My change was only a workaround. |
Hi @dhs-rec, thanks for raising the issue. We're a small collective of module authors and maintain > 150 modules. It's not possible to provide fixes for all the issues that people raise. If you like, please provide a PR with the proposed change. We're also happy to guide you through our CI system or how to write tests. Feel free to hop into our IRC channel #voxpupuli on libera.chat or #voxpupuli on https://slack.puppet.com/. |
@bastelfreak, I don't get this. Obviously, @kenyon already found the right place and what's needed to do the fix. He could as well have just committed it... |
@dhs-rec Good luck, I certainly won't be helping you get anything fixed thanks to your ungrateful attitude. |
@dhs-rec release 6.0.0 should solve this. Could you please verify? |
Sure, I'll take a look as soon as possible. Thanks a lot for the hint. |
Yes, looks good. Thanks for fixing this. |
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
There's a
pidFilePath:
setting in/etc/mongodb.conf
that shouldn't be there:which leads to a server start failure on reboots because the pidfile isn't there and the mongod process has no permission to create it.
What behaviour did you expect instead
There should be no
pidFilePath:
setting in the file at all. The (MongoDB) documentation says:and
As you can see above,
$fork
is explicitly set to "false" (the default of "undef" didn't work either). I worked around this by modifyingtemplates/mongodb.conf.2.6.erb
like so:but I guess this is really just this, a workaround...
The text was updated successfully, but these errors were encountered: