Ask Your Question
1

Why does nova-manage service list shows XXX ?

asked 2014-08-26 02:03:09 -0500

David Hill gravatar image

Hi guys,

I was wondering, our lab is currently running ceilometer/heat/etc and I've noticed that all ceilometer services are shown as XXX even though they are avaialble and fully functionnal?

Binary           Host                                 Zone             Status     State Updated_At
nova-compute     cmp02            nova             enabled    :-)   2014-08-26 06:57:42
nova-network     cmp02            internal         enabled    :-)   2014-08-26 06:57:39
ceilometer-agent-compute cmp01            internal         enabled    XXX   2013-05-14 22:27:46
nova-compute     cmp01            nova             enabled    :-)   2014-08-26 06:57:34
nova-network     cmp01            internal         enabled    :-)   2014-08-26 06:57:39
ceilometer-agent-compute cmp02            internal         enabled    XXX   2013-05-14 22:27:57
nova-consoleauth ctrl02           internal         enabled    :-)   2014-08-26 06:57:38
nova-scheduler   ctrl02           internal         enabled    :-)   2014-08-26 06:57:41
ceilometer-agent-central ctrl02           internal         enabled    XXX   2013-05-14 22:27:50
nova-network     ctrl02           internal         enabled    :-)   2014-08-26 06:57:37
ceilometer-collector ctrl02           internal         enabled    XXX   2013-05-14 22:27:50
nova-volume      ctrl02           internal         enabled    XXX   None
nova-conductor   ctrl02           internal         enabled    :-)   2014-08-26 06:57:42
nova-conductor   cmp02            internal         enabled    :-)   2014-08-26 06:57:42
nova-conductor   cmp01            internal         enabled    :-)   2014-08-26 06:57:41
nova-conductor   ctrl01           internal         enabled    :-)   2014-08-26 06:57:43
nova-console     ctrl02           internal         enabled    :-)   2014-08-26 06:57:37
nova-cert        ctrl02           internal         enabled    :-)   2014-08-26 06:57:36
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-08-26 10:35:32 -0500

mpetason gravatar image

Services check in with the Database and update their availability. If the service takes too long to update and you run a check before it says it is available then it will show XXX instead of up even if the service is running. You'll run into this with nova-compute when there is a lot of load and nova-compute is doing a bunch of functions before reporting back the current status of the service.

You can troubleshoot this by looking at the ceilometer logs to see if it's getting stuck on anything. It is possible that Ceilometer is putting notifications on RabbitMQ and no one is consuming them to update the database about it's current status.

I don't think this will cause you to run into issues(not sure though), when Nova-compute doesn't update fast enough the node isn't considered for scheduling for new instances if the check returns XXX when scheduling happens.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-08-26 02:03:09 -0500

Seen: 925 times

Last updated: Aug 26 '14