Jira (PUP-5037) RedHat puppetmaster service status report is invalid when it's stopped and client is running

Title: Message Title

Hamid Nazari commented on

PUP-5037

The culprit is

# /etc/init.d/puppetmaster:92

rh_status() {

    status $pidopts $PUPPETMASTER

    RETVAL=$?

    return $RETVAL

Since lockfile is not being passed to status, it's being assumed it is /var/lock/subsys/puppet.

# /etc/init.d/functions:447

        if [ -z "${lock_file}" ]; then

                lock_file=${base}

fi

        # See if /var/lock/subsys/${lock_file} exists

        if [ -f /var/lock/subsys/${lock_file} ]; then

                echo $"${base} dead but subsys locked"

                return 2

fi

Which is incorrect. Clearly puppetmaster's lockfile is /var/lock/subsys/puppetmaster according to

# ext/redhat/server.init:92

lockfile=/var/lock/subsys/puppetmaster

Add Comment

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Reply via email to