No thumbnails of fat client

Bug #1313713 reported by kadkarol

This bug report was converted into a question: question #248189: No thumbnails of fat client.

6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Epoptes
Invalid
Undecided
Unassigned

Bug Description

My system lubuntu 14.04, Epoptes 0.5.7, Environment ltsp-pnp
I not see thumbnail in epoptes.

Maybe the reason is that it can not transfer certificate
in temrinal:
zsceglow@zsceglow-ltsp:~$ sudo epoptes-client -c
[sudo] password for zsceglow:
connect: Connection timed out
connect:errno=110
epoptes-client ERROR: Failed to fetch certificate from server:789

My network config eth0 -internet eth1 -local
auto eth0
iface eth0 inet static
address 192.168.1.10
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameservers 192.168.1.1

auto eth1
iface eth1 inet static
address 192.168.67.1
netmask 255.255.255.0

Tags: thumbnail
Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

On the server, run:
$ sudo md5sum /etc/epoptes/*
$ sudo netstat -nap|grep 789

On the fat client, run:
$ md5sum /etc/epoptes/*
$ getent hosts server

Paste the output of all those commands here.

Changed in epoptes:
status: New → Incomplete
Revision history for this message
kadkarol (karol-sienkowski) wrote :

Hi,
I'm sorry, that only today I write. In Poland, was a long weekend

On the server:

sudo md5sum /etc/epoptes/*
d41d8cd98f00b204e9800998ecf8427e /etc/epoptes/server.crt
850b091be9f45456a374fca7efcc1064 /etc/epoptes/server.key

sudo netstat -nap|grep 789
tcp 0 0 0.0.0.0:789 0.0.0.0:* LISTEN 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.181:37545 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.191:38040 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.174:36895 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.158:59705 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.37:52305 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.133:43498 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.47:54612 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.173:34377 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.97:53460 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.189:33774 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.172:43709 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.106:51528 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.105:52340 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.171:45554 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.113:41448 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.153:44863 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.179:59996 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.114:40021 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.59:43951 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.178:50000 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.170:47790 ESTABLISHED 3385/python
tcp 0 0 192.168.67.1:789 192.168.67.176:48875 ESTABLISHED 3385/python

On fat client:

md5sum /etc/epoptes/*
d41d8cd98f00b204e9800998ecf8427e /etc/epoptes/server.crt

getent hosts server
192.168.67.1 server

Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

I'm converting the bug report into a question, as it's not a bug in the application but a user error.

The problem is that the /etc/epoptes/server.crt file is empty, of size zero.
That might have happened if you ran `sudo epoptes-client -c localhost` on the server instead of some chroot.
You don't need to run `epoptes-client -c` at all, in ltsp-pnp.

EITHER see: http://www.epoptes.org/installation#TOC-Manually-updating-the-OpenSSL-certificate for how to create a new certificate.
OR run: sudo apt-get purge epoptes; sudo apt-get install epoptes
(don't do both of them)

Then run `sudo ltsp-update-image -c /`, then reboot the clients.

Changed in epoptes:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.