#1199: puppetd dies after connection to puppetmaster fails
---------------------------------------+------------------------------------
Reporter: immerda | Owner: community
Type: defect | Status: new
Priority: normal | Component: library
Version: 0.24.4 | Severity: normal
Keywords: daemon, die, no connection | Stage: Unreviewed
Patch: None | Complexity: Unknown
---------------------------------------+------------------------------------
We had now several times the problem that when our puppetmaster died (due
to some memory problems) all our clients daemons just stopped running and
exited. We then had to manually restart all daemons.
Sample log entry from a client:
{{{
Sun Apr 20 06:24:32 +0200 2008 Puppet (notice): Finished catalog run in
45.93 seconds
Sun Apr 20 06:56:32 +0200 2008 Puppet (err): Could not retrieve plugins:
execution expired
Sun Apr 20 06:58:32 +0200 2008 Puppet (err): Configuration retrieval timed
out
Sun Apr 20 06:58:33 +0200 2008 Puppet (notice): Starting catalog run
}}}
this is the last entry after that puppetd isn't running anymore.
It seems that puppetd is failling after sending the message benchmark in
lib/puppet/network/client/master.rb on line 234. I tried to nail this
problem down to propose a patch for it, however my puppet internal
knowledge isn't yet that fine to really see where the problem actually
raises. It might be due to some (unlogged) failure in benchmark or even
later.
--
Ticket URL: <http://reductivelabs.com/trac/puppet/ticket/1199>
puppet <http://reductivelabs.com>
Puppet - Portable System Automation
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
