Bug 1197421

Summary: Logrotate needs to use systemctl
Product: [Fedora] Fedora EPEL Reporter: Brian Wong <bwong>
Component: rabbitmq-serverAssignee: Peter Lemenkov <lemenkov>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: epel7CC: erlang, hubert.plociniczak, jeckersb, josh, lemenkov, plemenko, rjones, s, tagami_ryo
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-01 11:03:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brian Wong 2015-03-01 04:35:45 UTC 
Description of problem:
The package rabbitmq-server-3.3.5-4.el7.noarch installs a logrotate configuration file that uses /sbin/service. Log rotation does not run successfully because the postrotate parameter needs to be updated.

The message received from logrotate (via cron):
/etc/cron.hourly/logrotate:

The service command supports only basic LSB actions (start, stop, restart, try-restart, reload, force-reload, status). For other actions, please try to use systemctl.
error: error running shared postrotate script for '/var/log/rabbitmq/*.log '

Version-Release number of selected component (if applicable):
rabbitmq-server-3.3.5-4.el7.noarch

How reproducible:
Consistently

Steps to Reproduce:
1. Install rabbitmq-server.
2. View logrotate configuration file /etc/logrotate.d/rabbitmq-server
3.

Actual results:
All I can confirm is the error message from logrotate, whether the rabbitmq logs actually get rotated, I cannot say for sure at this time.

Expected results:
A working postrotate command

Additional info:
Comment 1 Peter Lemenkov 2015-10-01 11:03:18 UTC 

*** This bug has been marked as a duplicate of bug 1148444 ***