> > On Thursday, January 3, 2013 6:30:33 AM UTC-6, al...@gmx.de wrote: >> >> Seeing this a lot lately, restarting puppet master service usually >> resolves it: >> >> Jan 3 13:17:01 <puppet master> puppet-master[24120]: (//<some >> agent>/Puppet) Could not retrieve catalog from remote server: Error 400 on >> SERVER: Failed when searching for node <some agent>: Failed to find <some >> agent> via exec: Execution of >> '/usr/share/puppet-dashboard/bin/external_node <some agent>' returned : >> >> >> Any idea what causes this? >> > > > The error message seems to indicate that Dashboard's external node script > fails on the affected node(s). Is the problem consistent with respect to > the nodes that cause the error? That could indicate that the affected > nodes are not set up correctly there. > > I don't know much about the internals of Dashboard, but if the problem is > not tied to specific nodes then you may have a resource exhaustion > problem. Is the master's disk filled? Have you added many nodes > recently? Might a RAM module have gone bad, or have you otherwise reduced > the master's available memory? > > > John > > Commenting out ENC-related lines in puppet.conf fixed this. Calling the external command was the cause for spawned child processes in the first place. Don't need ENC anyway. It's all peachy now. Thx!
-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/KisMDeqyVb0J. 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.
