bigcouch sv start issue

[Johannes]

Hi,
I'm having issues starting bigcouch via "sv start bigcouch" using runit.

I installed bigcouch on three independent debian wheezy boxes. I can start all bigcouch services fine, I clusterd them together and the replicate fine... The issue I'm facing is starting bigcouch via runit using the sv command.

Sv does start bigcouch fine, but as soon, as the beam process is running, it continously tries to start up a new process (which of course fails). Checking "sv status bigcouch" shows "down".

Also in the ./supervise/ directory, the "pid" file remains empty after stating. To me it looks like sv is not getting the pid of the started bigcouch process.

I would like to start/stop bigcouch using the runit system - is there some special flag or so I need to set, to make sv get the pid of the started bigcouch process?

My /etc/sv/bigcouch/run looks like this:

#!/bin/bash
exec 2>&1
export HOME=/home/bigcouch
ulimit -n 10000
exec chpst -u bigcouch /opt/bigcouch/bin/bigcouch

anything wrong at this point?
The started bigcouch-process looks like this:

bigcouch 13996  0.0  0.1  10840   560 ?        S    10:11   0:00 /opt/bigcouch/erts-5.9.1/bin/epmd -daemon
bigcouch 13997  0.8  5.5 139628 28092 ?        Sl   10:11   0:18 /opt/bigcouch/erts-5.9.1/bin/beam.smp -K true -A 16 -Bd -- -root /opt/bigcouch -progname bigcouch -- -home /home/bigcouch -- -boot /opt/bigcouch/releases/0.4.0/bigcouch -name bigcouch@FQDN -setcookie mycookie -kernel error_logger silent inet_dist_listen_min 11500 inet_dist_listen_max 11999 -sasl sasl_error_logger false -noshell -noinput

Thanks for any help,
Johannes

[Johannes]

Is there realy nobody else experiencing this strange behaviour?
I have 4 debian wheezy nodes running bigcouch and all have the same issue. Is this debian-specific?

Regards,
Johannes