epoptes team mailing list archive

[David Groos <djgroos@xxxxxxxxx>]

Public bug reported:

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: 192.168.67.77:44231
untitled text:267: 2016-05-12 10:44:10-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.77:39113
untitled text:270: 2016-05-12 10:44:40-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.77:39172
untitled text:287: 2016-05-12 10:57:17-0500 [DelimitedBashReceiver (TLSMemoryBIOProtocol),136,192.168.67.77] Connection lost: 192.168.67.77:39172
untitled text:287: 2016-05-12 10:57:17-0500 [DelimitedBashReceiver (TLSMemoryBIOProtocol),136,192.168.67.77] Connection lost: 192.168.67.77:39172
untitled text:367: 2016-05-12 13:19:14-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.77:39232
untitled text:510: 2016-05-13 10:24:24-0500 [-] Ping timeout: 192.168.67.77:39232
untitled text:511: 2016-05-13 10:24:29-0500 [-] Ping timeout: 192.168.67.77:39113

** Affects: epoptes
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Epoptes
Developers, which is subscribed to Epoptes.
https://bugs.launchpad.net/bugs/1581581

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

Status in Epoptes:
  New

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: 192.168.67.77:44231
  untitled text:267: 2016-05-12 10:44:10-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.77:39113
  untitled text:270: 2016-05-12 10:44:40-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.77:39172
  untitled text:287: 2016-05-12 10:57:17-0500 [DelimitedBashReceiver (TLSMemoryBIOProtocol),136,192.168.67.77] Connection lost: 192.168.67.77:39172
  untitled text:287: 2016-05-12 10:57:17-0500 [DelimitedBashReceiver (TLSMemoryBIOProtocol),136,192.168.67.77] Connection lost: 192.168.67.77:39172
  untitled text:367: 2016-05-12 13:19:14-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.77:39232
  untitled text:510: 2016-05-13 10:24:24-0500 [-] Ping timeout: 192.168.67.77:39232
  untitled text:511: 2016-05-13 10:24:29-0500 [-] Ping timeout: 192.168.67.77:39113

To manage notifications about this bug go to:
https://bugs.launchpad.net/epoptes/+bug/1581581/+subscriptions