"There are no running bluepill daemons", even though there are.

[Denis Dervisevic]

I posted this on github as well but maybe there are more active users here, could be user error.

Hey, I've been fiddling with bluepill and currently running it in --no-privileged mode but running into a strange issue. Even tho it's working, i can't run commands on the bluepill process. Tried both 0.0.55 and 0.0.60. I'll run some commands below to show you my process.

$ bluepill load deploybs.pill --no-privileged

$ ps aux | grep 'bluepill\|rake'

shop      8149  0.6  0.3  71048 15988 ?        Sl   09:17   0:00 bluepilld: bs                                                                                                                                             

shop      8159  5.4  0.9 140404 40608 ?        Sl   09:17   0:01 /usr/local/rvm/gems/ruby-1.9.3-p374@global/bin/rake 

So clearly it has worked, it started the process and the server is up. The log is as expected and is as follows: 

shop@bullshit1:/usr/local/bullshit$ cat bluepill.log 

E, [2013-02-12T09:17:23.398778 #8149] ERROR -- : [bs:bsr] Failed to signal process 8112 with code 0: No such process

E, [2013-02-12T09:17:23.399840 #8149] ERROR -- : [bs:bsr] Failed to signal process 8112 with code 0: No such process

E, [2013-02-12T09:17:23.400018 #8149] ERROR -- : [bs:bsr] Failed to signal process 8112 with code 0: No such process

W, [2013-02-12T09:17:23.400370 #8149]  WARN -- : [bs:bsr] Executing start command: rake bs:start

I, [2013-02-12T09:17:23.463220 #8149]  INFO -- : [bs:bsr] Going from down => starting

I, [2013-02-12T09:17:26.565478 #8149]  INFO -- : [bs:bsr] Going from starting => up

However, when i run status or any other related bluepill command i get an error. It denied it's own existence! Could this have to do with no access to /var/run/bluepill or something? I'll paste the configuration below.

$ bluepill status --no-privileged

Error: There are no running bluepill daemons.

To start a bluepill daemon, use: bluepill load <config file>

Bluepill.application("bs", :base_dir => "/usr/local/bullshit/", :log_file => "/usr/local/bullshit/bluepill.log") do |app|

  app.working_dir = "/usr/local/bullshit/"

  app.uid = "shop"

  app.process("bsr") do |process|

    process_group = "rake"

    process.start_command = "rake bs:start"

    process.pid_file = "/usr/local/bullshit/deploy/bs.pid"

    process.daemonize = true

    process.stop_command = "kill -QUIT {{PID}}"

    #process.checks :cpu_usage, :every => 15.seconds, :below => 10, :times => [3. 5]

    #process.checks :mem_usage, :every => 20.seconds, :below => 20.megabytes, :times => [3,5]

  end

end

[Denis Dervisevic]

After some experimentation i found that if you run the commands with --no-privileged flag as well as base dir and logfile flags it works. They're also included in the configuration so it's a bit redundant :/ 

Commands example:  bundle exec bluepill load bluepill/monitorbs.pill --no-privileged --base-dir /xxx/xxx/xxx --logfile /xxx/xxx/xxx/bluepill/bs.log"

I'll leave this up in case anyone is googling for the same issue.