Puppet users - Jan 2013 - 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>

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? In the posted configs *some company internals 
are masked*.
> cat /etc/puppet/puppet.conf 
[main]
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl
    modulepath = /opt/<masked>/puppet/modules
    manifestDir = /opt/<masked>/puppet/manifests
    manifest = /opt/<masked>/puppet/manifests/site.pp

[development]
 logdir = /opt/<masked>/log/puppet
modulepath = /opt/<masked>/dev/puppet/modules
manifestDir = /opt/<masked>/dev/puppet/manifests
manifest = /opt/<masked>/dev/puppet/manifests/site.pp

[agent]
classfile = $vardir/classes.txt
localconfig = $vardir/localconfig
server = <masked>
report = true
listen = true
splaylimit = 0
runinterval = 30

[master]
certname=<masked>
reports = http,log
reportdir = /var/lib/puppet/reports/upload
reporturl = http://<masked>:3000/reports
node_terminus = exec
external_nodes = /usr/share/puppet-dashboard/bin/external_node


Used packages:
> rpm -qa | egrep "puppet|ruby"
rubygem-rake-0.8.7-2.1.el6.noarch
ruby-mysql-2.8.2-1.el6.x86_64
libselinux-ruby-2.0.94-5.3.el6.x86_64
puppet-3.0.2-1.el6.noarch
puppet-dashboard-1.2.16-1.el6.noarch
ruby-1.8.7.352-7.el6_2.x86_64
ruby-irb-1.8.7.352-7.el6_2.x86_64
rubygems-1.3.7-1.el6.noarch
ruby-augeas-0.4.1-1.el6.x86_64
ruby-shadow-1.4.1-13.el6.x86_64
puppet-server-3.0.2-1.el6.noarch
puppetlabs-release-6-6.noarch
ruby-libs-1.8.7.352-7.el6_2.x86_64
ruby-rdoc-1.8.7.352-7.el6_2.x86_64
rubygem-json-1.4.6-1.el6.x86_64


Any ideas? Thanks in advance! 

-- 
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/-/FnkowIcBME4J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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

-- 
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/-/qwqO5HXf1BEJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

>
> 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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.