service glance-registry start produces spawning child processes

Bug #1065519 reported by John D'Esposito
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Glance
Invalid
Undecided
Unassigned

Bug Description

I am running Ubuntu 12.04 Folsom 2012.2. When I start the registry process I get the following in the registry.log

2012-10-11 08:59:55 13673 DEBUG glance.common.config [-] Loading glance-registry from /etc/glance/glance-registry-paste.ini load_paste_app /usr/lib/python2.7/dist-packages/glance/common/config.py:185
2012-10-11 08:59:55 5581 ERROR eventlet.wsgi.server [-] Removing dead child 13673
2012-10-11 08:59:55 13674 DEBUG glance.common.config [-] Loading glance-registry from /etc/glance/glance-registry-paste.ini load_paste_app /usr/lib/python2.7/dist-packages/glance/common/config.py:185
2012-10-11 08:59:55 5581 ERROR eventlet.wsgi.server [-] Removing dead child 13674
2012-10-11 08:59:55 13675 DEBUG glance.common.config [-] Loading glance-registry from /etc/glance/glance-registry-paste.ini load_paste_app /usr/lib/python2.7/dist-packages/glance/common/config.py:185
2012-10-11 08:59:55 5581 ERROR eventlet.wsgi.server [-] Removing dead child 13675
2012-10-11 08:59:55 13676 DEBUG glance.common.config [-] Loading glance-registry from /etc/glance/glance-registry-paste.ini load_paste_app /usr/lib/python2.7/dist-packages/glance/common/config.py:185

Also, the "glance index" command takes forever to return, like 1,000 seconds.

This seems similar to :
https://bugs.launchpad.net/glance/+bug/1042823

thanks
John

Revision history for this message
Brian Waldon (bcwaldon) wrote :

If you start glance-registry with the 'workers' config set to 0, what do the logs report?

Changed in glance:
status: New → Incomplete
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

In my experience I found this to be related to a misconfiguration of some sort, like an error in a pipeline or an error in keystone keystone_authtoken (if you're using Keystone).

As Brian suggested, if you switch to workers=0 you should see the service die instead of being stuck in a loop. Then troubleshooting becomes easier.

I think there's definitely grounds for a bug regarding usability. Glance shouldn't just spinning wheel, but detect the right error and die gracefully.

HTH,
Armando

Revision history for this message
Suraj Subramanian (surajsub) wrote :

I tried changing the number of workers=0 but the process still seems to be spawning ..

2012-10-17 16:31:25 23868 DEBUG glance.common.config [-] Loading glance-registry-keystone from /etc/glance/glance-api-paste.ini load_paste_app /usr/lib/python2.7/dist-packages/glance/common/config.py:185
2012-10-17 16:31:25 21164 ERROR eventlet.wsgi.server [-] Removing dead child 23868
2012-10-17 16:31:25 23869 DEBUG glance.common.config [-] Loading glance-registry-keystone from /etc/glance/glance-api-paste.ini load_paste_app /usr/lib/python2.7/dist-packages/glance/common/config.py:185
2012-10-17 16:31:25 21164 ERROR eventlet.wsgi.server [-] Removing dead child 23869
2012-10-17 16:31:25 23870 DEBUG glance.common.config [-] Loading glance-registry-keystone from /etc/glance/glance-api-paste.ini load_paste_app /usr/lib/python2.7/dist-packages/glance/common/config.py:185
2012-10-17 16:31:25 21164 ERROR eventlet.wsgi.server [-] Removing dead child 23870
2012-10-17 16:31:25 23871 DEBUG glance.common.config [-] Loading glance-registry-keystone from /etc/glance/glance-api-paste.ini load_paste_app /usr/lib/python2.7/dist-packages/glance/common/config.py:185
2012-10-17 16:31:25 21164 ERROR eventlet.wsgi.server [-] Removing dead child 23871
2012-10-17 16:31:25 23872 DEBUG glance.common.config [-] Loading glance-registry-keystone from /etc/glance/glance-api-paste.ini load_paste_app /usr/lib/python2.7/dist-packages/glance/common/config.py:185
2012-10-17 16:31:25 21164 ERROR eventlet.wsgi.server [-] Removing dead child 23872
2012-10-17 16:31:25 23873 DEBUG glance.common.config [-] Loading glance-registry-keystone from /etc/glance/glance-api-paste.ini load_paste_app /usr/lib/python2.7/dist-packages/glance/common/config.py:185
2012-10-17 16:31:25 21164 ERROR eventlet.wsgi.server [-] Removing dead child 23873
2012-10-17 16:31:25 23874 DEBUG glance.common.config [-] Loading glance-registry-keystone from /etc/glance/glance-api-paste.ini load_paste_app /usr/lib/python2.7/dist-packages/glance/common/config.py:185

Loading glance-registry-keystone from /etc/glance/glance-api-paste.ini load_paste_app /usr/lib/python2.7/dist-packages/glance/common/config.py:185
2012-10-17 16:31:25 21164 ERROR eventlet.wsgi.server [-] Removing dead child 23874

Revision history for this message
Brian Waldon (bcwaldon) wrote :

Suraj - setting workers=0 in the correct config file should prevent any child processes from being created. Make sure you set that value in the correct config file.

As several bugs related to this have been fixed, I'm going to close this as Invalid.

Changed in glance:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.