WebSocketConnectionClosedException
Connection to remote host was lost.
#38
Labels
3rd party errors
Errors observed from 3rd party code such as websocket or SSL errors
_Migrated from internal repo.
Complete stack trace and logs (sensitive) https://github.com/AI-Safety-Institute/aisi-inspect-tools/issues/142
Original date: 23 Oct 2024
Originally raised by @willpayne23
Another instance of this, with the improved logging below (26 Oct 2024)
With timestamps (from py log file). Why did nearly an hour elapse between starting the command and the failure?
Kubernetes cluster events. Note the "node not ready".
Another instance of this (02 Nov 2024)
cluster events:
06 November 2024
Note the 50 minutes between starting (or technically queueing) the command the when the actual error was raised.
It looks like the default container was started at 01:32:22, then the node was marked as not ready at 01:33:37 (by which point some write_files had already taken place). Note that the exec started at 01:32:39 errored at 01:39:47.
06 Nov 2024
The text was updated successfully, but these errors were encountered: