Project

Profile

Help

Issue #654

closed

Users are reporting that our rsyslog config example does not work

Added by rbarlow about 9 years ago. Updated almost 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
2.4.3
Platform Release:
2.6.1
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation, Pulp 2
Sprint:
Quarter:

Description

Document URL:
https://pulp-user-guide.readthedocs.org/en/latest/troubleshooting.html#logging

Section Number and Name:
Logging

Describe the issue:
The following is an e-mail from Ben Stanley on Pulp List:

The documentation there regarding rsyslogd is incorrect (at least for RHEL7).

Configuring the log with the line

pulp.* /var/log/pulp.log

causes the following error when rsyslogd starts up:
rsyslogd-<pid>: unknown facility name "pulp"

rsyslogd has no log facility called pulp, so it can't be configured in the
manner described in the logging section of the troubleshooting page. The
list of facilities is fixed at compile time. Filters must be used to
select the messages instead.

The documentation for filters in rsyslogd is located here:
http://www.rsyslog.com/doc/rsyslog_conf_filter.html

The RainerScript filters allow you to select a sub-set of messages to put
into a particular file like this:

if $programname == 'pulp' then {
action(type="omfile" file="/var/log/pulp.log")
}

However, I don't know how to exclude pulp messages from /var/log/messages .

Suggestions for improvement:
Make sure our logging instructions are either accurate, or link to rsyslog docs that discuss how to filter.

Additional information:

+ This bug was cloned from Bugzilla Bug #1180163 +

Also available in: Atom PDF