[Fiware-lab-federation-nodes] Unauthorized (HTTP 401) problem

[Ariel Otilibili Anieli]

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.
>