Hide Forgot
Description of problem: Calls to "service rhsmcertd start" reports [FAILED] on architectures s390x and ppc64. However, the rhsmcertd actually does start despite the FAILED report. This misbehavior does not happen on x86_64 or i386. Version-Release number of selected component (if applicable): [root@ibm-z10-05 ~]# rpm -q subscription-manager subscription-manager-0.95.5-1.el6.s390x [root@ibm-z10-05 ~]# uname -a Linux ibm-z10-05.rhts.eng.bos.redhat.com 2.6.32-125.el6.s390x #1 SMP Mon Mar 21 10:20:35 EDT 2011 s390x s390x s390x GNU/Linux How reproducible: 100% Steps to Reproduce: [root@ibm-z10-05 ~]# service rhsmcertd stop Stopping rhsmcertd[ OK ] [root@ibm-z10-05 ~]# service rhsmcertd status rhsmcertd is stopped [root@ibm-z10-05 ~]# ps -ef | grep [rR]hsmcertd [root@ibm-z10-05 ~]# service rhsmcertd start Starting rhsmcertd 1[FAILED] [root@ibm-z10-05 ~]# service rhsmcertd status rhsmcertd (pid 55197) is running... [root@ibm-z10-05 ~]# ps -ef | grep [rR]hsmcertd root 55197 1 0 20:00 ? 00:00:00 /usr/bin/rhsmcertd 1 [root@ibm-z10-05 ~]# ^^^ It is very strange that the service start reports FAILED while the succeeding calls to status and a ps call appear as though the service start was a success. Is this a bug with rhsmcertd, or a bug with service? or maybe its the return code that rhsmcertd returns. Actual results: Starting rhsmcertd 1[FAILED] Expected results: Starting rhsmcertd 1[ OK ] Additional info: I have also seen this same misbehavior on ppc64 > [root@ibm-js22-03 ~]# uname -a > Linux ibm-js22-03.rhts.eng.bos.redhat.com 2.6.32-124.el6.ppc64 #1 > SMP Wed Mar 16 11:45:11 EDT 2011 ppc64 ppc64 ppc64 GNU/Linux > > [root@ibm-js22-03 ~]# service rhsmcertd stop > Stopping rhsmcertd[ OK ] > [root@ibm-js22-03 ~]# service rhsmcertd status > rhsmcertd is stopped > [root@ibm-js22-03 ~]# service rhsmcertd start > Starting rhsmcertd 1[FAILED] > [root@ibm-js22-03 ~]# service rhsmcertd status > rhsmcertd (pid 26023) is running... > [root@ibm-js22-03 ~]# service rhsmcertd start > rhsmcertd is already running
The daemon wasn't setting a return code on success, only on failure. on s390x and ppc64, this resulted in a non-zero return code. Fixed in master, rhel6, and rhel5.7 branches.
*** Bug 691577 has been marked as a duplicate of this bug. ***
Created attachment 489984 [details] /etc/init.d/rhsmcertd restart ; /etc/init.d/rhsmcertd status ; # console output in log.txt
[root@ibm-js22-vios-02-lp1 ~]# rpm -q subscription-manager subscription-manager-0.95.6-1.el6.ppc64 [root@ibm-js22-vios-02-lp1 ~]# service rhsmcertd stop Stopping rhsmcertd[ OK ] [root@ibm-js22-vios-02-lp1 ~]# service rhsmcertd status rhsmcertd is stopped [root@ibm-js22-vios-02-lp1 ~]# ps -ef | grep [rR]hsmcertd [root@ibm-js22-vios-02-lp1 ~]# service rhsmcertd start Starting rhsmcertd 240[ OK ] [root@ibm-js22-vios-02-lp1 ~]# service rhsmcertd status rhsmcertd (pid 4897) is running... [root@ibm-js22-vios-02-lp1 ~]# ps -ef | grep [rR]hsmcertd root 4897 1 0 10:19 ? 00:00:00 /usr/bin/rhsmcertd 240 [root@ibm-js22-vios-02-lp1 ~]# service rhsmcertd restart Stopping rhsmcertd[ OK ] Starting rhsmcertd 240[ OK ] ^^^ all expected behavior VERIFIED ppc64
[root@ibm-z10-32 ~]# rpm -q subscription-manager subscription-manager-0.95.6-1.el6.s390x [root@ibm-z10-32 ~]# service rhsmcertd stop Stopping rhsmcertd[ OK ] [root@ibm-z10-32 ~]# service rhsmcertd status rhsmcertd is stopped [root@ibm-z10-32 ~]# ps -ef | grep [rR]hsmcertd [root@ibm-z10-32 ~]# service rhsmcertd start Starting rhsmcertd 240[ OK ] [root@ibm-z10-32 ~]# service rhsmcertd status rhsmcertd (pid 37947) is running... [root@ibm-z10-32 ~]# ps -ef | grep [rR]hsmcertd root 37947 1 0 11:28 ? 00:00:00 /usr/bin/rhsmcertd 240 [root@ibm-z10-32 ~]# service rhsmcertd restart Stopping rhsmcertd[ OK ] Starting rhsmcertd 240[ OK ] ^^^ all expected behavior VERIFIED s390x
*** Bug 675125 has been marked as a duplicate of this bug. ***
------- Comment From Subrata Modak subrata.ibm.com 2011-04-11 07:47 EDT------- Redhat, This is still reproducible on SNAP2 on PPC64. Please see the results: [root@devl4e-little-lp3 ~]# service rhsmcertd status rhsmcertd (pid 1742) is running... [root@devl4e-little-lp3 ~]# service rhsmcertd stop Stopping rhsmcertd [ OK ] [root@devl4e-little-lp3 ~]# service rhsmcertd start Starting rhsmcertd 240 [FAILED] [root@devl4e-little-lp3 ~]# service rhsmcertd status rhsmcertd (pid 32008) is running... [root@devl4e-little-lp3 ~]# uname -a Linux <> 2.6.32-128.el6.ppc64 #1 SMP Mon Mar 28 21:49:38 EDT 2011 ppc64 ppc64 ppc64 GNU/Linux [root@devl4e-little-lp3 ~]# cat /etc/issue Red Hat Enterprise Linux Server release 6.1 Beta (Santiago) Kernel \r on an \m Regards-- Subrata
I believe the error seen in comment 10 is because your build (built on Mar 28) was with subscription-manager 95.5 : http://download.devel.redhat.com/devel/candidate-trees/RHEL6.1-20110328.1/6.1/Server/ppc64/os/Packages/subscription-manager-0.95.5-1.el6.ppc64.rpm Newer builds of rhel6.1 appear to have the newer subscription-manager 95.6 which fixes this bug : http://download.devel.redhat.com/devel/candidates/RHEL6.1-20110407.2/6/Server/x86_64/os/Packages/subscription-manager-0.95.6-1.el6.x86_64.rpm I don't know what the SNAPSHOT numbers are.
------- Comment From Subrata Modak subrata.ibm.com 2011-04-15 06:53 EDT------- > Ok. i can see this version on SS3. I will retest it and let you know. Hello Redhat, The issue is fixed on SS3. Thanks. [root@devl4e-little-lp3 ~]# service rhsmcertd status rhsmcertd (pid 1793) is running... [root@devl4e-little-lp3 ~]# service rhsmcertd stop [root@devl4e-little-lp3 ~]# service rhsmcertd status [root@devl4e-little-lp3 ~]# service rhsmcertd start [root@devl4e-little-lp3 ~]# service rhsmcertd status rhsmcertd (pid 2186) is running... [root@devl4e-little-lp3 ~]# rpm -qa | grep -i subscription-manager subscription-manager-gnome-0.95.6-1.el6.ppc64 subscription-manager-firstboot-0.95.6-1.el6.ppc64 [root@devl4e-little-lp3 ~]# uname -a Linux devl4e-little-lp3.austin.ibm.com 2.6.32-130.el6.ppc64 #1 SMP Tue Apr 5 19:52:26 EDT 2011 ppc64 ppc64 ppc64 GNU/Linux [root@devl4e-little-lp3 ~]# cat /etc/issue Red Hat Enterprise Linux Server release 6.1 Beta (Santiago) Kernel \r on an \m Regards-- Subrata
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2011-0611.html