On Jan 6, 1:06 am, Andreas N <d...@pseudoterminal.org> wrote: > Wow, it took quite a while for my post to reach this group. No idea why, is > it moderated? > > Anyway, this problem seems to also happen with agents running Puppet 2.7.6, > although apparently less frequently. I'm almost positive it must have > something to do with a module but I wouldn't know how or where to begin > debugging. > > Does anyone have any ideas?
Nothing in your log suggests that the Puppet agent is doing any work when it fails. It appears to apply a catalog successfully, then create a report successfully, then nothing else. That doesn't seem like a problem in a module. Nevertheless, you could try removing classes from the affected node's configuration and testing whether Puppet still freezes. You said the agent runs for several hours before it hangs. Does it perform multiple successful runs during that time? That also would tend to counterindicate a problem in your manifests. I'm suspicious that something else on your systems is interfering with the Puppet process; some kind of service manager, for example. You'll have to say whether that's a reasonable guess. Alternatively, you may have a system-level bug; there have been a few Ruby bugs and kernel regressions that interfered with Puppet operation. You could try using strace to determine where the failure happens, though that's not as simple as it may sound. You could also try just sidestepping the problem by using cron to launch puppetd --runonce at your desired intervals, instead of leaving puppetd running in daemon mode. A fair number of people seem to run Puppet that way, and it has some advantages. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
