OpenStack Object Storage (swift)

logging problem with keystone

Asked by David Kranz

I finally got swift to work with keystone but was hampered by getting these errors

Aug 15 11:06:55 se10-1eth0 proxy-server STDOUT: No handlers could be found for logger "keystone.middleware.auth_token" (txn: tx5c3ef24441c74a1597cfca4400b25a48)

I also don't get any proxy log messages after the initial series of "Started child ..".
I am not sure if these issues are related. How do I get rid of this error and see the log messages from auth_token?
Here is my proxy-server.conf file which seemed to work fine for logging without keystone:

[DEFAULT]
bind_ip = 172.18.1.156
bind_port = 8080
workers = 16
user = swift
log_facility = LOG_LOCAL1

[pipeline:main]
pipeline = catch_errors healthcheck cache tempurl authtoken keystoneauth proxy-server

[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true
log_level = INFO

[filter:catch_errors]
use = egg:swift#catch_errors

[filter:tempauth]
use = egg:swift#tempauth
user_system_root = testpass .admin .reseller_admin
user_slogging_slogging = slogging .admin
user_test_tester = testing .admin
user_taco_test = taco .admin
user_dispersion_test = dispersion .admin
user_MedCloud_test = cloudisgood .admin
log_level = INFO
allow_overrides = true

[filter:tempurl]
use = egg:swift#tempurl

[filter:keystoneauth]
use = egg:swift#keystoneauth
operator_roles = admin, swiftoperator
is_admin = true

[filter:authtoken]
paste.filter_factory = keystone.middleware.auth_token:filter_factory
auth_host = se09-4.qrclab.com
auth_port = 35357
auth_protocol = http
admin_tenant_name = service
admin_user = swift
admin_password = swift
delay_auth_decision = 1
memcache_servers = 172.18.1.156:11211
signing_dir = /var/lib/swift/keystone-signing

[filter:healthcheck]
use = egg:swift#healthcheck

[filter:cache]
use = egg:swift#memcache
memcache_servers = 172.18.1.156:11211

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Object Storage (swift) Edit question
Assignee:
No assignee Edit question
Solved by:
David Kranz
Solved:
Last query:
Last reply:
Revision history for this message
David Kranz (david-kranz) said : 		#1

I figured out what is going on. I had upgraded to 1.6 and now need to put proxy-logging in the pipeline. When I do this the logger handler error goes away. However I still don't see the log messages from auth_token which seems to be due to the way it sets up logging. If I change auth_token to initialize logging the same way keystoneauth does then I see the log messages. I will file a bug with keystone but it seems that the behavior of auth_token depends on the configuration of the app using it as middleware which is unfortunate.