[SERVER-30230] Detailed error message when mongod fails to start to because systemLog.path points to a directory Created: 19/Jul/17  Updated: 30/Oct/23  Resolved: 07/Aug/17

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

Type: Improvement Priority: Major - P3
Reporter: Andrey Brindeyev Assignee: Spencer Jackson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Platforms 2017-08-21
Participants:
Case:

 Description   

When mongod have directory instead of file in the systemLog.path configuration option, the error message on RHEL-style Linux distros isn't explicit about the failure and the directory itself is empty. This confuses the customer:

about to fork child process, waiting until server is ready for connections.
forked process: 37600
ERROR: child process failed, exited with error number 1



 Comments   
Comment by Githook User [ 07/Aug/17 ]

Author:

{'username': 'spencerjackson', 'email': 'spencer.jackson@mongodb.com', 'name': 'Spencer Jackson'}

Message: SERVER-30230: Instruct to disable 'fork' for info on failed startup
Branch: master
https://github.com/mongodb/mongo/commit/ed444f830015b1241d999442865053b6bb992c6c

Comment by Spencer Jackson [ 01/Aug/17 ]

I'm thinking of appending a line to this output, to the effect of:

To see additional information in the console, start the server without the 'fork' option.

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