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:
Since the upgrade to RHEL 6.7 we receive e-mails like this:

--- snipp ---
Date: Sat,  1 Aug 2015 03:06:34 +0200 (CEST)
From: Anacron <root.net>
To: root.net
Subject: Anacron job 'cron.daily' on gateway2.example.net

/etc/cron.daily/logrotate:

error: error running non-shared postrotate script for /var/log/radius/radius.log of '/var/log/radius/radius.log '
--- snapp ---

From my point of view this error is triggered due to a insane postrotate
script in logrotate which gets visible since the logrotate update (which
is no longer hiding any logrotate output).

Above error is triggered if radius is not running while the postrotate
script of logrotate tries to reload the daemon (leads to exit 7).

Version-Release number of selected component (if applicable):
freeradius-2.2.6-4.el6.x86_64
logrotate-3.7.8-23.el6.x86_64

How reproducible:
Everytime, see above and below.

Actual results:
error running non-shared postrotate script for /var/log/radius/radius.log of '/var/log/radius/radius.log '

Expected results:
No error message by logrotate via e-mail.

Created attachment 1058796 [details]
Patch to avoid the failure

Even this patch is not really great it uses the same common style and way that 
"grep -C 2 postrotate /etc/logrotate.d/*" shows (Apache, BIND, rsyslogd, ...).

Cross-filed case 01486583 on the Red Hat customer portal.

Please note that this issue usually happens if freeradius is started or
stopped by a pacemaker setup where the configuration and the logs do not
reside on a shared filesystem. So if freeradius was running and gets then
stopped (e.g. due to a takeover), the log file is indeed not empty, the
issue above happens.

We're going to address this issue in RHEL7 eventually.

Nikolai, did this get addressed ? If it has, I'm just curious what the fix was.. I'm having troubles finding any further information.

Hi David. Unfortunately, this is only fixed in RHEL7, but systemd in RHEL7 has a bug, which prevents the fix from working. See Bug 1365226 and Bug 1191920. Sorry for the mess.

Not a problem, thanks for the links.. those and the patch above at least give me ideas for a work around!