Ask Your Question
0

Nova-compute not showing on nova service-list(controller)

asked 2015-02-18 11:29:16 -0600

oscar gravatar image

Hi,

Im not seeing the nova-compute service running for host compute on the controller side.

The service nova-compute is running on compute node but nova-compute log shows:

Error oslo.messaging._drivers.impl_rabbit [-] AMQP server on controller:5672 is unreachable: socket closed. Trying again in 30 seconds.

ntp is installed on both hosts but I did have a problem before when configuring. Running ntpq -c peers shows:

remote *LOCAL(0) refid .LOCL. st 5 t 1 when 28 poll 64 reach 377 deay 0.000 offset 0.000 jitter 0.000.

Any ideas?

edit retag flag offensive close merge delete

Comments

Could you paste nova.conf file of compute node. Where did you installed rabbitmq server. Whether rabbitmq server is running ? Add your rabbitmq server ip address, username and password in nova.conf file on compute node

rajcoumar gravatar imagerajcoumar ( 2015-02-19 21:43:00 -0600 )edit

Hello , How to get the log file?

Pauravi gravatar imagePauravi ( 2015-03-10 21:18:05 -0600 )edit

Hello the log file usually is locaten in /var/log/nova/nova-compute.log (The location is on the conf file.)

oscar gravatar imageoscar ( 2015-03-11 08:03:13 -0600 )edit

hi oscar I have the same problem , did you solve it ??

ebtihel gravatar imageebtihel ( 2017-04-02 06:10:44 -0600 )edit
add a comment

2 answers

Sort by ยป oldest newest most voted
0

answered 2015-02-18 12:02:06 -0600

Saikiran Veeravarapu gravatar image

updated 2015-02-19 15:34:18 -0600

Hi Oscar,

By seeing the log you pasted here, it seems like nova conductor is not running.

once check the status of nova-conductor like

 service nova-conductor  status

if the status of nova-conductor is down, restart the nova-conductor service like

 service nova-conductor restart

so once again restart the services like mysql,rabbitmq-server and all nova services. if there is any another issue let me know.

edit flag offensive delete link more

Comments

Thanks, I already restarted averything and checked the conf file. It clearly has to do with rabbitmq but no idea of what. How can I check if the port is allowed to connect through firewall. I ran: telnet controller 5672 on the compute node and it connected but then "Connection closed by foreign host

oscar gravatar imageoscar ( 2015-02-18 13:39:05 -0600 )edit

the mapping between hosts name and ip addresses may be went wrong in the etc/hosts. once again check the rabbitmq-server credentials in nova.conf like

  vi  /etc/nova/nova.conf

could you please display the compute log files once again?

Saikiran Veeravarapu gravatar imageSaikiran Veeravarapu ( 2015-02-19 05:21:14 -0600 )edit

your issue is solved or not

Saikiran Veeravarapu gravatar imageSaikiran Veeravarapu ( 2015-02-19 15:33:00 -0600 )edit

Hi, It is not.

oscar gravatar imageoscar ( 2015-02-20 10:17:51 -0600 )edit

It was solved apparently it had to do with the rabbit password for guest.

oscar gravatar imageoscar ( 2015-03-02 11:11:02 -0600 )edit
see more comments
0

answered 2015-02-19 14:58:34 -0600

oscar gravatar image

hi,

credentials seem to be fine..and controller is in /etc/hosts. The log now shows: 2015-02-18 15:23:16.098 4682 ERROR oslo.messaging._drivers.impl_rabbit [-] AMQP server on controller:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 3 seconds. 2015-02-19 14:52:38.612 2019 INFO nova.openstack.common.periodic_task [-] Skipping periodic task _periodic_update_dns because its interval is negative 2015-02-19 14:52:38.684 2019 INFO nova.virt.driver [-] Loading compute driver 'libvirt.LibvirtDriver' 2015-02-19 14:52:38.704 2019 INFO oslo.messaging._drivers.impl_rabbit [-] Connected to AMQP server on controller:5672 2015-02-19 14:52:38.713 2019 INFO oslo.messaging._drivers.impl_rabbit [-] Connected to AMQP server on controller:5672 2015-02-19 14:52:48.722 2019 WARNING nova.conductor.api [req-c5374e74-4c70-4bcd-9fcc-19d56db1881f None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? 2015-02-19 14:52:58.735 2019 WARNING nova.conductor.api [req-c5374e74-4c70-4bcd-9fcc-19d56db1881f None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? 2015-02-19 14:53:08.738 2019 WARNING nova.conductor.api [req-c5374e74-4c70-4bcd-9fcc-19d56db1881f None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? 2015-02-19 14:53:18.744 2019 WARNING nova.conductor.api [req-c5374e74-4c70-4bcd-9fcc-19d56db1881f None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? 2015-02-19 14:53:28.747 2019 WARNING nova.conductor.api [req-c5374e74-4c70-4bcd-9fcc-19d56db1881f None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? 2015-02-19 14:53:38.759 2019 WARNING nova.conductor.api [req-c5374e74-4c70-4bcd-9fcc-19d56db1881f None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? 2015-02-19 14:53:48.771 2019 WARNING nova.conductor.api [req-c5374e74-4c70-4bcd-9fcc-19d56db1881f None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? 2015-02-19 14:53:58.783 2019 WARNING nova.conductor.api [req-c5374e74-4c70-4bcd-9fcc-19d56db1881f None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? 2015-02-19 14:54:08.796 2019 WARNING nova.conductor.api [req-c5374e74-4c70-4bcd-9fcc-19d56db1881f None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? 2015-02-19 14:54:18.808 2019 WARNING nova.conductor.api [req-c5374e74-4c70-4bcd-9fcc-19d56db1881f None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? 2015-02-19 14:55:18.871 2019 WARNING nova.conductor.api [req-c5374e74-4c70-4bcd-9fcc-19d56db1881f None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? 2015-02-19 14:56:18.933 2019 WARNING nova.conductor.api [req-c5374e74-4c70-4bcd-9fcc-19d56db1881f None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor?

edit flag offensive delete link more

Comments

looks like now it is connecting but some other thing is failing

oscar gravatar imageoscar ( 2015-02-19 15:04:38 -0600 )edit

@oscar I have the same problem. In my environment i have already 3 compute nodes that communicates without error with conductor but a new one compute service start to talk successfully but after some changes stopped. my guess is something wrong with package versions happen (python-oslo.*)

tze gravatar imagetze ( 2017-11-02 05:55:19 -0600 )edit
add a comment

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

subscribe to rss feed

Stats

Asked: 2015-02-18 11:29:16 -0600

Seen: 4,403 times

Last updated: Feb 19 '15

Related questions

qemu guest agent connection

Can't delete or force-delete instance

A spice-html5 error

Network Injection not working

Duplicate services record

Timeout while waiting on RPC response

Slow glance queries > 118 secs

Improving disk performance?

Wrong libvirt UUID attaching volume to instance

unabel to send for git review