Comment 3 for bug 1241395

Revision history for this message
Tom Fifield (fifieldt) wrote :

example from debug log that should be carried through to the dashboard

[Fri Apr 11 04:55:37.760404 2014] [:error] [pid 22351] HTTP/1.1 400 Bad Request
[Fri Apr 11 04:55:37.760408 2014] [:error] [pid 22351] date: Fri, 11 Apr 2014 04:55:37 GMT
[Fri Apr 11 04:55:37.760410 2014] [:error] [pid 22351] content-length: 301
[Fri Apr 11 04:55:37.760413 2014] [:error] [pid 22351] content-type: application/json; charset=UTF-8
[Fri Apr 11 04:55:37.760416 2014] [:error] [pid 22351]
[Fri Apr 11 04:55:37.760419 2014] [:error] [pid 22351] {"explanation": "Environment not in valid format: The environment is not a valid YAML mapping data type.", "code": 400, "error": {"message": "Environment not in valid format: The environment is not a valid YAML mapping data type.", "traceback": null, "type": "HTTPBadRequest"}, "title": "Bad Request"}
[Fri Apr 11 04:55:37.760422 2014] [:error] [pid 22351]
[Fri Apr 11 04:55:37.761751 2014] [:error] [pid 22351] Recoverable error: ERROR: Environment not in valid format: The environment is not a valid YAML mapping data type.