login failed with 502 Bad Gateway: Registered endpoint failed to handle the request

[ikizoo4]

it was working before lab shutdown, and bring back up all CF VMs and can not login.
there is no spcecial message in cloud_controller_ng.

can someone advice me where to start to look at to fix this issue?

cf trace :

[1;38mREQUEST: [0m [2015-01-15T19:26:15-08:00]
GET /login HTTP/1.1
Host: uaa.mb-lab.huron.uno
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.3.2-217929b / darwin



[1;38mRESPONSE: [0m [2015-01-15T19:26:31-08:00]
HTTP/1.1 502 Bad Gateway
Content-Length: 67
Content-Type: text/plain; charset=utf-8
Date: Fri, 16 Jan 2015 03:20:55 GMT
X-Cf-Routererror: endpoint_failure

502 Bad Gateway: Registered endpoint failed to handle the request.

FAILED
Server error, status code: 502, error code: , message:

[James Bayer]

your first step should be to see if the UAA process is running on the VM running the UAA.

"bosh vms" to see the status of the UAA vm.

if that's ok, then "bosh ssh" to the VM and use monit to check the status of the UAA, check it locally with curl, look at the logs, etc.

--
You received this message because you are subscribed to the Google Groups "Cloud Foundry Developers" group.
To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/f17e886b-9818-4f48-a65f-b8e0e19d99c6%40cloudfoundry.org.

To unsubscribe from this group and stop receiving emails from it, send an email to vcap-dev+u...@cloudfoundry.org.

--

Thank you,

James Bayer

[ikizoo4]

thanks James,
actually check the monit uaa and it was running status, but there is no listenning on 8080.
after restart the uaa, the issue is fixed,

BK