All Hosts Shown as Unresponsive. Worker Restart Fails. Clients Seem Happy?
Wed, 13 Feb 2013 11:40:31 -0800 Post Comments
I think there might be a bug buried here. I hit this before a demo this
morning - the problem was that the pid files at
/opt/puppet/share/puppet-dashboard/tmp/pids/delayed_job.{0,1}.pid were
present but there was no PID in them (and the background workers weren't
running). Removing the pidfiles allowed the service to start, but we need
to discover why these files are being created empty. My master was on
Ubuntu 12.04 and PE 2.7.0
--
Gary Larizza
Professional Services Engineer
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe*******.
To post to this group, send email to puppet-users*******.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
morning - the problem was that the pid files at
/opt/puppet/share/puppet-dashboard/tmp/pids/delayed_job.{0,1}.pid were
present but there was no PID in them (and the background workers weren't
running). Removing the pidfiles allowed the service to start, but we need
to discover why these files are being created empty. My master was on
Ubuntu 12.04 and PE 2.7.0
--
Gary Larizza
Professional Services Engineer
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe*******.
To post to this group, send email to puppet-users*******.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
