Ok that looks strange, did you enabled the service with a symbolic link?
Take a look at our runit usage 
<http://www.voidlinux.eu/usage/runit/#enabling-a-service> 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.
>>>>>
>>>>>
>>>>>