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.

Created attachment 1065329 [details]
sosreport

Description of problem:

Freshly installed "minimal" system.

Logwatch is running twice daily at approx 3am and 4am. Several other daily and weekly jobs are also running twice


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


How reproducible:

100%

Steps to Reproduce:
1. Install minimal system with logwatch and MTA
2. monitor root mail over several days
3.

Actual results:

2 logwatches are mailed to root each day.


Expected results:

1 Logwatch is mailed to root each day.


Additional info:


This has been repeatedly reported ion Bugzilla by various redhat/fedora users over the years and closed with blame placed on user malconfiguration.

This is a freshly installed system, we haven't configured it. There is no reason for this to be occurring other than vendor malconfiguration.

Can you please report the issue via the Red Hat Support account?
http://www.redhat.com/en/services/support

Also do you have both cronie-anacron and cronie-noanacron packages installed?
If so, just choose one and uninstall the other. I have no idea how you could get both installed but it normally does not happen unless you explicitly install both.

We (eventually) traced the problem.

In short: if /etc/crontab is used from an old system (in this case RHEL5) then the (now) redundant entries are used and the duplication is never flagged up during sanity checks.

It would be a good idea to check for and make more noise about locally edited /etc/crontab and suggest that entries be moved to /etc/cron.d/

Except normally local editing of /etc/crontab is perfectly OK. This is work for some system for proper inplace upgrade between major versions but I do not think we have one for upgrades from RHEL-5.