ERROR ao criar nova Instancia

32 views
Skip to first unread message

nelson....@gmail.com

unread,
Jul 27, 2018, 1:49:00 PM7/27/18
to Comunidade Openstack Brasil
Boa tarde a todos,

Estou enfrentando um erro ao criar uma nova INSTANCIA.

basicamente ele da erro na hora de checar e poder liberar para uso, segue erro no log:

2018-07-27 09:34:18.980 900 ERROR nova.conductor.manager     return cctxt.call(ctxt, 'select_destinations', **msg_args)
2018-07-27 09:34:18.980 900 ERROR nova.conductor.manager   File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", l
ine 174, in call
2018-07-27 09:34:18.980 900 ERROR nova.conductor.manager     retry=self.retry)
2018-07-27 09:34:18.980 900 ERROR nova.conductor.manager   File "/usr/lib/python2.7/site-packages/oslo_messaging/transport.py", li
ne 131, in _send
2018-07-27 09:34:18.980 900 ERROR nova.conductor.manager     timeout=timeout, retry=retry)
2018-07-27 09:34:18.980 900 ERROR nova.conductor.manager   File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriv
er.py", line 559, in send
2018-07-27 09:34:18.980 900 ERROR nova.conductor.manager     retry=retry)
2018-07-27 09:34:18.980 900 ERROR nova.conductor.manager   File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriv
er.py", line 548, in _send
2018-07-27 09:34:18.980 900 ERROR nova.conductor.manager     result = self._waiter.wait(msg_id, timeout)
2018-07-27 09:34:18.980 900 ERROR nova.conductor.manager   File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriv
er.py", line 440, in wait
2018-07-27 09:34:18.980 900 ERROR nova.conductor.manager     message = self.waiters.get(msg_id, timeout=timeout)
2018-07-27 09:34:18.980 900 ERROR nova.conductor.manager   File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriv
er.py", line 328, in get
2018-07-27 09:34:18.980 900 ERROR nova.conductor.manager     'to message ID %s' % msg_id)
2018-07-27 09:34:18.980 900 ERROR nova.conductor.manager MessagingTimeout: Timed out waiting for a reply to message ID 56f0b468403
c457e9bd326275a194dcf
2018-07-27 09:34:18.980 900 ERROR nova.conductor.manager 
2018-07-27 09:35:06.330 900 WARNING nova.scheduler.utils [req-247b0a7d-9cc7-4c67-885c-b964758c6cb1 115dd262e62d4ee8838d217271c156c
2 db12130a9e9c40669bc17f3e35800629 - default default] Failed to compute_task_build_instances: Timed out waiting for a reply to mes
sage ID 56f0b468403c457e9bd326275a194dcf: MessagingTimeout: Timed out waiting for a reply to message ID 56f0b468403c457e9bd326275a
194dcf
2018-07-27 09:35:08.732 900 WARNING nova.scheduler.utils [req-247b0a7d-9cc7-4c67-885c-b964758c6cb1 115dd262e62d4ee8838d217271c156c
2 db12130a9e9c40669bc17f3e35800629 - default default] [instance: 0385862d-05bd-466f-8c63-9065f229d82f] Setting instance to ERROR s
tate.: MessagingTimeout: Timed out waiting for a reply to message ID 56f0b468403c457e9bd326275a194dcf
2018-07-27 09:35:58.372 900 INFO oslo_messaging._drivers.amqpdriver [req-247b0a7d-9cc7-4c67-885c-b964758c6cb1 115dd262e62d4ee8838d217271c156c2 db12130a9e9c40669bc17f3e35800629 - default default] No calling threads waiting for msg_id : 56f0b468403c457e9bd326275a194dcf


Pelo que andei lendo pode ser no RABBIT, mas o mesmo esta iniciardo:

[root@controller nova]# systemctl status rabbitmq-server.service -l
â— rabbitmq-server.service - RabbitMQ broker
   Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2018-07-27 11:00:06 EDT; 2h 48min ago
 Main PID: 901 (beam)
   Status: "Initialized"
   CGroup: /system.slice/rabbitmq-server.service
           â”œâ”€ 901 /usr/lib64/erlang/erts-8.3.5.3/bin/beam -W w -A 64 -P 1048576 -t 5000000 -stbt db -K true -- -root /usr/lib64/erlang -progname erl -- -home /var/lib/rabbitmq -- -pa /usr/lib/rabbitmq/lib/rabbitmq_server-3.6.5/ebin -noshell -noinput -s rabbit boot -sname rabbit@controller -boot start_sasl -config /etc/rabbitmq/rabbitmq -kernel inet_default_connect_options [{nodelay,true}] -sasl errlog_type error -sasl sasl_error_logger false -rabbit error_logger {file,"/var/log/rabbitmq/rab...@controller.log"} -rabbit sasl_error_logger {file,"/var/log/rabbitmq/rab...@controller-sasl.log"} -rabbit enabled_plugins_file "/etc/rabbitmq/enabled_plugins" -rabbit plugins_dir "/usr/lib/rabbitmq/lib/rabbitmq_server-3.6.5/plugins" -rabbit plugins_expand_dir "/var/lib/rabbitmq/mnesia/rabbit@controller-plugins-expand" -os_mon start_cpu_sup false -os_mon start_disksup false -os_mon start_memsup false -mnesia dir "/var/lib/rabbitmq/mnesia/rabbit@controller" -kernel inet_dist_listen_min 25672 -kernel inet_dist_listen_max 25672
           â”œâ”€1267 erl_child_setup 1024
           â”œâ”€1366 inet_gethost 4
           â””─1367 inet_gethost 4

Jul 27 10:58:47 controller.localdomain systemd[1]: Starting RabbitMQ broker...
Jul 27 10:59:30 controller.localdomain rabbitmq-server[901]: RabbitMQ 3.6.5. Copyright (C) 2007-2016 Pivotal Software, Inc.
Jul 27 10:59:30 controller.localdomain rabbitmq-server[901]: ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
Jul 27 10:59:30 controller.localdomain rabbitmq-server[901]: ##  ##
Jul 27 10:59:30 controller.localdomain rabbitmq-server[901]: ##########  Logs: /var/log/rabbitmq/rab...@controller.log
Jul 27 10:59:30 controller.localdomain rabbitmq-server[901]: ######  ##        /var/log/rabbitmq/rab...@controller-sasl.log
Jul 27 10:59:30 controller.localdomain rabbitmq-server[901]: ##########
Jul 27 10:59:30 controller.localdomain rabbitmq-server[901]: Starting broker...
Jul 27 11:00:06 controller.localdomain systemd[1]: Started RabbitMQ broker.
Jul 27 11:00:06 controller.localdomain rabbitmq-server[901]: completed with 6 plugins.

Muito Obrigado Pela ajuda

Nelson

Gui Maluf

unread,
Jul 27, 2018, 1:56:52 PM7/27/18
to openst...@googlegroups.com
Faltou um pouco da cabeça do log, pra saber qual tarefa ele executou que disparou esse timeout.
Se foi no neutron uma config no nova.conf que é útil "vif_plugging_timeout=300"

Esse slide me ajudou bastante a entender e corrigir algumas questões do rabbit: https://pt.slideshare.net/michaelklishin/troubleshooting-common-oslomessaging-and-rabbitmq-issues

--
--
Você recebeu esta mensagem porque está inscrito no Grupo "openstack-br".
Para postar neste grupo, envie um e-mail para
openst...@googlegroups.com
Para cancelar a sua inscrição neste grupo, envie um e-mail para
openstack-br...@googlegroups.com
Para ver mais opções, visite este grupo em
http://groups.google.com/group/openstack-br

---
Você recebeu essa mensagem porque está inscrito no grupo "Comunidade Openstack Brasil" dos Grupos do Google.
Para cancelar inscrição nesse grupo e parar de receber e-mails dele, envie um e-mail para openstack-br...@googlegroups.com.
Para mais opções, acesse https://groups.google.com/d/optout.


--
guilherme \n
\t maluf
Reply all
Reply to author
Forward
0 new messages