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

RedHat puppetmaster service status report is invalid when it's stopped and client is running

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.3.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      1
    • Sprint:
      Client 2015-09-02
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      If the puppet service was running, but the passenger-based puppetmaster service was not, then you would receive an error when trying to get the status of the puppetmaster service. Now it reports that the puppetmaster service is stopped.

      Description

      I initially ran into this issue on Amazon Linux.

      When puppetmaster service is stopped and puppet service is running, service puppetserver status returns false info, "puppet dead but subsys locked" to be exact.

      [vagrant@localhost ~]$ cat /etc/issue
      CentOS release 6.5 (Final)
      Kernel \r on an \m
       
      [vagrant@localhost ~]$ sudo service puppetmaster status
      puppet is stopped
      [vagrant@localhost ~]$ sudo service puppet status
      puppet is stopped
      [vagrant@localhost ~]$ sudo service puppet start
      Starting puppet agent:                                     [  OK  ]
      [vagrant@localhost ~]$ sudo service puppetmaster status
      puppet dead but subsys locked
      

      What I expected was "puppet is stopped".

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                hamidnazari Hamid Nazari
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support