Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-2367

Puppet master service dies on SIGHUP

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Fix
    • Affects Version/s: PUP 3.5.0, PUP 3.5.1
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Ubuntu 12.04

    • Template:

      Description

      Puppet master service dies when receives a SIGHUP. This only happens if puppet is run as root. Running puppet master as root with --debug and --no-daemonize shows the actual error:
      Notice: Starting Puppet master version 3.5.0
      Notice: Caught HUP; calling restart
      Notice: Restarting with '/usr/bin/puppet master --masterport=8140 --debug --no-daemonize'
      /usr/lib/ruby/vendor_ruby/facter/util/directory_loader.rb:75:in `open': Permission denied - /root/.facter/facts.d (Errno::EACCES)
      from /usr/lib/ruby/vendor_ruby/facter/util/directory_loader.rb:75:in `entries'
      from /usr/lib/ruby/vendor_ruby/facter/util/directory_loader.rb:75:in `entries'
      from /usr/lib/ruby/vendor_ruby/facter/util/directory_loader.rb:55:in `load'
      from /usr/lib/ruby/vendor_ruby/facter/util/composite_loader.rb:10:in `block in load'
      from /usr/lib/ruby/vendor_ruby/facter/util/composite_loader.rb:10:in `each'
      from /usr/lib/ruby/vendor_ruby/facter/util/composite_loader.rb:10:in `load'
      from /usr/lib/ruby/vendor_ruby/facter/util/collection.rb:158:in `load_external_facts'
      from /usr/lib/ruby/vendor_ruby/facter/util/collection.rb:99:in `load'
      from /usr/lib/ruby/vendor_ruby/facter/util/collection.rb:73:in `fact'
      from /usr/lib/ruby/vendor_ruby/facter/util/collection.rb:129:in `value'
      from /usr/lib/ruby/vendor_ruby/facter.rb:117:in `value'
      from /usr/lib/ruby/vendor_ruby/puppet/defaults.rb:4:in `default_diffargs'
      from /usr/lib/ruby/vendor_ruby/puppet/defaults.rb:205:in `<module:Puppet>'
      from /usr/lib/ruby/vendor_ruby/puppet/defaults.rb:1:in `<top (required)>'
      from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
      from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
      from /usr/lib/ruby/vendor_ruby/puppet.rb:111:in `<module:Puppet>'
      from /usr/lib/ruby/vendor_ruby/puppet.rb:29:in `<top (required)>'
      from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
      from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
      from /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:12:in `<top (required)>'
      from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
      from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
      from /usr/bin/puppet:3:in `<main>'

      As to why this happens, I'm not entirely sure. Will try to look into it. Probably not a critical issue given that nothing should be sending the process a SIGHUP, but it is broken given that the SIGHUP handler is registered for the puppet master.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              timuralp Timur Alperovich
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support