-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ben,
This has been resolved by issue #654 and merged to 2.6-testing. The next 2.6 build will update RTD. It was general consensus that the pulp project documentation should not be suggesting rsyslog configuration changes at all for these reasons: 1. rsyslog.conf is general system configuration. 2. rsyslog.conf contains scripting language and not configuration. So the resolution was to replace the incorrect documentation with a reference to rsyslog documentation. That said, your suggests are valuable to the pulp community and I would encourage you to continue to share them on the mailing list and perhaps and blog post. Thanks, Jeff https://pulp.plan.io/issues/654 On 05/01/2015 02:41 AM, ben.stan...@exemail.com.au wrote: > I have previously pointed out that the pulp documentation on how > to configure rsyslogd is incorrect. The thread ended at > > https://www.redhat.com/archives/pulp-list/2015-January/msg00022.html > > The pulp documentation on configuring rsyslogd is at > > https://pulp.readthedocs.org/en/latest/user-guide/troubleshooting.html > > There is a section on rsyslogd. It is still wrong. > > The problem is that rsyslogd has no log facility called pulp, so > the documented solution does not work. > > Inserting the following text into /etc/rsyslog.conf causes pulp and > celery log messages to be diverted to /var/log/pulp.log (and > removed from /var/log/messages): > > ------ /etc/rsyslog.conf (before /var/log/messages line) --------- > # Log messages from pulp to its own log file. if $programname == > 'pulp' or $programname == 'celery' then { action(type="omfile" > file="/var/log/pulp.log") stop } > ------------------------------------------------------------------ > > The code fragment above should be inserted before any catch-all > lines such as /var/log/messages. > > The rsyslog documentation states that the RainerScript-Based > Filters (as used above) are to be used in preference to the legacy > format. http://rsyslog.com/doc/rsyslog_conf_filter.html > > I also tried to turn on logging the PID of the source process, to > assist with the confusing log messages complained about here > https://www.redhat.com/archives/pulp-list/2015-April/msg00066.html > > I found that inserting the line $SysSock.UsePIDFromSystem on in > combination with using the imuxsock module provided PIDs on some of > the log lines, but not all. This problem is not completely solved > yet. > > How can this change be inserted into the documentation? Ben > Stanley. > > > _______________________________________________ Pulp-list mailing > list Pulp-list@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-list > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVQ5S2AAoJEM9lW7UwFwZXw6kP/iF6X7G9VvRO9ZPhV1ERKwT2 bjm+63xD6cmKc2sPKblAYbiITBQrLeVRz/Q18zcBoswUqhPlrVzYxpi124k7LoPp F+qAjq/2x4QohUh0BaDhfKZlrUD5jwofTI2OI8HHH1iJAtmTYrQckPb9Vk0dKbnT k0zQSS1h0l6+KzI9N6JJAVBY1Y9c3n4o3ztJz62Pl0xni4tEucHhdC6wCcNjML7y TxJWH8yOKw+ChV/BEPdAnE//OJ7wJR69ITbc8uqUMUa8frMk6U8NoCad8tPryml3 M157O4aKuySSjh2Z/P05sq6gGvbQWcwa1XaYprX/DwGhrcuGtdaLE1ZbZt9I9izT w2l69ypThB27NVLrDCfqtbd7uGjxQYxM1ALicLFacLIGBDJxdokQMslCY3FA3d5q uMSBpS9VAtA7/bbrL6nVj5RCHEVDJuyphUI5X5lY3MtR4a6LptyGqf16vZHbCtLD 519BLT4TeYwJQM893wLUiNBmkGsfTg9QIsJRk6kTt8Aqt9aMbd7iJBvBEH/E1Ftw uYiBhDqWPwqtPY8Vf52nQEqD0RbvEMV4nZmPPtuTpaAV9IxIRldtuUSqAeSswVCg rclLA1Q6s7IpO6uMzbe0ekYQY7i4oFAtCWXx1OWpPhqKzSSEmYuGgHGj6ikAvAb8 w0zXTfOEFNkQIQwUYadQ =THxN -----END PGP SIGNATURE----- _______________________________________________ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list