Thin client not registering with epoptes

Asked by David Hopkins

I have epoptes and epoptes-client installed on an Edubuntu LTSP 12.04 server (default install includes these). I have also installed epoptes-client in the chroot which is not installed by default. The version of epoptes is 0.5.5.0ubuntu0.1. I rebuilt the image (ltsp-update-kernels ; ltsp-update-sshkeys ; ltsp-update-image --arch i386)

When I boot the clients, I see all the thin clients but one prior to anyone logging in at a client. (e.g. ltsp21, ltsp50 appear but this particular client ltsp20 does not) All are booting from the same server (so same image). I don't have any client-specific settings in lts.conf (below). ipv4 forwarding is enabled. I check that a process (socat) started and connected to my ltsp server via ps ax | grep epoptes and the command is the same on all clients. If I then log in at the client (with any valid account), I see the client in the epoptes GUI and can manage that user.

I have no idea why just one client machine doesn't register properly.

Sincerely,
Dave Hopkins

lts.conf file:

[default]
  LDM_THEME=edubuntu
  SCREEN_02=shell
  SCREEN_07=ldm
  LANG=en_US.UTF-8
  LANGUAGE=en_US.UTF-8
  LDM_LANGUAGE=en_US.UTF-8
  LDM_SESSION="gnome-session --session=gnome-fallback"
  LOCAL_APPS=True
  LOCAL_APPS_MENU=True
  LOCAL_APPS_MENU_ITEMS=gcompris,tuxmath
  SOUND=True
  SEARCH_DOMAIN = ncs.k12.de.us
  DNS_SERVER = 10.179.2.25

Question information

Language:
English Edit question
Status:
Expired
For:
Epoptes Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Fotis Tsamis (ftsamis) said :
#1

Hello David,

Please start epoptes from a terminal before booting any clients, then boot ltsp20, login and paste here all the output you get in the terminal (there is some debugging information printed by default). Also please paste your /var/log/epoptes.log.

Thank you,
Fotis

Revision history for this message
David Hopkins (dahopkins429) said :
#2

Fotis,

This is probably a silly question, but how do I start from a terminal? I'm only aware of using the init scripts with service epoptes start/stop/restart. Same for the epoptes-client. Or are you referring to the epoptes GUI? I"ve pasted the output from the epoptes.log below, the output from /usr/bin/epoptes (GUI) below that.

I stopped/started epoptes (service epoptes stop ; service epoptes start)

2013-09-16 07:12:33-0400 [-] Log opened.
2013-09-16 07:12:33-0400 [-] twistd 11.1.0 (/usr/bin/python 2.7.3) starting up.
2013-09-16 07:12:33-0400 [-] reactor class: twisted.internet.pollreactor.PollReactor.
2013-09-16 07:12:33-0400 [-] DelimitedBashReceiverFactory (TLS) starting on 789
2013-09-16 07:12:33-0400 [-] Starting factory <epoptes.daemon.bashplex.DelimitedBashReceiverFactory instance at 0x192fb48>
2013-09-16 07:12:33-0400 [-] GUIFactory starting on '/var/run/epoptes/epoptes.socket'
2013-09-16 07:12:33-0400 [-] Starting factory <epoptes.daemon.guiplex.GUIFactory instance at 0x192fc68>

I then started epoptes in a GUI. After the GUI was up, I booted ltsp20, and logged in. I didn't get a notification until after logging in. I next booted a different thin client and booted it, and then logged in with a different account. Both account logins are registered, but only the second machine. Very strange.

dhopkins@ncslts7:~$ epoptes
Got clients: None
New connection from 127.0.0.1:55500
---
**addClient's been called for 127.0.0.1:55500
  Continuing inside addClient...
* This client is a new one, creating an instance
* I am a user client, will add dcas028 in my list
New connection from 192.168.0.25:34055
---
**addClient's been called for 192.168.0.25:34055
  Continuing inside addClient...
* This client is a new one, creating an instance
* I am a root client
New connection from 127.0.0.1:55643
---
**addClient's been called for 127.0.0.1:55643
  Continuing inside addClient...
* This is an existing client
* I am a user client, will add dcas029 in my list

Revision history for this message
Alkis Georgopoulos (alkisg) said :
#3

> When I boot the clients, I see all the thin clients but one prior to anyone logging in at a client.
> (e.g. ltsp21, ltsp50 appear but this particular client ltsp20 does not)

Hi,

put these under [Default] in lts.conf:
SCREEN_02=shell
SCREEN_07=ldm

On the server, open gnome-terminal, and run: epoptes
Boot ltsp20 (the client with the problem). Watch the epoptes GUI while the client boots, to see if you get any connected / immediately disconnected notifications.

When ltsp20 reaches the login screen, *don't* login.
Press Alt+Ctrl+F2 on ltsp20 to switch to a console. There, run: epoptes-client
...and then check if ltsp20 is now shown in the epoptes GUI.

Finally, attach here the output of both commands that you issued, `epoptes` on the server, and `epoptes-client` on the client console.

Revision history for this message
Launchpad Janitor (janitor) said :
#4

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.