[ruby agent question] monit not starting after cck/resurrection

[Dr Nic Williams]

I'm running bosh-aws-xen-ubuntu-lucid/2624 and today I both ran "bosh cck" and resurrection on a deployment where the VM had been manually terminated. The job VM was replaced but its status was "failing". Upon investigation, monit had not begun starting job processes.

Any ideas why this is happening? Regression in ruby agent? (which I assume hasn't been touched so not sure about regressions) A bad config in my BOSH?

Nic

--

Dr Nic Williams

Stark & Wayne LLC - consultancy for Cloud Foundry users

http://drnicwilliams.com

http://starkandwayne.com

cell +1 (415) 860-2185

twitter @drnic

[Karl Isenberg]

Can you provide sanitized BOSH Agent log from /var/vcap/bosh/log/current? 

We've not changed ruby agent for a long time so it's unlikely it's a new bug.

-Karl & Dmitriy

[Dr Nic Williams]

Thanks Karl. I came across another resurrected VM today that did not re-start monit processes.

sanitized agent log - https://gist.github.com/drnic/7fd43c0f6b88db5bdd8c

To unsubscribe from this group and stop receiving emails from it, send an email to bosh-users+...@cloudfoundry.org.