← Back to team overview

epoptes team mailing list archive

[Bug 1581581] Re: Connection lost (can't shutdown/interact with client)


> I repeated but for 30 minutes unplugged and as expected, it didn't re-

It should work fine from the epoptes side, I'm using that on a daily

But if you're talking about LTSP clients, then they might crash because
they'll be missing their root filesystem if you unplug the cable for 30
minutes, and this is of course completely unrelated to epoptes.

> Anyway, I'll keep looking for a similar event and update this report

The "incomplete" state means it'll auto-expire in 60 days if you don't
provide any feedback till then.


You received this bug notification because you are a member of Epoptes
Developers, which is subscribed to Epoptes.

  Connection lost (can't shutdown/interact with client)

Status in Epoptes:

Bug description:
  Sometimes it happens that something happens to a client, perhaps the
  ethernet plug got unplugged or something else. It would be nice in
  this situation of a re-boot message were somehow sent, or at least
  this client not be shown in the epoptes window as a connected client
  (with which no interaction seems possible)

  Here's some log data for an example client that I gathered:
  untitled text:260: 2016-05-12 10:43:18-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected:
  untitled text:267: 2016-05-12 10:44:10-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected:
  untitled text:270: 2016-05-12 10:44:40-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected:
  untitled text:287: 2016-05-12 10:57:17-0500 [DelimitedBashReceiver (TLSMemoryBIOProtocol),136,] Connection lost:
  untitled text:287: 2016-05-12 10:57:17-0500 [DelimitedBashReceiver (TLSMemoryBIOProtocol),136,] Connection lost:
  untitled text:367: 2016-05-12 13:19:14-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected:
  untitled text:510: 2016-05-13 10:24:24-0500 [-] Ping timeout:
  untitled text:511: 2016-05-13 10:24:29-0500 [-] Ping timeout:

To manage notifications about this bug go to: