Bug #952

Puppetd crashes

Added by Digant Kasundra over 4 years ago. Updated over 4 years ago.

Status:Closed Start date:
Priority:High Due date:
Assignee:Puppet Community % Done:

0%
Category:-
Target version:0.25.0
Affected Puppet version:0.25.4 Branch:
Keywords:
Votes: 0

Description

/usr/lib/ruby/1.8/timeout.rb:54:in @open': execution expired (Timeout::Error)
        from /usr/lib/ruby/1.8/net/http.rb:560:in @connect'
        from /usr/lib/ruby/1.8/timeout.rb:56:in @timeout'
        from /usr/lib/ruby/1.8/timeout.rb:76:in @timeout'
        from /usr/lib/ruby/1.8/net/http.rb:560:in @connect'
        from /usr/lib/ruby/1.8/net/http.rb:553:in @do_start'
        from /usr/lib/ruby/1.8/net/http.rb:542:in @start'
        from /usr/lib/ruby/1.8/net/http.rb:1032:in @request'
        from /usr/lib/ruby/1.8/net/http.rb:989:in @post2'
         ... 25 levels...
        from /usr/lib/ruby/1.8/puppet/external/event-loop/event-loop.rb:116:in @iterate'
        from /usr/lib/ruby/1.8/puppet/external/event-loop/event-loop.rb:107:in @run'
        from /usr/lib/ruby/1.8/puppet.rb:361:in @start'
        from /usr/sbin/puppetd:447

We’ve had several puppet clients crash periodically with the above error. This happens after the config is finished, possibly when sending report?

manifests.tar.gz (21.4 kB) Mike McGrath, 12/20/2007 11:20 pm

History

#1
Updated by Mike McGrath over 4 years ago

I’m seeing this too (just with an upgrade to the 0.24.0 release). Might be a different bug but it seems the puppetmaster is regularly getting into a bad state. The client eventually just dies. In debug mode the last line I’m seeing is:

debug: Finishing transaction -605897528 with 0 changes

#2
Updated by Luke Kanies over 4 years ago

  • Status changed from 1 to Closed
  • 7 set to fixed

Hopefully fixed in commit:e2fc425010c20e307c835a726b74f19abf31ba34.

#3
Updated by Mike McGrath over 4 years ago

Replying to [comment:4 luke]:

Hopefully fixed in commit:e2fc425010c20e307c835a726b74f19abf31ba34.

Is this testable just by upgrading the puppetmaster or will it be required on both puppetmaster and the nodes?

#4
Updated by Luke Kanies over 4 years ago

The exception is on the client, it looks like, so I’m sure they will have to be upgraded.

I’ll make sure this fix gets into 0.23.3, so you don’t have to upgrade all the way if you don’t want.

Also available in: Atom PDF