© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
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.
2016-05-17 11:48:44-0500 [twisted.
2016-05-17 11:48:45-0500 [twisted.
2016-05-17 11:48:52-0500 [twisted.
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.
2016-05-17 11:58:19-0500 [twisted.
2016-05-17 11:58:37-0500 [DelimitedBashR
2016-05-17 11:58:39-0500 [DelimitedBashR
2016-05-17 11:58:57-0500 [twisted.
2016-05-17 11:59:45-0500 [twisted.