Bluepill fails to create process silently #53
Description
I have a problem where I load a bluepill file and rather than bluepill creating the process and monitoring the new pid, it reports pid of zero. Bluepill is running as root, but dropping privileges to a non-privileged user for the created process.
Some more details:
- The pid file shows an actual pid number and a sock file is generated. Notice that the journals are not created.
find /var/run/bluepill/ | grep myapp
/var/run/bluepill/pids/myapp.pid
/var/run/bluepill/pids/myapp
/var/run/bluepill/socks/myapp.sock
/var/run/bluepill/pids/myapp.pid
10602
- The bluepill log shows a pid as well, but doesn't report any stats. Missing stats makes sense because there is no process matching the pid
bluepilld[10602]: [myapp:sidekiq] cpu_usage: [0.0, 0.0, 0.0, 0.0, 0.0]
bluepilld[10602]: [myapp:sidekiq] mem_usage: [0KB, 0KB, 0KB, 0KB, 0KB]
bluepilld[10602]: [myapp:sidekiq] mem_usage: [0KB, 0KB, 0KB]
bluepilld[10602]: [myapp:sidekiq] cpu_usage: [0.0, 0.0, 0.0, 0.0]
bluepilld[10602]: [myapp:sidekiq] mem_usage: [0KB, 0KB, 0KB, 0KB]
bluepilld[10602]: [myapp:sidekiq] cpu_usage: [0.0, 0.0, 0.0, 0.0, 0.0]
- And finally bluepill status reports pid 0, but there is not a process created.
bluepill myapp status
myapp:sidekiq(pid:0): up
Any hints or tips to troubleshoot further? Is there any way to get more verbosity into this logging?