Ask Your Question

Revision history [back]

| 2013-04-08 22:48:21 | 2013-04-25 18:45:44 | NULL | 0 | 1 | grzrc3 | cinder-scheduler | cinder-scheduler | 144940 | 0 | nova | | 2013-04-18 10:14:32 | 2013-04-24 09:49:08 | NULL | 0 | 6 | cinder | cinder-volume | cinder-volume | 43577 | 0 | nova |

I see that the update-time field of cinder-volume hasn't updated frequently -> so the cinder scheduler service marked it like as a service down.

I share you the formula which uses to check service down :

last_heartbeat = service['updated_at'] or service['created_at']
# Timestamps in DB are UTC.
elapsed = total_seconds(timeutils.utcnow() - last_heartbeat)
return abs(elapsed) <= FLAGS.service_down_time

FLAGS.service_down_time is 60s in default.

Hope it help you detect your problem...