Hello, After I reboot my controller node (which is running all the nova services), nova-mange only lists two nova services - nova-consoleauth and nova-scheduler (which is not started yet). What I am trying to find out is why only three of the nova service is started? And how are they started? Any pointers to config or log file would be very appreciated. root at sonoma<mailto:root at sonoma>:~# nova-manage service list 2012-09-29 04:21:39 DEBUG nova.utils [req-738fb5ff-175f-4d1d-97fb-91c78c47d6a5 None None] backend <module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc'> f rom (pid=2463) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658 Binary Host Zone Status State Updated_At nova-scheduler sonoma nova enabled XXX 2012-09-29 10:52:30 nova-consoleauth sonoma nova enabled :-) 2012-09-29 11:21:38 root at sonoma<mailto:root at sonoma>:~# service mysql status mysql start/running, process 1684 root at sonoma<mailto:root at sonoma>:~# service nova-api status nova-api start/running, process 1168 root at sonoma<mailto:root at sonoma>:~# service nova-cert status nova-cert stop/waiting root at sonoma<mailto:root at sonoma>:~# service nova-compute status nova-compute stop/waiting root at sonoma<mailto:root at sonoma>:~# service nova-consoleauth status nova-consoleauth start/running, process 1483 root at sonoma<mailto:root at sonoma>:~# service nova-network status nova-network stop/waiting root at sonoma<mailto:root at sonoma>:~# service nova-scheduler status nova-scheduler stop/waiting root at sonoma<mailto:root at sonoma>:~# service nova-vncproxy status nova-vncproxy start/running, process 1163 root at sonoma<mailto:root at sonoma>:~# service nova-volume status nova-volume stop/waiting root at sonoma<mailto:root at sonoma>:~# root at sonoma<mailto:root at sonoma>:~# ls -l /etc/rc?.d/*nova* ls: cannot access /etc/rc?.d/*nova*: No such file or directory Thank you, Ahmed. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120929/63c1f944/attachment.html>