epoptes team mailing list archive

[David Groos <djgroos@xxxxxxxxx>]

I've been experimenting a bit. I unplugged the ethernet cable for a
minute, the client disappeared from the epoptes UI, re-plugged, and it
re-appeared and was able to be managed by epoptes again. That was
amazing! I repeated but for 30 minutes unplugged and as expected, it
didn't re-connect. I tested both with a user logged in and also without
user logged in, same results. This is a great feature.

Today there was an issue and I thought at first that it was a similar
issue but, unless I did something different, it seemed to resolve
itself. It appears that the user with this problem had a corrupted home
folder. Here's a piece of the epoptes log file that includes this event
(Including here in case there might be a connection). The client with
the problem was 192.168.67.55. I ended rm -r the users home folder and
the user had no problems after that. Anyway, I'll keep looking for a
similar event and update this report then.

Thanks,
David

2016-05-17 11:48:35-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.26:60062
2016-05-17 11:48:44-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.55:48160
2016-05-17 11:48:45-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.187:47846
2016-05-17 11:48:52-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.116:32900
2016-05-17 11:57:03-0500 [-] Ping timeout: 192.168.67.55:47533
2016-05-17 11:57:04-0500 [-] Ping timeout: 192.168.67.55:48160
2016-05-17 11:57:22-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.178:54902
2016-05-17 11:58:19-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.55:43827
2016-05-17 11:58:37-0500 [DelimitedBashReceiver (TLSMemoryBIOProtocol),63,192.168.67.55] Connection lost: 192.168.67.55:47533
2016-05-17 11:58:39-0500 [DelimitedBashReceiver (TLSMemoryBIOProtocol),113,192.168.67.55] Connection lost: 192.168.67.55:48160
2016-05-17 11:58:57-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.55:43883
2016-05-17 11:59:45-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.43:34766

-- 
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:
  Incomplete

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