© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Considering this further. If rebooting the server didn't help, but rewriting the name of the ca link did help then it seems that the nature of the failure would be that either ca didn't find out that the socket disconnected along with taking appropriate action, or the client's ip kernel didn't detect the tcp circuit disconnect when the server rebooted.
The code paths in ca that detect a socket disconnect are frequently exercised so if there is failure there its a more rarely occurring type of bug like a race condition.