Description of problem: In RHEL62, running "service rhsmcertd restart" would append logging to the rhsmcertd.log like this... [root@jsefler-onprem-62server ~]# tail -4 /var/log/rhsm/rhsmcertd.log Wed Nov 9 15:21:54 2011: started: interval = 1440 minutes Wed Nov 9 15:21:54 2011: started: interval = 240 minutes Wed Nov 9 15:21:55 2011: certificates updated Wed Nov 9 15:21:55 2011: certificates updated Currently in RHEL58, the started * messages have disappeared. Please restore them. Version-Release number of selected component (if applicable): [root@jsefler-onprem-5server ~]# rpm -q subscription-manager subscription-manager-0.98.2-1.git.12.99fdffb.el5_7 How reproducible: Steps to Reproduce: 1.service rhsmcertd restart 2.tail -f /var/log/rhsm/rhsmcertd.log Actual results: Expected results: you should see "started" log statements like this: Wed Nov 9 15:21:54 2011: started: interval = 1440 minutes Wed Nov 9 15:21:54 2011: started: interval = 240 minutes Additional info: This regression may have been introduced in this commit f5d074a7e7da4c2e1f9cb4c2473b9835134bb99b
b71d5e2 master 0.98.4+
Verifying Version... [root@jsefler-onprem-5server ~]# rpm -q subscription-manager subscription-manager-0.98.3-1.git.24.65494c7.el5_7 [root@jsefler-onprem-5server ~]# service rhsmcertd restart Stopping rhsmcertd [ OK ] Starting rhsmcertd 240 1440 [ OK ] [root@jsefler-onprem-5server ~]# tail -4 /var/log/rhsm/rhsmcertd.log Thu Dec 1 18:28:47 2011: healing check started: interval = 1440 Thu Dec 1 18:28:47 2011: cert check started: interval = 240 Thu Dec 1 18:28:48 2011: certificates updated Thu Dec 1 18:28:48 2011: certificates updated [root@jsefler-onprem-5server ~]# moving to VERIFIED
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No description necessary
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0154.html