[Rdo-list] no valid host was found: nova problem
pauline phaure
phaurep at gmail.com
Mon Apr 20 12:33:53 UTC 2015
ok, then evrything is fine with my rabbitmq
[root at localhost ~]# iptables -S |grep 5672
-A INPUT -s 192.168.2.34/32 -p tcp -m multiport --dports 5671,5672 -m
comment --comment "001 amqp incoming amqp_192.168.2.34" -j ACCEPT
-A INPUT -s 192.168.2.35/32 -p tcp -m multiport --dports 5671,5672 -m
comment --comment "001 amqp incoming amqp_192.168.2.35" -j ACCEPT
do you have any other idea about what it may be happening with my
installation?
2015-04-20 14:26 GMT+02:00 Marius Cornea <marius at remote-lab.net>:
> That's the port used by rabbit nodes for communicating in a cluster.
> You should check the docs here[1] for further digging into clustering:
>
> https://www.rabbitmq.com/clustering.html
>
> On Mon, Apr 20, 2015 at 2:15 PM, pauline phaure <phaurep at gmail.com> wrote:
> > is it normal the the port for tcp4 is 25672???
> >
> > 2015-04-20 14:10 GMT+02:00 pauline phaure <phaurep at gmail.com>:
> >>
> >> [root at localhost ~]# rabbitmqctl status
> >> Status of node rabbit at localhost ...
> >> [{pid,18863},
> >> {running_applications,[{rabbit,"RabbitMQ","3.3.5"},
> >> {os_mon,"CPO CXC 138 46","2.2.14"},
> >> {mnesia,"MNESIA CXC 138 12","4.11"},
> >> {xmerl,"XML parser","1.3.6"},
> >> {sasl,"SASL CXC 138 11","2.3.4"},
> >> {stdlib,"ERTS CXC 138 10","1.19.4"},
> >> {kernel,"ERTS CXC 138 10","2.16.4"}]},
> >> {os,{unix,linux}},
> >> {erlang_version,"Erlang R16B03-1 (erts-5.10.4) [source] [64-bit]
> >> [smp:16:16] [async-threads:30] [hipe] [kernel-poll:true]\n"},
> >> {memory,[{total,91191840},
> >> {connection_procs,2848136},
> >> {queue_procs,1327752},
> >> {plugins,0},
> >> {other_proc,13932712},
> >> {mnesia,268832},
> >> {mgmt_db,0},
> >> {msg_index,87144},
> >> {other_ets,948952},
> >> {binary,48239344},
> >> {code,16698259},
> >> {atom,602729},
> >> {other_system,6237980}]},
> >> {alarms,[]},
> >> {listeners,[{clustering,25672,"::"},{amqp,5672,"::"}]},
> >> {vm_memory_high_watermark,0.4},
> >> {vm_memory_limit,4967161856},
> >> {disk_free_limit,50000000},
> >> {disk_free,49428885504},
> >> {file_descriptors,[{total_limit,924},
> >> {total_used,80},
> >> {sockets_limit,829},
> >> {sockets_used,78}]},
> >> {processes,[{limit,1048576},{used,921}]},
> >> {run_queue,0},
> >> {uptime,124}]
> >> ...done.
> >>
> >>
> >> 2015-04-20 14:08 GMT+02:00 pauline phaure <phaurep at gmail.com>:
> >>>
> >>>
> >>>
> >>> [root at localhost ~]# netstat -nltp |grep 5672
> >>> tcp 0 0 0.0.0.0:25672 0.0.0.0:*
> >>> LISTEN 1927/beam.smp
> >>> tcp6 0 0 :::5672 :::*
> >>> LISTEN 1927/beam.smp
> >>>
> >>>
> >>> 2015-04-20 13:56 GMT+02:00 Marius Cornea <marius at remote-lab.net>:
> >>>>
> >>>> Hi Pauline,
> >>>>
> >>>> I suspect the issues are caused by the rabbitmq connection. Check that
> >>>> it's running and can be reached on 192.168.2.34:5672 (server is
> >>>> running, listening on that address/port, no firewall rule preventing
> >>>> connections).
> >>>>
> >>>> On Mon, Apr 20, 2015 at 1:32 PM, pauline phaure <phaurep at gmail.com>
> >>>> wrote:
> >>>> > i tried with cirros actually and it didn't work. I don't think it's
> a
> >>>> > problem of ressources. I'm on baremetal and I only have 4 VMs
> spawned
> >>>> >
> >>>> > 2015-04-20 13:28 GMT+02:00 Mohammed Arafa <mohammed.arafa at gmail.com
> >:
> >>>> >>
> >>>> >> Pauline it could be a number of issues including too little CPU or
> >>>> >> ram or
> >>>> >> disk. Try with the cirros image first
> >>>> >>
> >>>> >> Tokens in the service project do not expire as far as I know
> >>>> >>
> >>>> >> On Apr 20, 2015 4:53 AM, "pauline phaure" <phaurep at gmail.com>
> wrote:
> >>>> >>>
> >>>> >>> I think it's because of an authentication issue as my plateform
> was
> >>>> >>> working fine friday. May be the tokens given to nova, neutron...
> has
> >>>> >>> expired?? how can I fix it if so. plz help
> >>>> >>>
> >>>> >>> 2015-04-20 10:23 GMT+02:00 pauline phaure <phaurep at gmail.com>:
> >>>> >>>>
> >>>> >>>> grep ERROR nova-scheduler.log
> >>>> >>>>
> >>>> >>>> 2015-04-17 15:41:25.119 1976 ERROR
> >>>> >>>> oslo.messaging._drivers.impl_rabbit
> >>>> >>>> [-] Failed to consume message from queue: [Errno 110] Connection
> >>>> >>>> timed out
> >>>> >>>> 2015-04-17 16:34:37.163 1959 ERROR
> >>>> >>>> oslo.messaging._drivers.impl_rabbit
> >>>> >>>> [-] Failed to consume message from queue: [Errno 110] Connection
> >>>> >>>> timed out
> >>>> >>>> 2015-04-20 09:40:21.192 9683 ERROR
> >>>> >>>> oslo.messaging._drivers.impl_rabbit
> >>>> >>>> [-] Failed to consume message from queue: (0, 0): (320)
> >>>> >>>> CONNECTION_FORCED -
> >>>> >>>> broker forced connection closure with reason 'shutdown'
> >>>> >>>> 2015-04-20 09:40:22.217 9683 ERROR
> >>>> >>>> oslo.messaging._drivers.impl_rabbit
> >>>> >>>> [-] AMQP server on 192.168.2.34:5672 is unreachable: [Errno 111]
> >>>> >>>> ECONNREFUSED. Trying again in 1 seconds.
> >>>> >>>>
> >>>> >>>>
> >>>> >>>>
> >>>> >>>> grep ERROR nova-api.log
> >>>> >>>>
> >>>> >>>> 2015-04-19 02:23:52.043 4750 ERROR nova.api.openstack
> >>>> >>>> [req-6cdb1bcf-18e3-4366-bc33-8afad6a0be9e None] Caught error:
> >>>> >>>> auth_url was
> >>>> >>>> not provided to the Neutron client
> >>>> >>>> 2015-04-19 04:33:52.051 4745 ERROR nova.api.openstack
> >>>> >>>> [req-a682ff4c-86ee-4d7e-97fa-df0741c4c5ef None] Caught error:
> >>>> >>>> auth_url was
> >>>> >>>> not provided to the Neutron client
> >>>> >>>> 2015-04-19 05:43:52.048 4749 ERROR nova.api.openstack
> >>>> >>>> [req-afec3fef-95a9-4b62-b531-a8c686648dc7 None] Caught error:
> >>>> >>>> auth_url was
> >>>> >>>> not provided to the Neutron client
> >>>> >>>> 2015-04-19 07:53:52.060 4743 ERROR nova.api.openstack
> >>>> >>>> [req-55074cb4-4dd9-442a-9e77-a6db54c41124 None] Caught error:
> >>>> >>>> auth_url was
> >>>> >>>> not provided to the Neutron client
> >>>> >>>> 2015-04-19 11:03:52.072 4733 ERROR nova.api.openstack
> >>>> >>>> [req-e7ec8959-17b7-4c20-b81f-eb4457e8d23e None] Caught error:
> >>>> >>>> auth_url was
> >>>> >>>> not provided to the Neutron client
> >>>> >>>> 2015-04-19 12:13:52.046 4747 ERROR nova.api.openstack
> >>>> >>>> [req-02fcdd32-18da-4e57-90fa-a269ac6446bb None] Caught error:
> >>>> >>>> auth_url was
> >>>> >>>> not provided to the Neutron client
> >>>> >>>> 2015-04-19 15:23:52.078 4741 ERROR nova.api.openstack
> >>>> >>>> [req-581682f3-4677-49ba-b6cf-4e7cd253b47f None] Caught error:
> >>>> >>>> auth_url was
> >>>> >>>> not provided to the Neutron client
> >>>> >>>> 2015-04-19 17:33:52.102 4750 ERROR nova.api.openstack
> >>>> >>>> [req-2f22a04c-5d84-4279-97e7-48ad99d99f17 None] Caught error:
> >>>> >>>> auth_url was
> >>>> >>>> not provided to the Neutron client
> >>>> >>>> 2015-04-19 20:43:52.252 4741 ERROR nova.api.openstack
> >>>> >>>> [req-48dc8185-d826-48eb-a629-e442d7e56181 None] Caught error:
> >>>> >>>> auth_url was
> >>>> >>>> not provided to the Neutron client
> >>>> >>>> 2015-04-19 21:53:52.107 4745 ERROR nova.api.openstack
> >>>> >>>> [req-c3b66cf9-eb12-4ddc-b929-c108cbce8575 None] Caught error:
> >>>> >>>> auth_url was
> >>>> >>>> not provided to the Neutron client
> >>>> >>>> 2015-04-20 01:03:52.125 4737 ERROR nova.api.openstack
> >>>> >>>> [req-31034151-4a94-4b5a-a925-e975912ec93a None] Caught error:
> >>>> >>>> auth_url was
> >>>> >>>> not provided to the Neutron client
> >>>> >>>> 2015-04-20 04:13:52.033 4741 ERROR nova.api.openstack
> >>>> >>>> [req-b521803c-e80c-4e86-a30b-16e5c57da918 None] Caught error:
> >>>> >>>> auth_url was
> >>>> >>>> not provided to the Neutron client
> >>>> >>>> 2015-04-20 05:23:52.047 4736 ERROR nova.api.openstack
> >>>> >>>> [req-95702e17-0960-451a-b5c1-828172b27bc0 None] Caught error:
> >>>> >>>> auth_url was
> >>>> >>>> not provided to the Neutron client
> >>>> >>>> 2015-04-20 06:33:52.013 4740 ERROR nova.api.openstack
> >>>> >>>> [req-711d560d-e9c3-48f3-aabe-28e138ae06e1 None] Caught error:
> >>>> >>>> auth_url was
> >>>> >>>> not provided to the Neutron client
> >>>> >>>> 2015-04-20 07:43:52.178 4747 ERROR nova.api.openstack
> >>>> >>>> [req-d0caca70-b960-4612-b99f-ca42292cb6b4 None] Caught error:
> >>>> >>>> auth_url was
> >>>> >>>> not provided to the Neutron client
> >>>> >>>>
> >>>> >>>>
> >>>> >>>>
> >>>> >>>> 2015-04-20 10:15 GMT+02:00 pauline phaure <phaurep at gmail.com>:
> >>>> >>>>>
> >>>> >>>>> hello guys ,
> >>>> >>>>> When I try to launch an instance, have this error, no valmid
> host
> >>>> >>>>> was
> >>>> >>>>> found. I found these errors in the file logs of nova and
> rabbitmq
> >>>> >>>>> but don't
> >>>> >>>>> know how to proceed:
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>> grep error nova-scheduler.log
> >>>> >>>>> 2015-04-17 15:41:25.119 1976 TRACE
> >>>> >>>>> oslo.messaging._drivers.impl_rabbit
> >>>> >>>>> error: [Errno 110] Connection timed out
> >>>> >>>>> 2015-04-17 16:34:37.163 1959 TRACE
> >>>> >>>>> oslo.messaging._drivers.impl_rabbit
> >>>> >>>>> error: [Errno 110] Connection timed out
> >>>> >>>>>
> >>>> >>>>> grep error nova-api.log
> >>>> >>>>>
> >>>> >>>>> 2015-04-20 01:13:52.005 4748 WARNING
> keystonemiddleware.auth_token
> >>>> >>>>> [-]
> >>>> >>>>> Identity response: {"error": {"message": "Could not find token:
> >>>> >>>>> 868d85f2de3d49878af5b6f79d80e8de", "code": 404, "title": "Not
> >>>> >>>>> Found"}}
> >>>> >>>>> 2015-04-20 02:13:52.022 4741 WARNING
> keystonemiddleware.auth_token
> >>>> >>>>> [-]
> >>>> >>>>> Identity response: {"error": {"message": "Could not find token:
> >>>> >>>>> b309783b561b44ef904b3c4a6ab474bd", "code": 404, "title": "Not
> >>>> >>>>> Found"}}
> >>>> >>>>> 2015-04-20 03:13:52.004 4737 WARNING
> keystonemiddleware.auth_token
> >>>> >>>>> [-]
> >>>> >>>>> Identity response: {"error": {"message": "Could not find token:
> >>>> >>>>> 24eed0bb37b54445bd753359b234a0c4", "code": 404, "title": "Not
> >>>> >>>>> Found"}}
> >>>> >>>>> 2015-04-20 04:13:52.033 4741 ERROR nova.api.openstack
> >>>> >>>>> [req-b521803c-e80c-4e86-a30b-16e5c57da918 None] Caught error:
> >>>> >>>>> auth_url was
> >>>> >>>>> not provided to the Neutron client
> >>>> >>>>> 2015-04-20 04:23:52.044 4742 WARNING
> keystonemiddleware.auth_token
> >>>> >>>>> [-]
> >>>> >>>>> Identity response: {"error": {"message": "Could not find token:
> >>>> >>>>> 6d3e77f2cf75495297c34133bc765bd8", "code": 404, "title": "Not
> >>>> >>>>> Found"}}
> >>>> >>>>> 2015-04-20 05:23:52.047 4736 ERROR nova.api.openstack
> >>>> >>>>> [req-95702e17-0960-451a-b5c1-828172b27bc0 None] Caught error:
> >>>> >>>>> auth_url was
> >>>> >>>>> not provided to the Neutron client
> >>>> >>>>> 2015-04-20 05:33:52.024 4731 WARNING
> keystonemiddleware.auth_token
> >>>> >>>>> [-]
> >>>> >>>>> Identity response: {"error": {"message": "Could not find token:
> >>>> >>>>> ccaee1e396614df5a753a331345e3e24", "code": 404, "title": "Not
> >>>> >>>>> Found"}}
> >>>> >>>>> 2015-04-20 06:33:52.013 4740 ERROR nova.api.openstack
> >>>> >>>>> [req-711d560d-e9c3-48f3-aabe-28e138ae06e1 None] Caught error:
> >>>> >>>>> auth_url was
> >>>> >>>>> not provided to the Neutron client
> >>>> >>>>> 2015-04-20 06:43:51.887 4737 WARNING
> keystonemiddleware.auth_token
> >>>> >>>>> [-]
> >>>> >>>>> Identity response: {"error": {"message": "Could not find token:
> >>>> >>>>> 6ad03759c8f446d09d4babde1aa7f63d", "code": 404, "title": "Not
> >>>> >>>>> Found"}}
> >>>> >>>>> 2015-04-20 07:43:52.178 4747 ERROR nova.api.openstack
> >>>> >>>>> [req-d0caca70-b960-4612-b99f-ca42292cb6b4 None] Caught error:
> >>>> >>>>> auth_url was
> >>>> >>>>> not provided to the Neutron client
> >>>> >>>>> 2015-04-20 07:53:52.037 4742 WARNING
> keystonemiddleware.auth_token
> >>>> >>>>> [-]
> >>>> >>>>> Identity response: {"error": {"message": "Could not find token:
> >>>> >>>>> 0bcaad841985487bbfe4bce038b49c9e", "code": 404, "title": "Not
> >>>> >>>>> Found"}}
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>> grep error /var/log/rabbitmq/rabbit\@localhost.log
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>> AMQP connection <0.865.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.1312.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.499.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.1657.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.9349.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.761.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.2801.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.4447.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.1065.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.712.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.618.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.664.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.9428.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.1222.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.9530.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.9496.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.6746.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.9479.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.9280.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.9295.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.1203.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.1420.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.9513.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.1048.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.741.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.1734.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.1390.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.1400.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>> AMQP connection <0.1430.0> (running), channel 0 - error:
> >>>> >>>>> {amqp_error,connection_forced,
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>
> >>>> >>>
> >>>> >>>
> >>>> >>> _______________________________________________
> >>>> >>> Rdo-list mailing list
> >>>> >>> Rdo-list at redhat.com
> >>>> >>> https://www.redhat.com/mailman/listinfo/rdo-list
> >>>> >>>
> >>>> >>> To unsubscribe: rdo-list-unsubscribe at redhat.com
> >>>> >
> >>>> >
> >>>> >
> >>>> > _______________________________________________
> >>>> > Rdo-list mailing list
> >>>> > Rdo-list at redhat.com
> >>>> > https://www.redhat.com/mailman/listinfo/rdo-list
> >>>> >
> >>>> > To unsubscribe: rdo-list-unsubscribe at redhat.com
> >>>
> >>>
> >>
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20150420/560ec1b4/attachment.html>
More information about the dev
mailing list