Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
DescriptionStephen Benjamin
2014-09-16 07:58:43 UTC
Description of problem:
/var/log/pulp is full of empty log files for pulp and the workers. All logs go to /var/log/messages or the journal (on rhel 7). We should use /var/log/pulp instead.
Version-Release number of selected component (if applicable):
6.0.4 GA
Comment 1RHEL Program Management
2014-09-16 08:03:17 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
I don't think pulp upstream should use /var/log/pulp/. We are currently using the standard log facilities given to us by the OS, and we have an explanation for our logging approach here:
https://pulp-user-guide.readthedocs.org/en/latest/troubleshooting.html#logging
As for the empty log files in /var/log/pulp, we are required by celery to have them. If there is an error during startup of a celery process, before it switches to the system log facility, it will log that error to its file in /var/log/pulp/.
All of that said, it could be appropriate for the downstream product to use a rsyslog rule to redirect log messages to a file. There have been multiple previous discussions about why pulp cannot do that upstream.
I suggest either closing this bug, or please provide a more detailed request.
Why exactly are they required by celery? Certainly that must be fixable?
My preference would be those files go away on rhel 7 and on el6, ship the rsyslog rule to use /var/log/pulp.
I don't think this should be closed at all, are those two things really impossible upstream?
I've seen lots of Satellite users confused by the presence of these empty log files.
As is, Celery will not start without being given some place to log, and it does not support syslog by default. Believe it or not, it is important that we continue to have these log files as this is where startup errors will be logged. If Celery is unable to start Pulp, error messages about that will go to those files. This is very similar to Apache's error_log. If Apache cannot start Pulp, it will log to /var/log/httpd/{ssl_,}error_log.
Once Celery starts Pulp, Pulp will configure logging (i.e., redirect all logging to syslog).
I have two ideas to make this clearer to users:
1) We could rename the log files to include the word "startup". For example, reserved_resource_worker-0-startup.log or similar.
2) We may be able to inject one log statement to those log files just before configuring logging that says something like "initial startup successful, redirecting logs to syslog."
How does that sound?
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.
https://access.redhat.com/errata/RHBA-2016:1501