← Back to team overview

epoptes team mailing list archive

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

 

I tried something new yesterday when problem happened again. This is
what I did:

-- With Epoptes tool I shut down all of the computers that were showing in the 'detected clients' window.
-- Computer "9A" wouldn't shut down, remaining in the detected clients window.
-- I went over to the client to check it out and saw that the small green power light on the computer was on, however, even though the display should therefore have been on, it was dark.
-- I checked the logs for previous few days and nothing unusual about that client, just 3 very ordinary entries.
-- I had tail command on the epoptes log as I powered down the client (client is 192.168.67.175)...

:~$ tail -f /var/log/epoptes.log
2016-06-03 17:36:24-0500 [DelimitedBashReceiver (TLSMemoryBIOProtocol),359,192.168.67.231] Connection lost: 192.168.67.231:33679
2016-06-03 17:36:24-0500 [DelimitedBashReceiver (TLSMemoryBIOProtocol),360,192.168.67.153] Connection lost: 192.168.67.153:53229
2016-06-03 17:36:24-0500 [DelimitedBashReceiver (TLSMemoryBIOProtocol),361,192.168.67.239] Connection lost: 192.168.67.239:41613
2016-06-03 17:36:24-0500 [DelimitedBashReceiver (TLSMemoryBIOProtocol),362,192.168.67.106] Connection lost: 192.168.67.106:42457
2016-06-03 17:36:24-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.195:42284
2016-06-03 17:36:24-0500 [DelimitedBashReceiver (TLSMemoryBIOProtocol),363,192.168.67.195] Connection lost: 192.168.67.195:42284
2016-06-03 17:36:24-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.115:44655
2016-06-03 17:36:25-0500 [twisted.protocols.tls.TLSMemoryBIOFactory] Connected: 192.168.67.102:55488
2016-06-03 17:36:25-0500 [DelimitedBashReceiver (TLSMemoryBIOProtocol),365,192.168.67.102] Connection lost: 192.168.67.102:55488
2016-06-03 17:36:25-0500 [DelimitedBashReceiver (TLSMemoryBIOProtocol),364,192.168.67.115] Connection lost: 192.168.67.115:44655
2016-06-03 17:44:04-0500 [-] Ping timeout: 192.168.67.175:56049

... as the client disappeared from the detected clients window.

This is the first time I've seen anything out of the ordinary in the
epoptes logs. Not sure if this is relevant. Anywhere else I should
check? I do have other epoptes log results from a week ago but as I
mentioned, it doesn't look like there's anything out of the ordinary. It
probably won't happen again as school's almost over for the year. Let me
know any other place to check, I've got times to check in other logs.
Thanks!

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


References