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:
From Trey Dockendorf on pulp-list: "I've been using this on EL6 :programname, isequal, "pulp" -/var/log/pulp.log & ~ I think as long as that comes before the line that sets the /var/log/messages logging then the "& ~" will discard the messages and keep them from making it to /var/log/messages."
Moved to https://pulp.plan.io/issues/654