glance startup gives ERROR: Could not bind to 0.0.0.0:9292 after trying for 30 seconds on stable-kilo after attempting service restart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Won't Fix
|
Undecided
|
Bhargavi |
Bug Description
Have a running stable-kilo setup, recently did a restart of all services and glance won't start up. Following error in g-api log:
2015-08-13 09:44:29.916 28813 DEBUG glance.
2015-08-13 09:44:29.916 28813 DEBUG glance.
2015-08-13 09:44:29.916 28813 DEBUG glance.
2015-08-13 09:44:29.916 28813 DEBUG glance.
2015-08-13 09:44:29.916 28813 DEBUG glance.
^[kERROR: Could not bind to 0.0.0.0:9292 after trying for 30 seconds
And same in the g-reg logs:
-08-13 09:44:20.743 28806 DEBUG glance.
2015-08-13 09:44:20.743 28806 DEBUG glance.
2015-08-13 09:44:20.743 28806 DEBUG glance.
2015-08-13 09:44:20.743 28806 DEBUG glance.
2015-08-13 09:44:20.743 28806 DEBUG glance.
2015-08-13 09:44:20.744 28806 DEBUG glance.
2015-08-13 09:44:20.744 28806 DEBUG glance.
2015-08-13 09:44:20.744 28806 DEBUG glance.
ERROR: Could not bind to 0.0.0.0:9191 after trying for 30 seconds
Changed in glance: | |
status: | New → Confirmed |
Changed in glance: | |
assignee: | nobody → Mohammed Ashraf (mohammed-asharaf) |
Changed in glance: | |
assignee: | Mohammed Ashraf (mohammed-asharaf) → nobody |
Changed in glance: | |
assignee: | nobody → Bhargavi (bhargavi-c81) |
Changed in glance: | |
status: | Confirmed → Incomplete |
Do the original glance processes still have the port open?
Does
# lsof -iTCP -sTCP:LISTEN
indicate something listening on 9191/9292?