Created attachment 1101145[details]
swift log
Description of problem:
HAProxy logs show up in /var/log/swift/swift.log
Version-Release number of selected component (if applicable):
RHEL-OSP 7.1
How reproducible:
100%
Steps to Reproduce:
1. Check /var/log/swift/swift.log on the overcloud controller
Actual results:
HAProxy logs show up.
Expected results:
Only swift related logs are shown.
Additional info:
Attaching swift.log
One can use the "programname" field in rsyslog to also select which logs go where instead of facility.
E.g.
if $programname == 'haproxy' then
action(type="omfile", file="/var/log/haproxy.log")
stop
endif
Then be sure to order that before the openstack-swift.conf file.
-peter
Comment 8Lars Kellogg-Stedman
2016-08-29 17:22:54 UTC
Re: comment #7, that's largely what I was thinking.
In particular, I think that we should just modify all the configs to log using the "daemon" facility and then use programname to filtering to separate log files, and leave the local* facilities for use by the local administrator.
Created attachment 1101145 [details] swift log Description of problem: HAProxy logs show up in /var/log/swift/swift.log Version-Release number of selected component (if applicable): RHEL-OSP 7.1 How reproducible: 100% Steps to Reproduce: 1. Check /var/log/swift/swift.log on the overcloud controller Actual results: HAProxy logs show up. Expected results: Only swift related logs are shown. Additional info: Attaching swift.log