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

[David Groos]

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

[Alkis Georgopoulos (alkisg)]

Hi David,

which epoptes and epoptes-client versions are you using?

[David Groos (djgroos)]

Hi Alkis!

epoptes --version
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
  warnings.warn(str(e), _gtk.Warning)
Epoptes 0.5.10

epoptes-client --version
0.5.10

[Alkis Georgopoulos (alkisg)]

OK so this is a recent epoptes, which is supposed to support client reconnection etc.
I.e. try this:
pull the network cable of a client
wait for 1 minute
verify that the client automatically disappears from the epoptes UI
put back the network cable
wait for a few seconds
verify that the client automatically reappears in the epoptes UI

I.e. what you're requesting is already implemented.

So, if I understood the issue correctly, what you experienced is an unknown bug.
Is there any way to reproduce it?

[David Groos (djgroos)]

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

[Alkis Georgopoulos (alkisg)]

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

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

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

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

Cheers!

[David Groos (djgroos)]

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!

[Launchpad Janitor (janitor)]

[Expired for Epoptes because there has been no activity for 60 days.]