until now yes. But I restarted again the services and I get : [Errno 111] Connection refused) We need the service up in order to migrate the VMs. ould you please help us? Cristian ----- Messaggio originale ----- Da: "Álvaro Alonso" <aalonsog at dit.upm.es> A: spyros at intelligence.tuc.gr Cc: "Cristian Cristelotti" <cristian.cristelotti.coll at trentinonetwork.it>, "FERNANDO LOPEZ AGUILAR" <fernando.lopezaguilar at telefonica.com>, "Pietropaolo Alfonso" <alfonso.pietropaolo at eng.it>, fiware-lab-federation-nodes at lists.fiware.org, support at com4innov.com, "Ariel Otilibili Anieli" <ariel.otilibili-anieli at com4innov.com>, "Paolo Bertolini" <paolo.bertolini at trentinonetwork.it>, "support-xifi" <support-xifi at trentinonetwork.it> Inviato: Giovedì, 25 febbraio 2016 14:59:01 Oggetto: Re: [Fiware-lab-federation-nodes] Unauthorized (HTTP 401) problem Hi all, we didn’t change anything there. Are those responses always 401? Or only sometimes? BR -- Álvaro El 25 Feb 2016, a las 10:52, Spyros Argyropoulos < spyros at intelligence.tuc.gr > escribió: Same problem in Crete. We need to know if there was any change in the way openstack services take authorization. Thank you, Spyros. Spyros Argyropoulos, Computer & Informatics Eng. Intelligent Systems Laboratory School of Electronic and Computer Engineering Technical University of Crete University Campus - Kounoupidiana 73100 Chania, Crete GREECE Phone: +3028210 37342 Fax: +3028210 37542 On 25/2/2016 11:37 πμ, Cristian Cristelotti wrote: Hi All, since yesterday morning Trento is getting "ERROR (Unauthorized): Unauthorized (HTTP 401)". We were supposed to start migrating VMs to the new node and this issue is blocking us. We informed Alvaro as responsible of Keystone to check and fix the issue. Also we received some complains from user that can't manage the VMs from cloud-portal. Can you please support us? Thank you Cristian ----- Messaggio originale ----- Da: "Ariel Otilibili Anieli" < ariel.otilibili-anieli at com4innov.com > A: "Cristian Cristelotti" < cristian.cristelotti.coll at trentinonetwork.it >, spyros at intelligence.tuc.gr , aalonsog at dit.upm.es Cc: fiware-lab-federation-nodes at lists.fiware.org , support at com4innov.com Inviato: Mercoledì, 24 febbraio 2016 17:52:10 Oggetto: Re: [Fiware-lab-federation-nodes] Unauthorized (HTTP 401) problem Hello Álvaro, All nodes (but Zurich and Madrid) are down. On this matter, see the mail log, Spýros (from Crete), Christian (from Trento) and I (Sophia Antipolis) have been talking over. At our side, all services are up; our check is sane. May you help to work this around? Regards, Ariel Otilibili Anieli 00 33 (0)6 28 11 87 30 Le 24/02/2016 17:28, Cristian Cristelotti a écrit : Trento still facing the problem ----- Messaggio originale ----- Da: "Ariel Otilibili Anieli" < ariel.otilibili-anieli at com4innov.com > A: spyros at intelligence.tuc.gr , "Cristian Cristelotti" < cristian.cristelotti.coll at trentinonetwork.it > Cc: fiware-lab-federation-nodes at lists.fiware.org , support at com4innov.com Inviato: Mercoledì, 24 febbraio 2016 16:45:23 Oggetto: Re: [Fiware-lab-federation-nodes] Unauthorized (HTTP 401) problem At our side, Spýro; it works: root at node-1:~# nova list --all-tenants +--------------------------------------+-------------------------+--------+------------+-------------+-------------------------------------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+-------------------------+--------+------------+-------------+-------------------------------------------------+ | 7c412711-679d-475f-affb-2fc04234d1f7 | Centos7x64_EGM_IoTAgent | ACTIVE | - | Running | node-int-net-01=192.168.111.175, 193.48.247.247 | | 2dff52e5-5cfa-4e57-ba3b-903ac4974615 | Context Broker C4I | ACTIVE | - | Running | node-int-net-01=192.168.111.229, 193.48.247.240 | | 1150d022-ce96-42a4-b097-0bbc1b38bcf4 | EGM_EsperTest | ACTIVE | - | Running | node-int-net-01=192.168.111.116 | | fc18456f-b584-4113-b23d-f7a5974b4f1e | Git Fiesta | ACTIVE | - | Running | node-int-net-01=192.168.111.14, 193.48.247.239 | | 3ab26e72-5507-476f-b2bc-6dd46418d12a | IOT Agent C4I | ACTIVE | - | Running | node-int-net-01=192.168.111.239, 193.48.247.231 | | ade1b2f1-ed4e-4597-9166-6576154470ae | OCB_OneM2M | ACTIVE | - | Running | node-int-net-01=192.168.111.150 | | aedaa83e-ed00-49c6-933d-7c33a502b869 | OrionCB_EGM_Instance | ACTIVE | - | Running | node-int-net-01=192.168.111.180, 193.48.247.246 | | f96099b1-5f58-4dbb-828f-2eb7869092ab | Ubuntu14.04GitLab | ACTIVE | - | Running | node-int-net-01=192.168.111.16, 193.48.247.201 | | 7ad0c331-513c-4833-b731-fe108425c9fa | cloud1 | ACTIVE | - | Running | node-int-net-01=192.168.111.237, 193.48.247.221 | | 44b64155-d82e-4770-a99c-626d739a7b3d | cygnus_Mongo | ACTIVE | - | Running | node-int-net-01=192.168.111.128, 193.48.247.223 | | 78542f35-b685-4a1e-89df-d5feb1d0c958 | iot | ACTIVE | - | Running | node-int-net-01=192.168.111.130 | | 9550f433-7768-4bab-ab86-5370f52e9f93 | pol1 | ACTIVE | - | Running | node-int-net-01=192.168.111.6, 193.48.247.208 | | dd9c35c3-5c32-4486-af04-20f912b0a0d9 | pol2 | ACTIVE | - | Running | node-int-net-01=192.168.111.7, 193.48.247.209 | | 30a3ff06-c088-4188-8ee7-4aa95b86431c | sofm2 | ACTIVE | - | Running | node-int-net-01=192.168.111.152 | | 53974bba-cc28-4a81-9825-5b8962a63dad | sofp | ACTIVE | - | Running | node-int-net-01=192.168.111.154 | | 7cfb54bb-822a-4d11-ab22-99ae5a674fa8 | sofp2 | ACTIVE | - | Running | node-int-net-01=192.168.111.156 | | 42b6d86e-99f7-44e6-a6d7-b5f62c600d4a | sofp51 | ACTIVE | - | Running | node-int-net-01=192.168.111.168 | | 04aee247-5d08-4c89-9078-ce73c23ab2fa | sofp52 | ACTIVE | - | Running | node-int-net-01=192.168.111.170 | | 4e639089-076d-413f-af50-f92cf101a215 | sofsav | ACTIVE | - | Running | node-int-net-01=192.168.111.135 | | 0ce39f07-d3a2-4fe9-9f87-04a5e5c406ab | sophia2ptres | ACTIVE | - | Running | node-int-net-01=192.168.111.171 | | d176eb89-f95a-41b5-823e-a6b6835deb54 | sophia2ptres2 | ACTIVE | - | Running | node-int-net-01=192.168.111.172 | | 9d1ef14a-5d83-4301-9cf5-031d6e0c2094 | sophia2xet | ACTIVE | - | Running | node-int-net-01=192.168.111.158 | | 25cf7a4c-9a06-4eb5-a824-bfd3053a5ec9 | sophia2xet2 | ACTIVE | - | Running | node-int-net-01=192.168.111.164 | | 9ba8d34b-daa4-438a-bb3e-ba4f85d2bbb4 | test1 | ACTIVE | - | Running | node-int-net-01=192.168.111.169 | | 872fe670-a1e0-4147-87d6-74a0cdc0b6c0 | test2 | ACTIVE | - | Running | node-int-net-01=192.168.111.173 | | 112f82d2-40f3-4dca-b257-a41db0ed9bea | test3 | ACTIVE | - | Running | node-int-net-01=192.168.111.174 | | 602843dc-311f-45ff-9fab-9803f3c122cf | test3 | ACTIVE | - | Running | ext=192.168.0.2, 193.48.247.206 | | 61448d5c-4171-4817-8628-9c9a7ed16d45 | test4 | ACTIVE | - | Running | node-int-net-01=192.168.111.176 | | c1b06377-6f86-4039-aa2a-1bb0eed53350 | test5 | ACTIVE | - | Running | node-int-net-01=192.168.111.177 | | 01315eeb-c829-4019-97c0-b3511d0cf3aa | test6 | ACTIVE | - | Running | node-int-net-01=192.168.111.178 | +--------------------------------------+-------------------------+--------+------------+-------------+-------------------------------------------------+ root at node-1:~# nova list On Nagios, all service are up; and all nodes are down, but Zurich and Spain. I can't square this circle... Ariel Otilibili Anieli 00 33 (0)6 28 11 87 30 Le 24/02/2016 16:06, Spyros Argyropoulos a écrit : The logs were from /var/log/neutron/server.log (for juno) Also notice we have problem with CLIs, e.g. # nova list ERROR (Unauthorized): Unauthorized (HTTP 401) (Request-ID: req-1de02ff2-d91c-4891-a7fd-7e586e1f3046) Spyros. ___________________________________________ Spyros Argyropoulos, Computer & Informatics Eng. Intelligent Systems Laboratory Department of Electronic and Computer Engineering Technical University of Crete University Campus - Kounoupidiana 73100 Chania, Crete GREECE Phone: +3028210 37342 Fax: +3028210 37542 On 2/24/2016 4:25 PM, Ariel Otilibili Anieli wrote: Hi Spýro, So do we: Keystone up, but others services down (as you). I went through this log: root at node-1:~# tail -f /var/log/keystone/keystone-all.log 2016-02-24 12:38:59.243 5297 INFO eventlet.wsgi.server [-] 192.168.252.4 - - [24/Feb/2016 12:38:59] "POST /v2.0/tokens HTTP/1.1" 200 3927 0.134585 2016-02-24 12:48:59.370 5297 INFO eventlet.wsgi.server [-] 192.168.252.4 - - [24/Feb/2016 12:48:59] "POST /v2.0/tokens HTTP/1.1" 200 3927 0.155716 2016-02-24 12:58:59.445 5297 INFO eventlet.wsgi.server [-] 192.168.252.4 - - [24/Feb/2016 12:58:59] "POST /v2.0/tokens HTTP/1.1" 200 3927 0.161786 2016-02-24 13:08:59.433 5297 INFO eventlet.wsgi.server [-] 192.168.252.4 - - [24/Feb/2016 13:08:59] "POST /v2.0/tokens HTTP/1.1" 200 3927 0.144382 2016-02-24 13:18:59.564 5297 INFO eventlet.wsgi.server [-] 192.168.252.4 - - [24/Feb/2016 13:18:59] "POST /v2.0/tokens HTTP/1.1" 200 3927 0.155842 2016-02-24 13:28:59.658 5297 INFO eventlet.wsgi.server [-] 192.168.252.4 - - [24/Feb/2016 13:28:59] "POST /v2.0/tokens HTTP/1.1" 200 3927 0.160769 2016-02-24 13:38:59.741 5297 INFO eventlet.wsgi.server [-] 192.168.252.4 - - [24/Feb/2016 13:38:59] "POST /v2.0/tokens HTTP/1.1" 200 3927 0.159837 2016-02-24 13:48:59.860 5297 INFO eventlet.wsgi.server [-] 192.168.252.4 - - [24/Feb/2016 13:48:59] "POST /v2.0/tokens HTTP/1.1" 200 3927 0.162100 2016-02-24 13:58:59.892 5297 INFO eventlet.wsgi.server [-] 192.168.252.4 - - [24/Feb/2016 13:58:59] "POST /v2.0/tokens HTTP/1.1" 200 3927 0.154368 2016-02-24 14:09:00.004 5297 INFO eventlet.wsgi.server [-] 192.168.252.4 - - [24/Feb/2016 14:09:00] "POST /v2.0/tokens HTTP/1.1" 200 3927 0.162309 And that one: root at node-1:~# tail -f /var/log/keystone/keystone-manage.log 2015-05-12 17:04:41.184 49441 INFO migrate.versioning.api [-] 39 -> 40... 2015-05-12 17:04:41.221 49441 INFO migrate.versioning.api [-] done 2015-05-12 17:04:41.222 49441 INFO migrate.versioning.api [-] 40 -> 41... 2015-05-12 17:04:41.236 49441 INFO migrate.versioning.api [-] done 2015-05-12 17:04:41.237 49441 INFO migrate.versioning.api [-] 41 -> 42... 2015-05-12 17:04:41.259 49441 INFO migrate.versioning.api [-] done 2015-05-12 17:04:41.259 49441 INFO migrate.versioning.api [-] 42 -> 43... 2015-05-12 17:04:41.267 49441 INFO migrate.versioning.api [-] done 2015-05-12 17:04:41.267 49441 INFO migrate.versioning.api [-] 43 -> 44... 2015-05-12 17:04:41.289 49441 INFO migrate.versioning.api [-] done But, still, couldn't see when you got your output. Where had you looked into? Regards, Ariel Otilibili Anieli 00 33 (0)6 28 11 87 30 Le 24/02/2016 14:47, Cristian Cristelotti a écrit : Same for Trento!!! Cristian ----- Messaggio originale ----- Da: "Spyros Argyropoulos" < spyros at intelligence.tuc.gr > A: fiware-lab-federation-nodes at lists.fiware.org Inviato: Mercoledì, 24 febbraio 2016 14:36:47 Oggetto: [Fiware-lab-federation-nodes] Unauthorized (HTTP 401) problem Hi all, Today sanity tests did not work for the Region of Crete because we got a 'Unauthorized (HTTP 401)' message for all of them. It seems we have lost connection with central keystone as we get messages in our logs like the following: 2016-02-24 13:32:39.423 6873 WARNING keystonemiddleware.auth_token [-] Retrying on HTTP connection exception: Unable to establish connection to http://cloud.lab.fiware.org:4731/ 2016-02-24 13:32:40.156 6873 WARNING keystonemiddleware.auth_token [-] Retrying on HTTP connection exception: Unable to establish connection to http://cloud.lab.fiware.org:4731/ 2016-02-24 13:32:41.388 6873 WARNING keystonemiddleware.auth_token [-] Retrying on HTTP connection exception: Unable to establish connection to http://cloud.lab.fiware.org:4731/ 2016-02-24 13:32:43.618 6873 ERROR keystonemiddleware.auth_token [-] HTTP connection exception: Unable to establish connection to http://cloud.lab.fiware.org:4731/ As I can see Trento has the same problem. Any ideas... Thank you, Spyros. -- Cristian Cristelotti Collaboratore di Trentino Network Srl
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy