[SERVER-1953] Cannot control mongodb process via service in Ubuntu when started with --fork Created: 16/Oct/10  Updated: 19/May/14  Resolved: 01/Mar/11

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

Type: Bug Priority: Minor - P4
Reporter: Andrei Zmievski Assignee: Richard Kreuter (Inactive)
Resolution: Won't Fix Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 10.04


Operating System: Linux
Participants:

 Description   

mongodb-stable package installed from 10gen repo. I can
start the service fine with 'service mongodb start', but neither
'service mongodb status' nor 'service mongodb restart' seem to work:

root@db01:/var/log$ service mongodb status
mongodb stop/waiting
root@db01:/var/log$ service mongodb restart
restart: Unknown instance:
root@db01:/var/log$ ps ax G mongodb

17605 ? Sl 0:00 /usr/bin/mongod --config /etc/mongodb.conf

The config is pretty bare:
dbpath = /data/mongo/db
logpath = /data/mongo/logs/mongodb.log
logappend = true
fork = true
directoryperdb = true
rest = true

The discussion linked to below indicates that this is because of "fork = true" setting.

http://groups.google.com/group/mongodb-user/browse_thread/thread/0c074b6a11eac29b



 Comments   
Comment by Richard Kreuter (Inactive) [ 01/Mar/11 ]

While it might be possible to add code to the upstart file to parse your config file, that'd be more clutter for an odd edge case. (Note that the packages we ship do not enable fork in the config file.)

Generated at Thu Feb 08 02:58:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.