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.

Description of problem:

The cron daemon fails to log that it is shutting down.


Version-Release number of selected component (if applicable):

All Redhat 6 platforms

How reproducible:

Steps to Reproduce:
1. /sbin/service crond stop
2. review the syslog

Actual results:

Nothing in the syslog regarding the shutdown.

Expected results:

A log line similar to the startup line should be logged.

2014-06-11T15:05:52-07:00 local.uvic.ca cron.info crond[25689]: (CRON) STARTUP (1.4.4)


Additional info:

This problem also exists in Redhat 5.

2014-06-11T15:07:54-07:00 local.uvic.ca cron.info crond[13998]: (CRON) STARTUP (V5.0)

How would log of stopping the daemon helped? Children of crond will be executed anyway if they already started. I don't think it's a good feature, because it won't tell you if jobs were executed or not. Tracking jobs is different issue, but I wouldn't do from cron something more complicated than it is.

The issue arises when attempting to monitor activity on a system and feed the logs into a SIEM or other reporting engine. Stopping of the crond process used to log that it was stopping, but no longer does.

Nearly all daemons log when they start and when they stop. crond should do the same.

2014-09-04 14:47:28 localhostcron.info crond[27874]: (CRON) STARTUP (V5.0)

crond logs when it starts, and it should log when it stops.

To help to prioritize the issue please report it through the regular Red Hat support channels.

http://www.redhat.com/support

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.

https://rhn.redhat.com/errata/RHBA-2015-0704.html