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

systemctl restart puppet fails to restart puppet

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Cannot Reproduce
    • Affects Version/s: PUP 3.7.5, PUP 4.0.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Environment:

      Fedora Linux

    • Template:
    • Story Points:
      3

      Description

      Adding KillMode=process to puppet.service to fix PUP-3931 appears to have broken systemctl restart puppet for me.

      # systemctl status puppet
      ● puppet.service - Puppet agent
         Loaded: loaded (/usr/lib/systemd/system/puppet.service; enabled)
         Active: active (running) since Fri 2015-05-01 11:02:35 MDT; 11s ago
       Main PID: 18662 (start-puppet-ag)
         CGroup: /system.slice/puppet.service
                 ├─18662 /bin/sh /usr/bin/start-puppet-agent agent --no-daemonize
                 └─18665 /usr/bin/ruby-mri /usr/bin/puppet agent --no-daemonize
      # systemctl restart puppet
      # systemctl status puppet
      ● puppet.service - Puppet agent
         Loaded: loaded (/usr/lib/systemd/system/puppet.service; enabled)
         Active: failed (Result: exit-code) since Fri 2015-05-01 11:03:03 MDT; 4s ago
        Process: 19066 ExecStart=/usr/bin/start-puppet-agent agent ${PUPPET_EXTRA_OPTS} --no-daemonize (code=exited, status=1/FAILURE)
       Main PID: 19066 (code=exited, status=1/FAILURE)
         CGroup: /system.slice/puppet.service
                 └─18665 /usr/bin/ruby-mri /usr/bin/puppet agent --no-daemonize
      

      The old child puppet process is still around. Strace shows:

      19199 restart_syscall(<... resuming interrupted call ...> <unfinished ...>
      19245 restart_syscall(<... resuming interrupted call ...> <unfinished ...>
      19198 wait4(-1,  <unfinished ...>
      19199 <... restart_syscall resumed> )   = -1 ETIMEDOUT (Connection timed out)
      19199 futex(0xb556d0, FUTEX_WAKE_PRIVATE, 1) = 0
      19199 futex(0xb55654, FUTEX_WAIT_BITSET_PRIVATE, 15, {359644, 166273339}, ffffffff <unfinished ...>
      19198 <... wait4 resumed> 0x7ffc8ab93080, 0, NULL) = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
      19198 --- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=1, si_uid=0} ---
      19198 +++ killed by SIGTERM +++
      19199 <... futex resumed> )             = -1 ETIMEDOUT (Connection timed out)
      19199 futex(0xb556d0, FUTEX_WAKE_PRIVATE, 1) = 0
      19199 futex(0xb55654, FUTEX_WAIT_BITSET_PRIVATE, 17, {359649, 166794009}, ffffffff <detached ...>
      

      I'm seeing this with Fedora 21 and 3.7.5 and Fedora 22 w/ 4.0.0.

        Attachments

          Activity

            People

            • Assignee:
              opoplawski Orion Poplawski
              Reporter:
              opoplawski Orion Poplawski
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support