Bug #591

puppetd dies on SIGHUP

Added by Peter Abrahamsen about 5 years ago. Updated about 5 years ago.

Status:Closed Start date:
Priority:Urgent Due date:
Assignee:Luke Kanies % Done:

0%

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

Description

Upon receiving a SIGHUP, puppetd dies with this:

/usr/lib64/ruby/gems/1.8/gems/puppet-0.22.3/lib/puppet.rb:207:in @settraps': uninitialized constant Puppet::Network::Client::MasterClient (NameError)

    from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in @find'
    from /usr/lib64/ruby/gems/1.8/gems/puppet-0.22.3/lib/puppet.rb:207:in @each'
    from /usr/lib64/ruby/gems/1.8/gems/puppet-0.22.3/lib/puppet.rb:207:in @find'
    from /usr/lib64/ruby/gems/1.8/gems/puppet-0.22.3/lib/puppet.rb:207:in @settraps'
    from /usr/lib64/ruby/gems/1.8/gems/puppet-0.22.3/lib/puppet/external/event-loop/event-loop.rb:123:in @call'
    from /usr/lib64/ruby/gems/1.8/gems/puppet-0.22.3/lib/puppet/external/event-loop/event-loop.rb:123:in @select'
    from /usr/lib64/ruby/gems/1.8/gems/puppet-0.22.3/lib/puppet/external/event-loop/event-loop.rb:123:in @select'
    from /usr/lib64/ruby/gems/1.8/gems/puppet-0.22.3/lib/puppet/external/event-loop/event-loop.rb:112:in @iterate'
    from /usr/lib64/ruby/gems/1.8/gems/puppet-0.22.3/lib/puppet/external/event-loop/event-loop.rb:103:in @run'
    from /usr/lib64/ruby/gems/1.8/gems/puppet-0.22.3/lib/puppet.rb:323:in @start'
    from /usr/lib64/ruby/gems/1.8/gems/puppet-0.22.3/bin/puppetd:443
    from /usr/bin/puppetd:18:in @load'
    from /usr/bin/puppetd:18

It’s possible that something’s in a strange state because during the last run, it failed to get the state for many packages due to broken Gentoo package category/name support.

History

Updated by Luke Kanies about 5 years ago

  • Status changed from 1 to 2

Marking #600 as a dupe of this bug.

Updated by Luke Kanies about 5 years ago

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

Fixed in r2402.

Also available in: Atom PDF