IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 15 October 2017   (all times are UTC)

01:38adrianor1 has joined IRC (adrianor1!~adrianorg@177.204.158.208.dynamic.adsl.gvt.net.br)
01:41adrianorg has left IRC (adrianorg!~adrianorg@177.18.50.235, Ping timeout: 240 seconds)
01:56vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
02:05Guest34506 has left IRC (Guest34506!bennabiyma@gateway/shell/matrix.org/x-hbmfkpawbcreetrv, Changing host)
02:05Guest34506 has joined IRC (Guest34506!bennabiyma@unaffiliated/bennabiy)
02:05Guest34506 has joined IRC (Guest34506!bennabiyma@gateway/shell/matrix.org/x-hbmfkpawbcreetrv)
03:02adrianor1 is now known as adrianorg
05:26vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
06:24ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
14:12qqqqqqqqq9 has joined IRC (qqqqqqqqq9!~guido@p5DD6E5E8.dip0.t-ipconnect.de)
14:13
<qqqqqqqqq9>
Hi, how do i get nbd-server to listen on ip4 and ip6? I have listenaddr = 0.0.0.0 , :: in my config, but always uses only the first entry.
14:28
<alkisg>
qqqqqqqqq9: just leave the default, without listenaddr...
14:29
manpages.ubuntu.com/nbd-server => If it is not set, nbd-server will listen to "::, 0.0.0.0", which causes nbd-server to listen to all local IPv4 and IPv6 addresses
15:05
<qqqqqqqqq9>
alkisg: I tried that, netstat -plnt | grep nbd
15:05
grep me only a tcp6 line
15:34neopss has joined IRC (neopss!~neops@unaffiliated/neops)
15:34
<neopss>
hello
15:34
speak french?
15:34
<alkisg>
qqqqqqqqq9: same here, yet it does answer to tcp4 requests
15:34
neopss: no, english/greek :)
15:34
Maybe some Finnish too... :D
15:36
<neopss>
help me please
15:36
<alkisg>
What is the problem?
15:36
<neopss>
i use debian 9.1 ::but black screen https://ibb.co/mfWWWR
15:37
https://ibb.co/bDKeJ6
15:37
<alkisg>
Are you using LTSP?
15:37
<neopss>
ltsp-server-standalone
15:37
<alkisg>
Install epoptes, to help in troubleshooting:
15:37
!epoptes
15:37
<ltsp`>
epoptes: Epoptes is a computer lab administration and monitoring tool. It works on Ubuntu and Debian based labs with LTSP or non-LTSP servers, thin and fat clients, standalone workstations, NX clients etc. More info: http://www.epoptes.org
15:39
<alkisg>
Then from epoptes, right click on the ltsp client, open terminal, root locally, and type: xrandr
15:39
And paste the output to !pastebin
15:39
<neopss>
ok im test apt-get install epoptes
15:40
<alkisg>
check epoptes.org/installation, you need to install epoptes-client in the chroot too, and run epoptes-client -c in the chroot, and ltsp-update-image outside of the chroot
15:49
<neopss>
why i have to install epoptes i is not included
15:49
why epotes install ?
15:49
it is mandatory ?
15:56
sorry for my english
15:57
I just want to check black screen, not have new functionality
15:57
alkisg,
16:34
<alkisg>
neopss: epoptes will help you check why the screen is black
16:34
neopss: otherwise you would have to install ssh to the client, then run some weird command to get access to xorg from ssh, etc
16:34
<neopss>
ok i just install i do what after
16:35
<alkisg>
neopss: do you see the client in epoptes?
16:35
Does it have a green or a fat icon?
16:35
*a blue icon?
16:36
<neopss>
https://pastebin.com/mARWLTjE
16:36
<qqqqqqqqq9>
alkisg: So, it wasn't the guilty part. Anyway, I got my problem (Non-booting client) fixed. Thanks!
16:36
<alkisg>
qqqqqqqqq9: np
16:36
neopss: please read epoptes.org/installation for installation instructions
16:36
http://epoptes.org/installation
16:36
You run epoptes-client -c in the chroot, not on the server
16:37
<neopss>
http://hpics.li/a17efb0
16:38
<alkisg>
neopss: did you read http://epoptes.org/installation?
16:39
Please read it..
16:39
<neopss>
ok
16:39
thx alkisg
16:47
alkisg, http://hpics.li/bd24833
17:03
<alkisg>
neopss: did you reboot the client? If yes, you didn't set up the chroot correctly
17:05
See the last paragraph of epoptes.org/installation
17:11
neopss: what's the output of this command? sudo ls -l /etc/epoptes/* /opt/ltsp/*/etc/epoptes/*
17:13
<neopss>
https://pastebin.com/p4us4vEM
17:13
<alkisg>
You ran epoptes-client -c on the server and damaged the keys
17:13
Run apt-get purge epoptes; apt get install epoptes to reinstall it,
17:13
and then sudo ltsp-chroot epoptes-client -c to put it to the chroot,
17:13
and finally ltsp-update-image to rebuild the image
17:25
<neopss>
https://ibb.co/dqfQrR
17:25
its ok ?
17:26
it has well download image
17:27
and type commands to generate certificates
17:27
but I do not understand the continuation > alkisg
17:38
<alkisg>
neopss: when you boot the client, you must see it in epoptes
17:38
If not, the it's not installed correctly and we can't access the logs of the clients etc
17:39
<neopss>
I understand ,
17:39
How to start epoptes without being root
17:39
without being in the root session
17:40
<alkisg>
you run epoptes without being root
17:40
<neopss>
*.icon ?
17:40
<alkisg>
E.g. alkisg@ltsp:~$ epoptes
17:40
Or from the menu
17:41
<neopss>
epoptes : > Service connection erreor (probleme permission...
17:41
<alkisg>
Did you read the installation page about adding yourself to the epoptes group and logoff/logon?
17:42
"After the installation you need to add some users to the "epoptes" group (or use another group as mentioned in the Configuration section below). These users will be allowed to launch the GUI and control clients: gpasswd -a username epoptes
17:42
Users that are currently logged on need to logoff/logon for the group change to take effect (or use newgrp)."
17:42
You can read it there, no need for me to copy/paste it here...
17:42
<neopss>
gpasswd: user 'neops epoptes' does not exist
17:43
ok
17:43
<alkisg>
gpasswd -a neopss epoptes
17:43
<neopss>
ok its good now
17:43
sorry ^^
17:45
I have epoptes but I do not see the client workstation alkisg
17:47
<alkisg>
Then you didn't install it properly, maybe you didn't read the instructions :/
18:08
neopss: I can help using remote support for a couple of minutes, are you here?
18:14
<neopss>
alkisg, ok
18:18
you are the alkisg ?
18:21
<alkisg>
!vnc-edie
18:21
<ltsp`>
I do not know about 'vnc-edie', but I do know about these similar topics: 'vnc-edide', 'vnc-dide'
18:21
<alkisg>
!vnc-edide
18:21
<ltsp`>
vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
18:21
<alkisg>
neopss: do this ^
18:23neopss has left IRC (neopss!~neops@unaffiliated/neops, Read error: Connection reset by peer)
19:02
<Guest34506>
alkisg: when I try to start the epoptes service... epoptes[1982]: /usr/bin/twistd: Unknown command: epoptes
19:02neops has joined IRC (neops!~neops@unaffiliated/neops)
19:02
<neops>
re
19:03
sorry alkisg
19:03
im eat etc...
19:05
<alkisg>
bb in 10 mins
19:05
<neops>
thank you for your help, I will rest a little
19:05
<Guest34506>
alkisg: https://pastebin.mozilla.org/9070229 is the error from syslog
19:24
<alkisg>
neops: are you here?
19:24
!vnc-edide
19:24
<ltsp`>
vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
19:25neops has left IRC (neops!~neops@unaffiliated/neops, Read error: Connection reset by peer)
19:25
<alkisg>
Guest34506: it doesn't seem to be properly installed
19:26
Which distro/version?
19:28
<Guest34506>
Ubuntu 16.04
19:29
mate
19:29
I just tried to reinstall it, but same thing
19:36Guest34506 is now known as bennabiy
19:37
<bennabiy>
alkisg: just tried to reinstall after a purge, and same thing
19:39
<alkisg>
bennabiy: maybe you mixed python2/python3 defaults?
19:40
<bennabiy>
how?
19:41
<alkisg>
no idea..
19:42
<bennabiy>
Hrm. How would I even check that?
19:43
/usr/bin/python points to 2.7
20:14gverv has joined IRC (gverv!8b5b4936@gateway/web/freenode/ip.139.91.73.54)
20:16gverv has left IRC (gverv!8b5b4936@gateway/web/freenode/ip.139.91.73.54, Client Quit)
20:32ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
22:56dsj2 has joined IRC (dsj2!~david@71-90-224-179.dhcp.gnvl.sc.charter.com)
22:56
<dsj2>
sbalneav1
22:56
Scotty, are you there?
22:58[foo]bar has joined IRC ([foo]bar!~asdfasdf@unaffiliated/foobar/x-9027208)