Bug 1036359

Summary:	ejabberd logs not reopened after rotation
Product:	[Fedora] Fedora	Reporter:	Lucas Maneos <redhat>
Component:	ejabberd	Assignee:	Peter Lemenkov <lemenkov>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	erlang, jkaluza, lemenkov, martin, rstory
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:	2014-09-01 11:28:22 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 Lucas Maneos 2013-12-01 12:38:18 UTC

Description of problem:


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

ejabberd-2.1.13-7.fc20.x86_64

How reproducible:


Steps to Reproduce:
1. Make sure ejabberd is running and logrotate is enabled.
2. Wait until logrotate runs.
3. Check contents of /var/log/ejabberd/ejabberd.log.

Actual results:

0 size file that never gets updated.

Expected results:

File containing log entries for events as they occur.

Additional info:

/etc/logrotate.d/ejabberd is trying to run /usr/sbin/ejabberdctl, but ejabberdctl is installed in /usr/bin now.

Comment 1 rstory 2014-02-18 21:26:35 UTC

ejabberd.log is size 0 and not updated, and actual logging is still going to the rotated log file, ejabberd.log-YYYYMMDD..

Comment 2 Peter Lemenkov 2014-09-01 11:28:22 UTC

This bug should be closed in Rawhide now and will be closed in Fedora 21.