[SERVER-9239] Mongo Server does not close stdout when using --fork and --syslog Created: 04/Apr/13  Updated: 11/Jul/16  Resolved: 11/Jul/13

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: 2.2.4, 2.4.1
Fix Version/s: 2.5.1

Type: Bug Priority: Critical - P2
Reporter: Benedikt Waldvogel Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: pull-request
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux


Issue Links:
Duplicate
duplicates SERVER-10084 Logging infrastructure improvements f... Closed
Related
related to SERVER-966 Mongo Server does not close stdin/std... Closed
related to SERVER-5092 Better named logging with tracing Closed
Operating System: ALL
Participants:

 Description   

The mongod server does not daemonize correctly when using --fork and --syslog: It does not close stdout.

This bug causes a hang when starting mongod via SSH:

# ssh hostname "mongod --fork --syslog ..."

Pretty much the same bug already existed and was fixed in an older version of MongoDB (without --syslog): SERVER-966



 Comments   
Comment by Andy Schwerin [ 11/Jul/13 ]

Resolved coincidentally by SERVER-10084.

Comment by Benedikt Waldvogel [ 04/Apr/13 ]

My proposed fix: https://github.com/mongodb/mongo/pull/408

Generated at Thu Feb 08 03:19:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.