[SERVER-47478] Missing "forked process: <pid>" message on --fork startup. Created: 10/Apr/20  Updated: 29/Oct/23  Resolved: 11/Apr/20

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: 4.4.0-rc0
Fix Version/s: 4.4.0-rc1, 4.7.0

Type: Bug Priority: Blocker - P1
Reporter: Billy Donahue Assignee: Billy Donahue
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Problem/Incident
is caused by SERVER-46563 SIGUSR2 does not work with --fork Closed
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Service arch 2020-04-20
Participants:

 Description   

Message was lost in SERVER-46563, but it's needed for cloud operators to know the pid of the daemonized process.



 Comments   
Comment by Githook User [ 11/Apr/20 ]

Author:

{'name': 'Billy Donahue', 'email': 'billy.donahue@mongodb.com', 'username': 'BillyDonahue'}

Message: SERVER-47478 restore 'forked process: <pid>' message

(cherry picked from commit ab0603ff2082e7e6a5c8990908a00bda6d852ba2)
Branch: v4.4
https://github.com/mongodb/mongo/commit/02869c7db07512f9492d00fcb7544e623fd21c84

Comment by Githook User [ 10/Apr/20 ]

Author:

{'name': 'Billy Donahue', 'email': 'billy.donahue@mongodb.com', 'username': 'BillyDonahue'}

Message: SERVER-47478 restore 'forked process: <pid>' message
Branch: master
https://github.com/mongodb/mongo/commit/ab0603ff2082e7e6a5c8990908a00bda6d852ba2

Comment by Billy Donahue [ 10/Apr/20 ]

CR https://mongodbcr.appspot.com/588550003/

Comment by Billy Donahue [ 10/Apr/20 ]

Was:

about to fork child process, waiting until server is ready for connections.
forked process: 87511
all output going to: /tmp/flog.tmp
child process started successfully, parent exiting

Now (4.4.0-rc0):

about to fork child process, waiting until server is ready for connections.
child process started successfully, parent exiting

 

Generated at Thu Feb 08 05:14:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.