[SERVER-34123] mongod fork mode not respecting default conf file Created: 25/Mar/18  Updated: 27/Oct/23  Resolved: 26/Mar/18

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Maxi Dev Assignee: Ramon Fernandez Marina
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

mongod when launched with fork mode but not conf file specified not using /etc/mongod.conf (Ubuntu 16.04) but also exposing default port to public ip.
tested on:
MongoDb 3.4
Ubuntu 16.04
Command: mongod --fork --logpath /var/log/mongodb/mongod.log --dbpath /var/lib/mongodb



 Comments   
Comment by Ramon Fernandez Marina [ 26/Mar/18 ]

maxidev, by default mongod doesn't load a configuration file, but uses built-in defaults. The configuration file is provided for use with init scripts.

MongoDB 3.4 does listen on 0.0.0.0 by default. This behavior was changed in MongoDB 3.6 to only listen on localhost – see SERVER-28229.

If you want to control the addresses to bind to from the command line please take a look at the --bind_ip command line option documentation.

Regards,
Ramón.

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