Might also be bug #995719. Can you try remove process_name.rb ?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1043292
Title:
Hung agent processes
To manage notifications about
The upstream bug should actually be
http://projects.puppetlabs.com/issues/10418. The originally referenced
one is a duplicate.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1043292
Thanks James Clint for your answers.
I would like to add some details:
Currently, as a temporary solution, we use crontab to kill the process
at 00h00 and start again at 00h01. With that, we are sure that the agent
works every days.
With my co-worker, we have updated a server (Ubuntu 12.04
Have run into this quite a few times now on precise. Its really quite
dangerous as puppet just randomly seems to fail.
I've looked through the changelog of puppet 2.7.12 and can't find any
obvious reason this doesn't happen, so the next step is likely to find a
reliable reproducer (tough,
I have seen this as well on 12.04 with just simple puppet apply.
Looking through 2.7.12's changelog I see a few things that *might* be
it. including:
c5d3825 (#11740) Wait on the handle from the PROCESS_INFORMATION structure
4f493a3 (#12564) Stub CHILDSTATUS in all test cases, not just failure
Thanks for taking the time to report this bug in Ubuntu.
Unfortunately its not possible to upgrade the version of puppet in
Ubuntu 12.04; if its possible to identify what was causing this issue
and what the fix in puppet was this could be fixed through the Stable
Release Update process.
**
