Problem with Janus login and no error in log and no error returned to client

[brentgriffin]

Related to testing of #465

First, it is important to understand that this is the new Janus that uses Cassandra and one of the Cassandra nodes did not start up correctly. Even so, I would expect Janus to better handle the failure.

Console from postman:

POST http://acf777a17a3c74b08943b75a1d6cd326-1400381294.us-west-2.elb.amazonaws.com:8081/login
  Error: socket hang up
  Request Headers
  Authorization: Basic amFudXNhZG1pbjpLczlZQTRCeSR6Njk=
  User-Agent: PostmanRuntime/7.26.10
  Accept: */*
  Cache-Control: no-cache
  Postman-Token: 90550187-cf5b-4aec-a4fc-35c81409f699
  Host: acf777a17a3c74b08943b75a1d6cd326-1400381294.us-west-2.elb.amazonaws.com:8081
  Accept-Encoding: gzip, deflate, br
  Connection: keep-alive

It is understandable if Cassandra is not healthy that the login would fail; however, I would expect two things to happen in this case:

• Return error status code to client (500 or something)
• Log error message in log file (this would help diagnose the problem)