Issue #6658 has been updated by Jacob Helwig.

After talking with James, it looks like propagating the block below down to the 
agent's run log would be sufficient for the user's needs.

    err: Failed to find nops via exec: Execution of 
'/etc/puppetlabs/puppet-dashboard/external_node node' returned 1: 
/opt/puppet/lib/ruby/1.8/net/http.rb:560:in `initialize': Connection timed out 
- connect(2) (Errno::ETIMEDOUT) 
    from /opt/puppet/lib/ruby/1.8/net/http.rb:560:in `open' 
    from /opt/puppet/lib/ruby/1.8/net/http.rb:560:in `connect' 
    from /opt/puppet/lib/ruby/1.8/timeout.rb:53:in `timeout' 
    from /opt/puppet/lib/ruby/1.8/timeout.rb:101:in `timeout' 
    from /opt/puppet/lib/ruby/1.8/net/http.rb:560:in `connect' 
    from /opt/puppet/lib/ruby/1.8/net/http.rb:553:in `do_start' 
    from /opt/puppet/lib/ruby/1.8/net/http.rb:542:in `start' 
    from /opt/puppet/lib/ruby/1.8/net/http.rb:440:in `start' 
    from /etc/puppetlabs/puppet-dashboard/external_node:11
----------------------------------------
Bug #6658: Capture and return a cleaner error when ENC fails to connect (esp. 
Dashboard ENC)
https://projects.puppetlabs.com/issues/6658

Author: James Turnbull
Status: Accepted
Priority: High
Assignee: 
Category: error reporting
Target version: 2.6.x
Affected Puppet version: 2.6.3
Keywords: 
Branch: 


<pre>
notice: Starting Puppet master version 2.6.4 (Puppet Enterprise 1.0) 
info: mount[files]: allowing x.x.x.x/16 access 
debug: No modules mount given; autocreating with default permissions 
debug: No plugins mount given; autocreating with default permissions 
debug: Finishing transaction 70155478255660 
info: access[^/catalog/([^/]+)$]: allowing 'method' find 
info: access[^/catalog/([^/]+)$]: allowing $1 access 
info: access[/certificate_revocation_list/ca]: allowing 'method' find 
info: access[/certificate_revocation_list/ca]: allowing * access 
info: access[/report]: allowing 'method' save 
info: access[/report]: allowing * access 
info: access[/file]: allowing * access 
info: access[/certificate/ca]: adding authentication no 
info: access[/certificate/ca]: allowing 'method' find 
info: access[/certificate/ca]: allowing * access 
info: access[/certificate/]: adding authentication no 
info: access[/certificate/]: allowing 'method' find 
info: access[/certificate/]: allowing * access 
info: access[/certificate_request]: adding authentication no 
info: access[/certificate_request]: allowing 'method' find 
info: access[/certificate_request]: allowing 'method' save 
info: access[/certificate_request]: allowing * access 
info: access[/]: adding authentication any 
info: Inserting default '/status'(auth) acl because none where found in 
'/etc/puppetlabs/puppet/auth.conf' 
info: mount[files]: allowing x.x.x.x/16 access 
info: Expiring the node cache of node
info: Not using expired node for node from cache; expired at Wed Mar 09 
11:51:43 -0800 2011 
debug: Executing '/etc/puppetlabs/puppet-dashboard/external_node node' 
err: Failed to find nops via exec: Execution of 
'/etc/puppetlabs/puppet-dashboard/external_node node' returned 1: 
/opt/puppet/lib/ruby/1.8/net/http.rb:560:in `initialize': Connection timed out 
- connect(2) (Errno::ETIMEDOUT) 
from /opt/puppet/lib/ruby/1.8/net/http.rb:560:in `open' 
from /opt/puppet/lib/ruby/1.8/net/http.rb:560:in `connect' 
from /opt/puppet/lib/ruby/1.8/timeout.rb:53:in `timeout' 
from /opt/puppet/lib/ruby/1.8/timeout.rb:101:in `timeout' 
from /opt/puppet/lib/ruby/1.8/net/http.rb:560:in `connect' 
from /opt/puppet/lib/ruby/1.8/net/http.rb:553:in `do_start' 
from /opt/puppet/lib/ruby/1.8/net/http.rb:542:in `start' 
from /opt/puppet/lib/ruby/1.8/net/http.rb:440:in `start' 
from /etc/puppetlabs/puppet-dashboard/external_node:11
</pre>


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
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.

Reply via email to