From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 24 Aug 2015 06:13:06 -0700 (PDT) From: Duncaen To: voidlinux Message-Id: <089c20dd-21cf-4ca6-8550-80eb49077bb9@googlegroups.com> In-Reply-To: <6dd7013e-df82-41d6-8f8f-04616c482aaf@googlegroups.com> References: <13ff9ce8-8ea5-4bce-9900-24216b873201@googlegroups.com> <584429aa-31b2-41a0-a447-82a5a1d9351d@googlegroups.com> <8c5d2b0b-4886-4854-91b3-332c56ea7161@googlegroups.com> <6dd7013e-df82-41d6-8f8f-04616c482aaf@googlegroups.com> Subject: Re: Mongodb not started by runit MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_60_2086458211.1440421987039" ------=_Part_60_2086458211.1440421987039 Content-Type: multipart/alternative; boundary="----=_Part_61_1825380525.1440421987039" ------=_Part_61_1825380525.1440421987039 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Ok that looks strange, did you enabled the service with a symbolic link? Take a look at our runit usage page. Am Montag, 24. August 2015 15:08:25 UTC+2 schrieb Frankie Wild: > > Thanks, here is the output of the latter. Still no clue, I haven't changed > anything in the default mongodb.conf. > > runsvdir -P /run/runit/runsvdir/current log: xist runsv mongodb: fatal: > unable to start ./run: file does not exist runsv mongodb: fatal: unable to > start > > > On Monday, August 24, 2015 at 4:01:06 PM UTC+3, Duncaen wrote: >> >> Try "ps -ef | grep runsvdir" and checkout the last bit of the runsvdir >> process, there should be an error message. >> >> Am Montag, 24. August 2015 14:56:07 UTC+2 schrieb Frankie Wild: >>> >>> sudo sv start mongodb >>> timeout: down: mongodb: 0s, normally up, want up >>> >>> >>> On Monday, August 24, 2015 at 3:33:41 PM UTC+3, Duncaen wrote: >>>> >>>> I dont know what you are doing, could you provide the commands and the >>>> output you get. >>>> >>>> Am Montag, 24. August 2015 14:19:36 UTC+2 schrieb Frankie Wild: >>>>> >>>>> So here is the story. I have installed mongodb and added it to >>>>> /var/service/ but it's down after a reboot. It timeouts when trying to load >>>>> it manually. >>>>> >>>>> The var/log/mongodb folder is empty... >>>>> >>>>> Has anyone experienced this or got a suggestion ? >>>>> >>>>> Thanks. >>>>> >>>>> >>>>> ------=_Part_61_1825380525.1440421987039 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Ok that looks strange, did you enabled the service with a = symbolic link?
Take a look at our runit usage page.

Am Montag, 24. A= ugust 2015 15:08:25 UTC+2 schrieb Frankie Wild:
Thanks, here is the output of the la= tter. Still no clue, I haven't changed anything in the default mongodb.= conf.

runsvdir -P /run/runit/runsvdir/current log: xist= runsv mongodb: fatal: unable to start ./run: file does not exist runsv mon= godb: fatal: unable to start


On Monday, August 24, 2= 015 at 4:01:06 PM UTC+3, Duncaen wrote:
Try "ps -ef | grep runsvdir" and checkout th= e last bit of the runsvdir process, there should be an error message.
Am Montag, 24. August 2015 14:56:07 UTC+2 schrieb Frankie Wild:
sudo sv start mongodb
timeout: down: mongodb: 0s, normally up, want up


On Monday, August 24, 2015 at 3:33:41 PM UTC+3, Duncaen wrote:
I dont know what you are= doing, could you provide the commands and the output you get.

Am Mo= ntag, 24. August 2015 14:19:36 UTC+2 schrieb Frankie Wild:
So here is the story. I have instal= led mongodb and added it to /var/service/ but it's down after a reboot.= It timeouts when trying to load it manually.

The var/lo= g/mongodb folder is empty...

Has anyone experience= d this or got a suggestion ?

Thanks.

------=_Part_61_1825380525.1440421987039-- ------=_Part_60_2086458211.1440421987039--