| 2015-02-16 11:24:44 |
Mark Goddard |
description |
With syslog enabled on Juno (enable_syslog=True in glance-api.conf), glance spins on startup, consuming all available CPU cycles.
With some carefully placed calls to exit(), the line in glance causing the problem was determined to be https://github.com/openstack/glance/blob/stable/juno/glance/openstack/common/log.py#L523. After this point the code gets lost in logging.handlers.SyslogHandler().
I noticed that the <component>.openstack.common.log source file was somewhat different in glance compared to several other OpenStack components. An update to glance.openstack.common missed the juno branch by a couple of commits https://github.com/openstack/glance/commit/d4f890798a0588a80e21fad044d4df5d0964dc70. Cherry picking this commit fixed the issue for me. |
With syslog enabled on Juno (use_syslog=True in glance-api.conf), glance spins on startup, consuming all available CPU cycles.
With some carefully placed calls to exit(), the line in glance causing the problem was determined to be https://github.com/openstack/glance/blob/stable/juno/glance/openstack/common/log.py#L523. After this point the code gets lost in logging.handlers.SyslogHandler().
I noticed that the <component>.openstack.common.log source file was somewhat different in glance compared to several other OpenStack components. An update to glance.openstack.common missed the juno branch by a couple of commits https://github.com/openstack/glance/commit/d4f890798a0588a80e21fad044d4df5d0964dc70. Cherry picking this commit fixed the issue for me. |
|
