intermittent auth failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sloecode |
Triaged
|
High
|
Unassigned |
Bug Description
I have just seen an auth failure with the BZR smart server, and then auth success when retrying the same command without changing anything on the client-side. The client-executed commands were:
lee@ubuntu:
Permission denied (publickey).
bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist.
lee@ubuntu:
farlelr1
lee@ubuntu:
Sloecode Bazaar Smart Server
Pushed up to revision 2.
And the relevant section from the twistd.log file are below. Note the two separate authentications, and the error message for the first failed authentication:
Here's the attempt that failed:
2011-03-23 10:24:00+1300 [twisted.
2011-03-23 10:24:00+1300 [TimeoutProtoco
2011-03-23 10:24:00+1300 [TimeoutProtoco
2011-03-23 10:24:00+1300 [TimeoutProtoco
2011-03-23 10:24:00+1300 [TimeoutProtoco
2011-03-23 10:24:00+1300 [TimeoutProtoco
2011-03-23 10:24:00+1300 [SSHService ssh-userauth on TimeoutProtocol
2011-03-23 10:24:00+1300 [SSHService ssh-userauth on TimeoutProtocol
2011-03-23 10:24:00+1300 [SSHService ssh-userauth on TimeoutProtocol
--- <exception caught here> ---
]
2011-03-23 10:24:00+1300 [SSHService ssh-userauth on TimeoutProtocol
2011-03-23 10:24:00+1300 [SSHService ssh-userauth on TimeoutProtocol
2011-03-23 10:24:00+1300 [TimeoutProtoco
And here's the subsequent attempt that succeeded (just a few seconds later):
2011-03-23 10:24:43+1300 [twisted.
2011-03-23 10:24:43+1300 [TimeoutProtoco
2011-03-23 10:24:43+1300 [TimeoutProtoco
2011-03-23 10:24:43+1300 [TimeoutProtoco
2011-03-23 10:24:43+1300 [TimeoutProtoco
2011-03-23 10:24:43+1300 [TimeoutProtoco
2011-03-23 10:24:43+1300 [SSHService ssh-userauth on TimeoutProtocol
2011-03-23 10:24:43+1300 [SSHService ssh-userauth on TimeoutProtocol
2011-03-23 10:24:43+1300 [SSHService ssh-userauth on TimeoutProtocol
2011-03-23 10:24:43+1300 [SSHService ssh-userauth on TimeoutProtocol
2011-03-23 10:24:43+1300 [SSHService ssh-userauth on TimeoutProtocol
2011-03-23 10:24:43+1300 [SSHService ssh-userauth on TimeoutProtocol
2011-03-23 10:24:43+1300 [SSHService ssh-userauth on TimeoutProtocol
2011-03-23 10:24:43+1300 [SSHService ssh-connection on TimeoutProtocol
2011-03-23 10:24:43+1300 [SSHChannel session (0) on SSHService ssh-connection on TimeoutProtocol
2011-03-23 10:24:43+1300 [SSHChannel session (0) on SSHService ssh-connection on TimeoutProtocol
2011-03-23 10:24:43+1300 [SSHChannel session (0) on SSHService ssh-connection on TimeoutProtocol
2011-03-23 10:24:43+1300 [SSHChannel session (0) on SSHService ssh-connection on TimeoutProtocol
I've now seen this twice. It seems that after a period of inactivity the auth will fail, but once it's been "woken up" it will work consistently. At a first glance it seems to be failing in the XMLRPC code when we attempt to get user auth details from the web app.