Comment 5 for bug 1054183

This has not been fixed...

On a fresh checkout of devstack, I now run into a glance service that won't respond. This, however, isn't the worst part. The worst part is that the glance API server is hung in a perpetual loop, eating up disk space for logs at an alarming rate.

After just a few seconds, the glance API log file (screen-ga-api.log) was at 17MB:

jpipes@uberbox:~/repos/devstack$ ls -alh /opt/stack/logs/screen-g-api*
-rw-rw-r-- 1 jpipes jpipes 17M Nov 1 13:56 /opt/stack/logs/screen-g-api.2012-11-01-134816.log
lrwxrwxrwx 1 jpipes jpipes 50 Nov 1 13:49 /opt/stack/logs/screen-g-api.log -> /opt/stack/logs/screen-g-api.2012-11-01-134816.log

The log file looks like this: http://paste.openstack.org/show/23512/

with the child process attempting to create the consumer, failing, and then the parent process launching another child process, which does the same thing, continuing ad-infinitum.

Basically, at a minimum, I believe that the AMQP negotiation should at least be *tried* before the child processes are spawned so that basic things like this can be caught before the child process starts. Either that, or the parent must have a wait to stop spawning on repeated failures.