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


Channel log from 7 October 2015   (all times are UTC)

00:48cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Read error: Connection timed out)
00:49cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
01:16cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Read error: Connection timed out)
01:17cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
01:29F-GT has joined IRC (F-GT!~phantom@ppp121-44-252-216.lns20.syd7.internode.on.net)
01:38gbaman has left IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net, Remote host closed the connection)
01:44gbaman has joined IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net)
01:51cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Read error: Connection timed out)
01:52cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
02:08gbaman has left IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net, Remote host closed the connection)
02:18gbaman has joined IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net)
02:22gbaman has left IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net, Ping timeout: 244 seconds)
02:38cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Read error: Connection timed out)
02:41
<work_alkisg>
staffencasa: ubuntu in 15.04 is very broken, you'll want the daily builds ppa to use that
02:41cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
02:42
<work_alkisg>
Although this shouldn't be what's causing the tftp issue, you'll nevertheless find 10 other critical issues that make it not working
02:45
ltsp in ubuntu 15.10 works pretty well with the greek schools ppa though
02:52
<maldridge>
work_alkisg: If you were standing up a new cluster, what revision of ubuntu would you recommend
02:53
<work_alkisg>
Yesterday I was setting up Ubuntu/LTSP in a school. After spending 3-4 hours I saw that the problem was the 3.13 kernel. Reverting to 3.2 (plain 12.04.1) made clients work again.
02:54
<maldridge>
ok, 14.04 is very broken at the moment
02:54
<work_alkisg>
(the problem being that clients hanged without any messages after 1-2 minutes)
02:54
<maldridge>
thinking I should just revert
02:54
<work_alkisg>
So what I'm thinking is that I need a big choice in kernels + xorgs
02:54
Only LTS releases offer that
02:55
14.04 now has 3 different kernels and xorgs, it should be ok... (with the greek schools ppa if you're using ltsp)
02:56
gnome-keyring gets disabled though by ltsp because it produces thousands of temp lock files
02:58
<maldridge>
I'm using the ppa, but not nbd
02:59
14.04 had issues mounting the nbd volume during image generation
02:59
<work_alkisg>
it's solved in the ppa
02:59
<maldridge>
hm, I'll double check why the PPA wasn't given priority
02:59
<work_alkisg>
and the problem with keyrings is not in / but in /home, i.e. in sshfs
02:59
<maldridge>
yeah, I don't run keyrings on my networks
02:59cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Read error: Connection timed out)
03:00
<work_alkisg>
people don't save passwords in firefox?
03:00
*input passwords, whether they save them or not...
03:00cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
03:01
<maldridge>
we use lastpass as an organization, so its not in the keyring
03:01
everyone uses 2FA
03:01
<work_alkisg>
check if /home/users/.gnome2/keyrings exists or not
03:02
If it does, then firefox did call gnome-keyrings-daemon
03:05
<maldridge>
nope, though not particularly surprising, we run firefox from an internal repo where we disable all autofill and all credential management
03:06
<work_alkisg>
The location for keyrings is different in recent versions, I don't know if that affects 14.04 as well, I think maybe in .local/share/keyrings
03:16cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Read error: Connection timed out)
03:17cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
03:19gbaman has joined IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net)
03:24gbaman has left IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net, Ping timeout: 265 seconds)
03:28cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 255 seconds)
03:45Parker955_Away has joined IRC (Parker955_Away!~parker@2607:5300:60:8425::2d62:a8e6)
04:21gbaman has joined IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net)
04:22vmlintu has joined IRC (vmlintu!~vmlintu@a91-152-200-13.elisa-laajakaista.fi)
04:25gbaman has left IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net, Ping timeout: 246 seconds)
04:32work_alkisg is now known as alkisg
04:35gdi2k has joined IRC (gdi2k!~gdi2k@203.177.248.238)
04:49gdi2k has left IRC (gdi2k!~gdi2k@203.177.248.238, Ping timeout: 240 seconds)
05:13gehidore has left IRC (gehidore!~username@unaffiliated/man, Quit: WeeChat 1.3)
05:16gehidore has joined IRC (gehidore!~username@unaffiliated/man)
05:21gbaman has joined IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net)
05:26gbaman has left IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net, Ping timeout: 268 seconds)
05:30
<alkisg>
!nbd-clients
05:30
<ltsp>
I do not know about 'nbd-clients', but I do know about these similar topics: 'nbd-client'
05:30
<alkisg>
!ltsp-clients
05:30
<ltsp>
Error: "ltsp-clients" is not a valid command.
05:30
<alkisg>
!clients
05:30
<ltsp>
I do not know about 'clients', but I do know about these similar topics: 'fatclients', 'epoptes-fat-clients'
05:30
<alkisg>
!nbd
05:30
<ltsp>
I do not know about 'nbd', but I do know about these similar topics: 'disable-nbd-proxy', 'nbd-proxy', 'nbd-compression', 'quick-nbd-tests', 'nbd-client', 'nbd-server-bug', 'nbd-trusty-bug'
05:30
<alkisg>
!client
05:30
<ltsp>
I do not know about 'client', but I do know about these similar topics: 'fatclients', 'fatclient-printers', 'epoptes-fat-clients', 'nbd-client', 'client-list'
05:31
<alkisg>
!client-list
05:31
<ltsp>
client-list: to get a list of all nbd-clients (which sometimes is the same as ltsp clients), run: netstat -tn | sed -n 's/.*:10809 *\([0-9.]*\):.*/\1/p' | sort -Vu
05:31cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
05:56ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)
06:13gdi2k has joined IRC (gdi2k!~gdi2k@180.190.69.83)
06:21mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
06:23gbaman has joined IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net)
06:25gbaman has left IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net, Read error: No route to host)
06:25gbaman has joined IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net)
06:30gbaman has left IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net, Ping timeout: 268 seconds)
06:33khildin has joined IRC (khildin!~khildin@ip-62-235-41-6.dial.scarlet.be)
06:45gbaman has joined IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net)
06:49gbaman has left IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net, Ping timeout: 255 seconds)
06:55gbaman has joined IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net)
06:55thegkor has joined IRC (thegkor!c23fefeb@gateway/web/freenode/ip.194.63.239.235)
06:59gbaman has left IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net, Ping timeout: 264 seconds)
07:33thegkor has left IRC (thegkor!c23fefeb@gateway/web/freenode/ip.194.63.239.235, Quit: Page closed)
07:39NeonLicht has joined IRC (NeonLicht!~NeonLicht@darwin.ugr.es)
07:48alkisg is now known as work_alkisg
07:56gbaman has joined IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net)
07:59andygraybeal has left IRC (andygraybeal!~andy@40.133.184.123, Remote host closed the connection)
08:03khildin has left IRC (khildin!~khildin@ip-62-235-41-6.dial.scarlet.be, Ping timeout: 264 seconds)
08:03gbaman has left IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net, Ping timeout: 252 seconds)
08:05schlady has joined IRC (schlady!~schlady@141-53-215-125.ip.uni-greifswald.de)
09:05oldjoe has joined IRC (oldjoe!c3c38a40@gateway/web/freenode/ip.195.195.138.64)
09:06
<oldjoe>
Hi Guys, please check the page http://wiki.ltsp.org/wiki/Installation there has been some gambling links added to the bottom of the page
09:09
<work_alkisg>
Thank you oldjoe
09:09
Hyperbyte: we've been hacked ^
09:09work_alkisg is now known as alkisg
09:19
<Hyperbyte>
alkisg, it's a public wiki.
09:19
We've been spammed.
09:19
But you can undo all of these edits I think.
09:19
<alkisg>
Hyperbyte: do we want it to be public?
09:19
<Hyperbyte>
Well you have to register.
09:19
<alkisg>
Can bots register?
09:19
That wasn't manual, was it?
09:19
No captcha etc involved in the registration?
09:20
Anyway, do whatever you prefer, oh mighty web master of ltsp :)
09:21
<Hyperbyte>
I'll just undo all contribs by Domtheo
09:23
And blocked account as well
09:23
Fixed.
09:23
<alkisg>
Cool! :)
09:30vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-13.elisa-laajakaista.fi, Ping timeout: 246 seconds)
09:33oldjoe has left IRC (oldjoe!c3c38a40@gateway/web/freenode/ip.195.195.138.64)
09:34stgraber has left IRC (stgraber!~stgraber@ubuntu/member/stgraber, Quit: kernel update)
09:43vmlintu has joined IRC (vmlintu!~vmlintu@37-219-183-202.nat.bb.dnainternet.fi)
09:46stgraber has joined IRC (stgraber!~stgraber@shell.stgraber.org)
09:47stgraber has left IRC (stgraber!~stgraber@shell.stgraber.org, Changing host)
09:47stgraber has joined IRC (stgraber!~stgraber@ubuntu/member/stgraber)
09:48schlady has left IRC (schlady!~schlady@141-53-215-125.ip.uni-greifswald.de, Remote host closed the connection)
09:56ioanna has joined IRC (ioanna!c23fefeb@gateway/web/freenode/ip.194.63.239.235)
10:02ioanna has left IRC (ioanna!c23fefeb@gateway/web/freenode/ip.194.63.239.235, Quit: Page closed)
10:12lbssousa has joined IRC (lbssousa!~laercio@177.143.56.37)
10:21schlady has joined IRC (schlady!~schlady@141-53-215-125.ip.uni-greifswald.de)
10:24alkisg is now known as work_alkisg
10:29gdi2k has left IRC (gdi2k!~gdi2k@180.190.69.83, Ping timeout: 240 seconds)
10:34gdi2k has joined IRC (gdi2k!~gdi2k@203.177.248.238)
10:36gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
10:38gbaman has joined IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net)
10:40gdi2k has left IRC (gdi2k!~gdi2k@203.177.248.238, Ping timeout: 240 seconds)
10:41admin-lab has joined IRC (admin-lab!c23fefeb@gateway/web/freenode/ip.194.63.239.235)
10:41admin-lab has left IRC (admin-lab!c23fefeb@gateway/web/freenode/ip.194.63.239.235, Client Quit)
10:43khildin has joined IRC (khildin!~khildin@ip-62-235-41-6.dial.scarlet.be)
11:06lbssousa has left IRC (lbssousa!~laercio@177.143.56.37, Ping timeout: 240 seconds)
11:06Phantomas has joined IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
11:10vmlintu has left IRC (vmlintu!~vmlintu@37-219-183-202.nat.bb.dnainternet.fi, Ping timeout: 246 seconds)
11:14vmlintu has joined IRC (vmlintu!~vmlintu@37-219-183-202.nat.bb.dnainternet.fi)
11:25danau11 has joined IRC (danau11!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
11:30adrianorg has left IRC (adrianorg!~adrianorg@177.204.149.125.dynamic.adsl.gvt.net.br, Ping timeout: 268 seconds)
11:31danau11 has left IRC (danau11!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
11:32adrianorg has joined IRC (adrianorg!~adrianorg@179.183.66.186)
11:40vmlintu has left IRC (vmlintu!~vmlintu@37-219-183-202.nat.bb.dnainternet.fi, Ping timeout: 244 seconds)
11:41Faith has joined IRC (Faith!~paty_@unaffiliated/faith)
11:55lbssousa has joined IRC (lbssousa!~laercio@187.11.244.53)
12:05gvy has left IRC (gvy!~mike@altlinux/developer/mike, Read error: Connection reset by peer)
12:05gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
12:06gbaman has left IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net, Remote host closed the connection)
12:07lbssousa has left IRC (lbssousa!~laercio@187.11.244.53, Quit: lbssousa)
12:08lbssousa has joined IRC (lbssousa!~laercio@187.11.244.53)
12:09lbssousa has joined IRC (lbssousa!~laercio@187.11.244.53)
12:16lbssousa has left IRC (lbssousa!~laercio@187.11.244.53, Quit: lbssousa)
12:16lbssousa has joined IRC (lbssousa!~laercio@187.11.244.53)
12:24danau111 has joined IRC (danau111!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
12:35vmlintu has joined IRC (vmlintu!~vmlintu@37-219-183-202.nat.bb.dnainternet.fi)
12:38lbssousa has left IRC (lbssousa!~laercio@187.11.244.53, Quit: lbssousa)
12:38lbssousa has joined IRC (lbssousa!~laercio@187.11.244.53)
12:41UserTest has joined IRC (UserTest!8d3522b2@gateway/web/freenode/ip.141.53.34.178)
12:44
<UserTest>
Hello, in the lts.conf is the parameter "LDM_GUESTLOGIN", that I enabled. But logging in as Guest, causes that in the panel (Ubuntu 14.04 Mate) disappears the "Shutdown" button. Any help how I can activate it?
12:45
Logged in as not Guest but "normal" or LDAP user, the "Shutdown" button is activated.
12:50vmlintu has left IRC (vmlintu!~vmlintu@37-219-183-202.nat.bb.dnainternet.fi, Ping timeout: 246 seconds)
13:02
<maldridge>
guest user not in the same/right groups maybe?
13:10Phantomas has left IRC (Phantomas!~ftsamis@ubuntu/member/phantomas, Quit: Leaving.)
13:21khildin has left IRC (khildin!~khildin@ip-62-235-41-6.dial.scarlet.be, Ping timeout: 246 seconds)
13:35lbssousa has left IRC (lbssousa!~laercio@187.11.244.53, Quit: lbssousa)
13:36lbssousa has joined IRC (lbssousa!~laercio@187.11.244.53)
13:42
<UserTest>
I define Guest User in the lts.conf like
13:43
[XX.XX.XX.XX.XX.XX]
13:43
LDM_GUESTLOGIN=TRUE
13:43
LDM_USERNAME=username
13:43
LDM_PASSWORD=password
13:43
<maldridge>
yes, but does that username have permission to shut down the machine? I'm pretty sure mate hides that menu if the user isn't in the correct groups
13:44khildin has joined IRC (khildin!~khildin@ip-62-235-41-6.dial.scarlet.be)
13:45
<UserTest>
I can login with username and password manually and then the shutdown button is activated
13:46
<maldridge>
yes, because your user is in the correct groups, but your guest user isn't
13:48
<UserTest>
When I defined the guest username and password in lts.conf, what I have to do to add him to correct groups?
13:48
Thanks for help
13:50
<maldridge>
I'm not sure what group that is on ubuntu, might be powerdev?
13:50
logged in as you, run "groups" in a terminal and see if there's a group that looks like it has to do with power
13:51
then sudo usermod -aG <group> <user> on your guest user
13:51
<UserTest>
I will do it now, thank you very much
13:53ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
13:56mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
14:22khildin has left IRC (khildin!~khildin@ip-62-235-41-6.dial.scarlet.be, Ping timeout: 252 seconds)
14:31schlady has left IRC (schlady!~schlady@141-53-215-125.ip.uni-greifswald.de, Remote host closed the connection)
14:45
<lbssousa>
Phantomas, I've opened an issue in x11vnc github page about that problem with -grabkbd. See https://github.com/LibVNC/x11vnc/issues/18
14:46
I've also created a new branch with a x11vnc wrapper to circumvent these problems with -grabkbd and -grabptr options. See https://code.launchpad.net/~oiteam/epoptes/x11vnc-wrapper-with-alt-input-grabbing
14:49schlady has joined IRC (schlady!~schlady@141-53-215-125.ip.uni-greifswald.de)
14:53schlady has left IRC (schlady!~schlady@141-53-215-125.ip.uni-greifswald.de, Ping timeout: 240 seconds)
14:56ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Ping timeout: 265 seconds)
14:58khildin has joined IRC (khildin!~khildin@ip-62-235-41-6.dial.scarlet.be)
14:58NeonLicht has left IRC (NeonLicht!~NeonLicht@darwin.ugr.es, Quit: leaving)
14:58ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
15:09schlady has joined IRC (schlady!~schlady@141-53-215-125.ip.uni-greifswald.de)
15:10Phantomas has joined IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
15:14khildin has left IRC (khildin!~khildin@ip-62-235-41-6.dial.scarlet.be, Ping timeout: 244 seconds)
15:21danau111 has left IRC (danau111!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
15:25UserTest has left IRC (UserTest!8d3522b2@gateway/web/freenode/ip.141.53.34.178, Ping timeout: 246 seconds)
15:29cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 246 seconds)
15:39gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
16:00cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
16:03schlady has left IRC (schlady!~schlady@141-53-215-125.ip.uni-greifswald.de, Remote host closed the connection)
16:06work_alkisg is now known as alkisg
16:09Phantomas has left IRC (Phantomas!~ftsamis@ubuntu/member/phantomas, Ping timeout: 256 seconds)
16:14khildin has joined IRC (khildin!~khildin@ip-62-235-41-241.dial.scarlet.be)
16:25Phantomas has joined IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
16:32schlady has joined IRC (schlady!~schlady@ip1f111304.dynamic.kabel-deutschland.de)
16:38gbaman has joined IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net)
16:42schlady has left IRC (schlady!~schlady@ip1f111304.dynamic.kabel-deutschland.de, Remote host closed the connection)
16:51vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
16:58
<lbssousa>
Phantomas, alkisg, in my computer lab, I didn't install epoptes-client on my server. I've just installed epoptes on server with "apt-get --no-install-recommends". Everything goes fine, except that it doesn't install socat (needed for opening terminals) and x11vnc (needed for broadcasting) automatically.
16:58
<alkisg>
lbssousa: isn't that the expected behaviour with --no-recommends? :)
16:59
<lbssousa>
Could you make them explicit dependencies of epoptes package?
16:59
<alkisg>
Depends? why?
16:59
"recommends" afaik means "most of the functionality is there"
17:00
...if someone doesn't want to open terminals etc, he can skip socat
17:00
vagrantc can tell us if this would be considered "depends" or "recommends"
17:01
<lbssousa>
Anyway, could you make them explicit "Recommends" por epoptes package?
17:01
<vagrantc>
"The `Recommends' field should list packages that would be found together with this one in all but unusual installations."
17:01
<lbssousa>
So they won't be autoremoved if I remove epoptes-client from my server?
17:01
<alkisg>
epoptes recommends epoptes-client which recommends socat
17:02
OK let me think...
17:02
<vagrantc>
what's the use-case of epoptes installed without epoptes-client?
17:02
<alkisg>
A standalone installation with no ltsp-pnp etc
17:02
<lbssousa>
Yes. I don't use LTSP in my lab.
17:03
All clients are standalone ones.
17:03
<alkisg>
I think what you're saying does make sense, but those 2 won't be the only recommended things that we'll need
17:04
<vagrantc>
explicit recommends/depends might be appropriate rather than relying on an implicit recommends or depends from a recommended package
17:05
<alkisg>
lbssousa: to work around the issue now, you can just install the packages manually (apt-get install socat etc) before removing epoptes-client
17:06
Do file a bug report about this issue
17:06
<lbssousa>
alkisg: OK
17:07
Filing...
17:07
<alkisg>
lbssousa: if you could also please tell us the packages that are needed, it would help
17:07
<vagrantc>
lbssousa: does it cause problems to have epoptes-client installed in your environment?
17:07
<alkisg>
I.e. install epoptes with no recommends, and then try all its features, and tell us "socat is needed for terminals and reverse text-based connections" etc
17:07
<lbssousa>
OK
17:07
<alkisg>
epoptes-client doesn't run by default when epoptes is installed in that pc
17:08
So it shouldn't be causing any issues afaik
17:18
<lbssousa>
alkisg, it's true if epoptes-client is being started as a system (by root) instance, but it seems not true if it's launched as a session (by user) instance.
17:19
<alkisg>
lbssousa: that is true, because we want it for the teacher to be able to monitor students connected with e.g. x2go
17:20
<lbssousa>
Ah, OK.
17:20
<alkisg>
And if someone doesn't want himself monitored, he can de-select it from the autostarted programs
17:20
Is that why you want to remove epoptes-client?
17:23
<lbssousa>
Well, it's one reason. The other one is keeping my server installation as clean as possible, so I'm investigating what's strictly needed for epoptes server only.
17:29
<vagrantc>
alkisg: is the python-central backwards compatibility still needed in epoptes?
17:30
<alkisg>
vagrantc: I don't remember, I'd need to look into it...
17:31
<vagrantc>
alkisg: looks like ubuntu 14.04 has dh-python, which i think is what's needed
17:31
<alkisg>
We still need support for 12.04
17:31
<vagrantc>
ok
17:32
two more years, then?
17:32
<alkisg>
http://packages.ubuntu.com/search?keywords=dh-python
17:32
Haha, just one
17:33
<vagrantc>
wow, it's been a while since i've actually used/tested epoptes
17:33
probably not since november 2013
17:33
<alkisg>
(we won't be making any new releases of anything for 12.04 after 16.04 is out... similar to your backports to oldstable)
17:34* vagrantc 's non-existant backports
17:34
<vagrantc>
we'll see though, i'm using LTSP in the real world again, might e more inclined to do some backporting
17:39* alkisg waves, later...
17:39alkisg is now known as work_alkisg
18:05Phantomas has left IRC (Phantomas!~ftsamis@ubuntu/member/phantomas, Quit: Leaving.)
18:16khildin has left IRC (khildin!~khildin@ip-62-235-41-241.dial.scarlet.be, Ping timeout: 244 seconds)
18:32
<vagrantc>
doh.
18:32
work_alkisg: not sure what i'm doing wrong, but a user in group epoptes can't access the epoptes socket :(
18:33* vagrantc runs from console and gets some interesting errors
18:35
<vagrantc>
https://paste.debian.net/314856
18:52
it seems like it's not creating the epoptes socket
18:53
<lbssousa>
vagrantc, is your twisted daemon running?
18:54
<quinox>
that sounds dirty
18:55
<vagrantc>
also stopping epoptes doesn't kill the socat processes....
18:55khildin has joined IRC (khildin!~khildin@ip-62-235-41-241.dial.scarlet.be)
18:56
<vagrantc>
lbssousa: how would i check?
18:57
lbssousa: all i see are three socat processes
18:57
<lbssousa>
It seems you are in Debian testing, right?
18:57
Try systemctl status epoptes
18:57
<vagrantc>
yes
18:58
Process: 782 ExecStart=/etc/init.d/epoptes start (code=exited, status=0/SUCCESS)
18:58
Active: active (exited) since Wed 2015-10-07 11:56:11 PDT; 1min 38s ago
18:58
<lbssousa>
Oh, your twisted daemon has died
19:00
<vagrantc>
syslog has this line: stretchltsp epoptes[782]: Error retrieving file stats for file [/etc/lts.conf]: No such file or directory
19:00
but it should obviously work without lts.conf ...
19:03
lbssousa: does epoptes start twistd, or should that be running from some other package?
19:03
<lbssousa>
It should be started by e.g. "systemctl start epoptes"
19:04
Or "/etc/init.d/epoptes start"
19:05
<vagrantc>
doesn't start...
19:06
and doesn't appear to leave any useful log messages
19:06* vagrantc sighs
19:06* vagrantc puts off epoptes for another day
19:08* vagrantc tries with sysvinit
19:10
<lbssousa>
vagrantc, just is case, you can try my systemd service file for epoptes: https://aur.archlinux.org/cgit/aur.git/plain/epoptes.service?h=epoptes-bzr
19:11
Save it in /etc/systemd/system and start it with "systemctl start epoptes.service"
19:12
You can rename the file to avoid conflicts with original sysvinit one.
19:12
e.g. epoptes-server.service
19:19
Anyone here using Polari for IRC?
19:20* quinox uses Weechat inside tmux over mosh
19:21
<quinox>
the screenshots look nice
19:23
<lbssousa>
test 2
19:26khildin has left IRC (khildin!~khildin@ip-62-235-41-241.dial.scarlet.be, Quit: I'm gone, bye bye)
19:30danau11 has joined IRC (danau11!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
19:34danau11 has left IRC (danau11!~durban@static-72-89-243-139.nycmny.fios.verizon.net, Ping timeout: 246 seconds)
19:42work_alkisg is now known as alkisg
19:42
<alkisg>
vagrantc: it sounds like the epoptes daemon isn't started, do you want us to see it together with screen/socat/vnc?
19:44* vagrantc got caught up in other things at the moment
19:44
<alkisg>
/usr/bin/python /usr/bin/twistd --pidfile /var/run/epoptes.pid --logfile /var/log/epoptes.log epoptes
19:44
That's a usual epoptes-daemon process
19:45
<vagrantc>
ok, definitely not running
19:46
<alkisg>
The socket is at /run/epoptes/epoptes.socket
19:46
and /var/log/epoptes.log may help
19:47
I don't know why epoptes would look in /etc/lts.conf
19:50
<vagrantc>
something from epoptes/common/ltsconf.py ?
19:51
<alkisg>
vagrantc: do you have a symlink from /var/lib... lts.conf to /etc/lts.conf?
19:56
vagrantc: I'll put stretch in a vm, which cd is closer to your setup? http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-lxde-CD-1.iso ?
19:57
<vagrantc>
i've actually been running gnome ...
19:57* vagrantc just always uses mini.iso and a caching proxy
19:57* alkisg downloads http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-CD-1.iso ...
19:57
<vagrantc>
though it wouldn't be a half-bad idea to just reinstall my setup from scratch ... tried enough weird things with it
19:58
<alkisg>
Fortunately I have good internet here, it only takes 1 minute...
19:58* vagrantc hopes testing is installable at the moment, just had a kernel update
19:59danau11 has joined IRC (danau11!~durban@rrcs-198-179-71-210.nyc.biz.rr.com)
20:01
<alkisg>
The graphics installer showed up fine...
20:01
<vagrantc>
if you get to the partitioning disks phase you should be fine
20:01
looks like epoptes 0.5.8 will be short-lived... :)
20:02
ok, other issues solved, back to epoptes...
20:03
<alkisg>
vagrantc: anything useful at epoptes.log/
20:03
?
20:04
<vagrantc>
no log
20:04lbssousa has left IRC (lbssousa!~laercio@187.11.244.53, Quit: lbssousa)
20:04
<alkisg>
What happens if you run that command manually?
20:04
/usr/bin/python /usr/bin/twistd --pidfile /var/run/epoptes.pid --logfile /var/log/epoptes.log epoptes
20:06
<vagrantc>
with the service file lbssousa provided, it starts when i start it manually, but not on boot
20:06
<alkisg>
vagrantc: maybe you hit the bug where systemd doesn't run a service twice?
20:07
maybe you need to run service epoptes stop; service epoptes start
20:07
(that doesn't answer why epoptes didn't start the first time)
20:09
<vagrantc>
er, manually, using: sudo systemctl start epoptes
20:10
so the init script doesn't work on stretch, and this service file seems to have some issues...
20:10
<alkisg>
vagrantc: run `systemctl stop epoptes` before that
20:10
<vagrantc>
before what?
20:10
<alkisg>
Before `systemctl start epoptes`
20:11
To tell systemd that the service is stopped
20:11
<vagrantc>
it was already stopped
20:11
<alkisg>
Did systemd say that?
20:11
Because in your logs it doesn't
20:11
(in the paste you provided)
20:11
<vagrantc>
that's old news.
20:11
but we can go back to that
20:12
now that i have epoptes running, i'm going to boot a client, and see if there are other issues, and then come back to the startup issue
20:13
<alkisg>
OK, I should have stretch up and running in a few minutes...
20:13
I'll troubleshoot the startup issue
20:13
<vagrantc>
alkisg: cool.
20:13
i should probaly do a clean install as well
20:14
well, booted client doesn't show up either
20:15
before or after login ... running gnome3
20:15
<alkisg>
Did you run epoptes-client -c?
20:16danau11 has left IRC (danau11!~durban@rrcs-198-179-71-210.nyc.biz.rr.com, Ping timeout: 260 seconds)
20:16
<vagrantc>
you mean did i follow the installation instructions? :)
20:16
i thought with a ltsp-pnp that's done automatically
20:16
<alkisg>
Yup that would work
20:17
What happens if you manually run epoptes-client from the client?
20:17
e.g. from inside the session...
20:20
vagrantc: how should I go about installing some new ltsp version in stretch? debuild by myself?
20:20
Do you have any handy repositories somewhere?
20:21
<vagrantc>
not yet, but i could probably push something quick
20:21* alkisg would appreciate that
20:21
<vagrantc>
alkisg: so, on an ltsp (PNP) fatclient?
20:21
<alkisg>
yes
20:21
<vagrantc>
alkisg: what should i see for processes?
20:21
epoptes-client ?
20:22
socat?
20:22
<alkisg>
epoptes-client, yes
20:22
socat too
20:22
epoptes-client is dash renamed
20:22
socat is for the transport part
20:22
<vagrantc>
i just see two socat processes, no epoptes-client processes
20:23
<alkisg>
maybe they did not manage to connect
20:23
Can you run epoptes-client manually to see its output?
20:24
<vagrantc>
so, "/usr/sbin/epoptes-client"
20:24
?
20:24
no arguments?
20:24
<alkisg>
yes
20:24
OK I have stretch+gnome installed and updated
20:25
I'll try installing epoptes from the ppa first
20:29andygraybeal has joined IRC (andygraybeal!~andy@40.133.184.123)
20:30
<alkisg>
vagrantc: add-apt-repository ppa:alkisg; apt-get update; apt-get install epoptes ==> epoptes is now automatically started
20:30
I didn't do anything more than that after installation...
20:31
No reboot either after installing epoptes
20:33
vagrantc: maybe you have ipv6 enabled and it breaks some scripts for epoptes-client?
20:33
I don't know if it supports ipv6...
20:33
<vagrantc>
just link-local stuff ...
20:33
i.e. the defaults
20:34
alkisg: i built the package on sid, so maybe sid's build environment resulted in some incompatibilities...
20:34
<alkisg>
vagrantc: if you set up some repository I can troubleshoot tomorrow morning
20:34
<vagrantc>
i'll also try with a fresh install
20:34
alkisg: done.
20:34
alkisg: deb http://cascadia.aikidev.net/~vagrant/debian UNRELEASED main
20:35
alkisg: has ldm, ltsp, ltspfs and epoptes
20:35
<alkisg>
Thanks, let me try that now...
20:37
<vagrantc>
alkisg: you can find my key in the debian-keyring package :)
20:40
<alkisg>
vagrantc: I reverted the VM "just installed" snapshot, added your repo, apt-get install --allow-unauthenticated epoptes, and now epoptes is running
20:40
I didn't have to do anything else...
20:40
<vagrantc>
ok, i guess i'll try a fresh install
20:40
although what messed it up is a little unnerving
20:42
<alkisg>
To save some time in testing: LTSP_CLIENT_MAC=a1:b2:c3:d4:e5:f6 LTSP_CLIENT=1.2.3.4 LTSP_HOSTNAME=pc01 /usr/sbin/epoptes-client localhost
20:42
--> emulates a client, it connected fine
20:43
I'll try the ltsp/ldm etc versions tomorrow, along with ltsp-pnp and epoptes
20:46
<vagrantc>
it's still configured to default to NFS ... which is still broken
20:47
<alkisg>
ltsp-pnp isn't default anywhere...
20:47
although I'm guessing it could start being the default (meaning dnsmasq etc, not the -c / part)
20:48
proxydhcp is a much easier way, it doesn't require someone to change his networking etc
20:49
and it also automatically supports 2 nic setups with 192.168.67.1
20:49
<vagrantc>
right
20:49
<alkisg>
vagrantc, do you think it would make sense to add an ltsp-pnp metapackage?
20:50
this will also make more sense, now we're only talking about ltsp-pnp as a concept
20:50
ltsp-pnp would add all the defaults that ltsp-pnp uses
20:50
dnsmasq, proxy, ltsp-server and client, nbd default..
20:51StolenToast has joined IRC (StolenToast!~stolentoa@cnut.resist.cc)
20:51
<alkisg>
That would be the same in debian and ubuntu, without breaking the existing how-to's
20:51
So I'd like it if it would go like: apt-get install ltsp-pnp; ltsp-update-image -c / ==> done
20:51
That would be the ltsp-pnp how-to...
20:52
<vagrantc>
there's some logic to that...
20:52tecnico has joined IRC (tecnico!58166c98@gateway/web/freenode/ip.88.22.108.152)
20:52
<alkisg>
if really needed, we could add an `ltsp-config pnp` step
20:52
<vagrantc>
right
20:52
<alkisg>
But the ltsp-pnp package should take care of the dependencies
20:52* vagrantc really needs to update debian/copyright
20:53tecnico has left IRC (tecnico!58166c98@gateway/web/freenode/ip.88.22.108.152, Client Quit)
20:56* alkisg => pumpkin :)
20:56alkisg is now known as work_alkisg
20:56
<vagrantc>
night!
20:59ricotz has left IRC (ricotz!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)
21:13Faith has left IRC (Faith!~paty_@unaffiliated/faith, Quit: Leaving)
21:28danau11 has joined IRC (danau11!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
21:30danau11 has left IRC (danau11!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
23:31jammcq has joined IRC (jammcq!~jam@c-107-4-115-38.hsd1.mi.comcast.net)