Some online troubleshooting revealed the problem:
kadkarol had an invalid DNS server declared in her dhcpd.conf, so a `getent
hosts $SERVER` call that epoptes-client does took 20 seconds, and epoptes
thought the client timed out and closed the connection.
While it was a local configuration problem, epoptes-client should still be
smart enough not to time out.
It will be fixed in the next version.
** Changed in: epoptes
Importance: Undecided => Low
** Changed in: epoptes
Status: Incomplete => Triaged
** Changed in: epoptes
Assignee: (unassigned) => Alkis Georgopoulos (alkisg)
--
You received this bug notification because you are a member of Epoptes
Developers, which is the registrant for Epoptes.
https://bugs.launchpad.net/bugs/949055
Title:
can't shutdown ltsp client computers if no one is logged in on them
Status in Epoptes:
Triaged
Bug description:
After update to Epoptes v 4.4 I can't shutdown ltsp client computers
if no one is logged in on them. In previous version of the software
these comupters were visible in Epoptes as a green icon with an ltsp
client name label under it, thanks to that I was able to shut them
down remotely. Since the computers are no longer visible I'm unable to
do so. My system is Edubuntu 11.4.
To manage notifications about this bug go to:
https://bugs.launchpad.net/epoptes/+bug/949055/+subscriptions
--
Mailing list: https://launchpad.net/~epoptes
Post to : [email protected]
Unsubscribe : https://launchpad.net/~epoptes
More help : https://help.launchpad.net/ListHelp
