Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
(In reply to comment #0)
> Description of problem:
> there is change in status codes for krb5kdc and kadmin
> Results from 6.0
> :: [ LOG ] :: Lock file
> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
>
> :: [ PASS ] :: Running 'kill -n 9 25399'
> :: [ PASS ] :: Running 'service kadmin status'
> :: [ PASS ] :: Running 'service kadmin stop'
> :: [ LOG ] :: Duration: 1s
> :: [ LOG ] :: Assertions: 3 good, 0 bad
> :: [ PASS ] :: RESULT: Lock file
>
>
> And from 6.1 (krb5 1.9-1):
>
> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
> :: [ LOG ] :: Lock file
> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
>
> :: [ PASS ] :: Running 'kill -n 9 6413'
> :: [ FAIL ] :: Running 'service krb5kdc status' (Expected 2, got 1)
> :: [ PASS ] :: Running 'service krb5kdc stop'
> :: [ LOG ] :: Duration: 3s
> :: [ LOG ] :: Assertions: 2 good, 1 bad
> :: [ FAIL ] :: RESULT: Lock file
>
>
> Version-Release number of selected component (if applicable):
> krb5-server-1.9-1.el6
>
> How reproducible:
> always
>
> Steps to Reproduce:
> 1. kill -n 9 $(pidof ${SERVICE})
> 2. service ${SERVICE} status
>
>
> Actual results:
> service krb5kdc status; echo $?
> krb5kdc dead but pid file exists
> 1
>
> Expected results:
> service krb5kdc status; echo $?
> krb5kdc dead but pid file exists
> 2
Can you double-check that the expected error message is about the pid file, and not about the subsys being locked?
When I try this manually with 1.8.2-3.el6_0.3, I get exit status 2 with a "process dead but subsys locked" error message. In 1.9, where we start being able to tell krb5kdc and kadmind to create pid files, I do get an exit status of 1 and a "process dead but pid file exists error", which I guess is normal, because when there's a dead process, the status function checks for the existence of the pid file first.
You have right. My test was counting with nonexistence of pid files. The kadmin and krb5kdc scripts are behaving correctly. Even better now, when there is the pid file with the number of correct process.
Description of problem: there is change in status codes for krb5kdc and kadmin Results from 6.0 :: [ LOG ] :: Lock file :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ PASS ] :: Running 'kill -n 9 25399' :: [ PASS ] :: Running 'service kadmin status' :: [ PASS ] :: Running 'service kadmin stop' :: [ LOG ] :: Duration: 1s :: [ LOG ] :: Assertions: 3 good, 0 bad :: [ PASS ] :: RESULT: Lock file And from 6.1 (krb5 1.9-1): :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ LOG ] :: Lock file :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ PASS ] :: Running 'kill -n 9 6413' :: [ FAIL ] :: Running 'service krb5kdc status' (Expected 2, got 1) :: [ PASS ] :: Running 'service krb5kdc stop' :: [ LOG ] :: Duration: 3s :: [ LOG ] :: Assertions: 2 good, 1 bad :: [ FAIL ] :: RESULT: Lock file Version-Release number of selected component (if applicable): krb5-server-1.9-1.el6 How reproducible: always Steps to Reproduce: 1. kill -n 9 $(pidof ${SERVICE}) 2. service ${SERVICE} status Actual results: service krb5kdc status; echo $? krb5kdc dead but pid file exists 1 Expected results: service krb5kdc status; echo $? krb5kdc dead but pid file exists 2