Yep, you have to configure the proxy logging middleware like this, and if youre logging local you dont need to use the udp logging, you can log locally like this
[DEFAULT] section should look like this : log_name = swift-proxy-server log_facility = LOG_LOCAL0 log_level = DEBUG You need to add the proxy-logging filtering to the main pipeline [pipeline:main] pipeline = catch_errors healthcheck cache authtoken swiftauth proxy-logging proxy-server Then you need to activate the filter , adding this section at the end of the config [filter:proxy-logging] use = egg:swift#proxy_logging That should be enough, of course you need to configure your syslog to route your logs wherever you want, for example in out /etc/rsyslog.d/ , we create an 10-swift.conf , with this content :) local0.*;local0.!notice /var/log/swift/proxy.log local0.notice /var/log/swift/proxy.error local0.* Best Lean Mercadolibre Cloudbuilders On Fri, Jan 18, 2013 at 5:35 AM, Robert van Leeuwen < robert.vanleeu...@spilgames.com> wrote: > Hi, > > I'm trying to get the access log for the swift-proxy-server working. > I'm logging to UDP and the swauth logs are getting there. > However the access logs are not created. > We are running swift 1.7.5 on Scientific Linux > > proxy-server.conf > [default] > log_facility = LOG_LOCAL6 > log_udp_host = 127.0.0.1 > > Anything I might be missing? > > P.S. I've run tcpdump to capture all the logs swift sends to make sure its > not a syslog configuration issue. > > Thx, > Robert > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
