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.
Bug 913546 - Logrotate config missing
Summary: Logrotate config missing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: numad
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 915246 947781
TreeView+ depends on / blocked
 
Reported: 2013-02-21 12:53 UTC by Simon Matter
Modified: 2023-06-30 10:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
: 915246 (view as bug list)
Environment:
Last Closed: 2013-11-21 23:30:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1705 0 normal SHIPPED_LIVE numad bug fix and enhancement update 2013-11-20 21:51:59 UTC

Description Simon Matter 2013-02-21 12:53:47 UTC
Description of problem:
Numad by default logs to /var/log/numad.log and it seems it doesn't care have to clean it up.

Version-Release number of selected component (if applicable):
numad-0.5-8.20121015git.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. service numad start
2. watch /var/log/numad.log
3.
  
Actual results:
The file just grows and grows.

Expected results:
Logrotate should handle it like other log files.

Additional info:
I may have misshed something but I tried running numad on EL6.3 on two servers for tests and it seemed that on both servers the log file just kept growing endlessly. I expected the now supported numad package in EL6.4 may have a logrotate config in place but it still doesn't have one.

Comment 2 RHEL Program Management 2013-02-25 06:47:42 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 Jan Synacek 2013-05-22 09:23:39 UTC
Numad needs to be patched to be able to work with logrotate. I have sent a small patch to numad developers, so after it is accepted or implemented in any other way, I'll come up with a logrotate config and include it in the package.

Comment 10 errata-xmlrpc 2013-11-21 23:30:00 UTC
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.

http://rhn.redhat.com/errata/RHBA-2013-1705.html


Note You need to log in before you can comment on or make changes to this bug.