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


Channel log from 17 November 2017   (all times are UTC)

00:47eu^173-24-31-145 has joined IRC (eu^173-24-31-145!ad181f91@gateway/web/freenode/ip.173.24.31.145)
00:47
<eu^173-24-31-145>
Hello
00:47
I was wondering if this project monitors history?
00:52eu^173-24-31-145 has left IRC (eu^173-24-31-145!ad181f91@gateway/web/freenode/ip.173.24.31.145, Ping timeout: 260 seconds)
02:20GodFather has left IRC (GodFather!~rcc@47.33.250.142, Read error: No route to host)
02:21GodFather has joined IRC (GodFather!~rcc@47.33.250.142)
02:25GodFather has left IRC (GodFather!~rcc@47.33.250.142, Ping timeout: 240 seconds)
04:06adrianorg has left IRC (adrianorg!~adrianorg@189.114.158.195, Ping timeout: 248 seconds)
04:38adrianorg has joined IRC (adrianorg!~adrianorg@189.114.158.195)
05:01alazyworkaholic has left IRC (alazyworkaholic!~alan@179.126.101.148, Ping timeout: 240 seconds)
05:03alazyworkaholic has joined IRC (alazyworkaholic!~alan@189.41.157.200)
06:24Statler has joined IRC (Statler!~Georg@p579FE79B.dip0.t-ipconnect.de)
07:00ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:29alazyworkaholic has left IRC (alazyworkaholic!~alan@189.41.157.200, Disconnected by services)
07:29alazywor1 has joined IRC (alazywor1!~alan@189.41.157.200)
07:51kjackal has joined IRC (kjackal!~quassel@static062038141122.dsl.hol.gr)
07:56kjackal has left IRC (kjackal!~quassel@static062038141122.dsl.hol.gr, Quit: No Ping reply in 180 seconds.)
07:58kjackal has joined IRC (kjackal!~quassel@static062038141122.dsl.hol.gr)
09:24Statler has left IRC (Statler!~Georg@p579FE79B.dip0.t-ipconnect.de, Remote host closed the connection)
09:45kjackal has left IRC (kjackal!~quassel@static062038141122.dsl.hol.gr, Ping timeout: 248 seconds)
09:55adrianorg has left IRC (adrianorg!~adrianorg@189.114.158.195, Ping timeout: 248 seconds)
09:55adrianorg has joined IRC (adrianorg!~adrianorg@189.114.158.195)
09:56kjackal has joined IRC (kjackal!~quassel@2a02:587:3114:a000:8827:89cc:f506:13)
10:47Statler has joined IRC (Statler!~Georg@gwrz3.lohn24.de)
10:51pedro__ has joined IRC (pedro__!d5005718@gateway/web/freenode/ip.213.0.87.24)
10:51
<pedro__>
Hello everybody
10:51
<alkisg>
Hello
10:53
<pedro__>
My name is Pedro and I'm a teacher. I use Epoptes and today, when I started it I couldn't see any computer of the students
10:53
<alkisg>
pedro__: are you using ltsp, i.e. netbooted computers?
10:54
<pedro__>
They are fat clients
10:54
<alkisg>
Do they have a local linux installation in their disks?
10:54
<pedro__>
Yes, they have
10:54
<alkisg>
Which distribution and which version?
10:55
<pedro__>
Yesterday I had problems with two of the computers and executed sudo epoptes-client -c on them, but I executed it on the server too. Could this be the problem?
10:56
Ubuntu 16.04.3 LTS
10:57
<alkisg>
Yes, if you executed epoptes-client -c on the server, it erased its certificate
10:57
Run this, on all your computers: ls -l /etc/epoptes
10:57
If you see any files that are zero size, they have issues and need to be copied from elsewhere
10:59
<pedro__>
Ok, there are some of the computers with server.crt with zero size
11:01
<alkisg>
pedro__: you need to copy that file from a correct computer, to the other damaged computers
11:01
To the server too
11:01
<pedro__>
Can I copy any certificate from any computer to the rest of them?
11:01
<alkisg>
Yes
11:01
<pedro__>
Ok thenks. I'll try that
11:01
<alkisg>
They should be exactly the same
11:01
You can run this, to verify: md5sum /etc/epoptes/*
11:02
If you see the same md5sum, it's the same file
11:04neops has joined IRC (neops!5ee4bfca@gateway/web/freenode/ip.94.228.191.202)
11:04
<neops>
hello
11:04
hello I would like to know if we can make a server linux leger LSTP and boot on a mac
11:04
<alkisg>
What does "leger" mean?
11:06
<neops>
ltsp alkisg
11:06
I would like to have a Linux Terminal Server Project (Debian or Centos) but boot on a Mac
11:07
<alkisg>
neops: the server would be mac or the client would be mac?
11:10
<neops>
no Mac just Client
11:10
<alkisg>
neops: can your mac boot debian normally? is it a usual x86 architecture?
11:13
<neops>
yes alkisg mac book pro 2011 intel
11:13
core 2 duo
11:13
x86..
11:14
<alkisg>
neops: if it boots debian normally, then it will boot ltsp normally as well
11:15
<neops>
ok I'll try this weekend
11:15
thx alkisg
11:15
<alkisg>
np
11:15
pedro__: if you put the .crt file on the server, and restart the server, then you can copy it to the other clients by just running `epoptes-client -c`
11:19
<pedro__>
Thanks
11:28GodFather has joined IRC (GodFather!~rcc@96-92-43-9-static.hfc.comcastbusiness.net)
11:28pedro__ has left IRC (pedro__!d5005718@gateway/web/freenode/ip.213.0.87.24, Ping timeout: 260 seconds)
11:40pedro__ has joined IRC (pedro__!d5005702@gateway/web/freenode/ip.213.0.87.2)
11:42
<pedro__>
It worked!
11:42
Thank you
11:45
<alkisg>
You're welcome :)
11:46
<pedro__>
Now I can see all the computer except one. It has got the same certificate but it doesn't appear
11:48
<alkisg>
Check its bios date, if it's wrong, then the certificate is invalid
11:48
If so, replace the cmos battery
11:48
<pedro__>
I'm going to check it
11:49* alkisg needs to leave, ciao for now...
11:51
<pedro__>
Goodbye and thanks again
12:01adrianor1 has joined IRC (adrianor1!~adrianorg@177.18.97.238)
12:04adrianorg has left IRC (adrianorg!~adrianorg@189.114.158.195, Ping timeout: 248 seconds)
12:40adrianor1 is now known as adrianorg
13:05pedro__ has left IRC (pedro__!d5005702@gateway/web/freenode/ip.213.0.87.2, Quit: Page closed)
14:18lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
14:47ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
15:59vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
16:32neops has left IRC (neops!5ee4bfca@gateway/web/freenode/ip.94.228.191.202, Quit: Page closed)
16:39GodFather has left IRC (GodFather!~rcc@96-92-43-9-static.hfc.comcastbusiness.net, Ping timeout: 240 seconds)
17:01lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Remote host closed the connection)
17:01Da-Geek has joined IRC (Da-Geek!~Da-Geek@88.98.221.152)
17:33Freejack has left IRC (Freejack!~quassel@unaffiliated/freejack, Ping timeout: 248 seconds)
17:34Freejack_ has joined IRC (Freejack_!~quassel@unaffiliated/freejack)
17:58Statler has left IRC (Statler!~Georg@gwrz3.lohn24.de, Remote host closed the connection)
18:11ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
18:46JuJUBee has joined IRC (JuJUBee!~knichel@24.148.115.153)
18:47
<JuJUBee>
My students pointed out today that the clocks on my fat clients are wrong. They are displaying GMT I think (5 hours off from EST)
18:52
<vagrantc>
i've heard this reported a few times recently...
18:52
distro, release, ltsp version?
18:52
!ltsp-info
18:52
<ltsp>
ltsp-info: please run ltsp-info and paste the output to http://ltsp.pastebin.com
18:54
<JuJUBee>
vagrantc, Running ubuntu 16.04 https://pastebin.com/ad7tFTLR
18:55
<vagrantc>
looks like you have both an amd64.img and fat-amd64.img ... do you know which is actually being used?
18:57
<JuJUBee>
Pretty sure only the amd64
18:58
<vagrantc>
JuJUBee: using a client chroot? ...
18:58
<JuJUBee>
I don't have /opt/ltsp/fat-amd64 dir
18:58
<vagrantc>
JuJUBee: check the contents of /opt/ltsp/amd64/etc/timezone
18:58
JuJUBee: ls -l /opt/ltsp/amd64/etc/timezone
18:58
<JuJUBee>
Etc/UTC
18:59
<vagrantc>
that would most likely explain it
18:59
is it a symlink or a regular file?
18:59
<JuJUBee>
regular file
19:00
<vagrantc>
check the contents of the server's /etc/timezone, and if it's what you want, you should be able to copy it into the chroot and rebuild the image
19:00
that *should* work
19:00
why it isn't doing that out of the box is a bit mysterious
19:01
is the server's /etc/timezone a symlink?
19:01
<JuJUBee>
no
19:02
This seems to have happened recently, maybe around time change...
19:02
I'll change it and rebuild the image
19:02
thanks vagrantc
19:02
<vagrantc>
hmmm... there's a subtle difference in the ubuntu and debian timezone configuration for ltsp-build-client ... that might be the issue
19:03
JuJUBee: did you rebuild the image around then?
19:03
<JuJUBee>
no, not since late September
19:03
<vagrantc>
well, the image wouldn't switch timezone without rebuilding it
19:03
<JuJUBee>
I rebuilt it Tuesday to see if that would fix it, but it did not
19:04
<vagrantc>
ah, simpler option: set TIMEZONE= in lts.conf
19:05
hrm... that might be broken
19:05
well, it's worth trying...
19:06
<JuJUBee>
it must be broken I already had that set
19:07
<vagrantc>
JuJUBee: ls -l /opt/ltsp/amd64/etc/localtime and /etc/localtime
19:07
er, drop the "and" :)
19:07* vagrantc half-thinking in shell and half in prose
19:08
<JuJUBee>
lrwxrwxrwx 1 root root 27 Feb 6 2017 /opt/ltsp/amd64/etc/localtime -> /usr/share/zoneinfo/Etc/UTC
19:10
<vagrantc>
hmmm... that might break the way TIMEZONE is implemented, not sure
19:10
<JuJUBee>
Question is why is that pointing to Etc/UTC and not America/New_York
19:11
<vagrantc>
because the code that generates the chroot doesn't touch that file
19:11* vagrantc suspects the timezone handling in ubuntu changed in some release and the ltsp-build-client plugins never got updated to reflect that
19:12
<JuJUBee>
so should I re-create the link to localtime?
19:12
<vagrantc>
ltsp-build-client hasn't really been well maintained ... mostly switched to using ltsp-pnp style in recent times
19:12
<JuJUBee>
what is the main advantage of using pnp for me?
19:13
<vagrantc>
JuJUBee: if you could file a bug in launchpad, that would mean the issue doesn't get lost
19:13
JuJUBee: people are actually testing the code path?
19:14
JuJUBee: also, looks like you at least experimented with fat clients at some point, and this is easier to maintain with ltsp-pnp
19:14
<JuJUBee>
Should I note that the symlink points to the wrong timezone?
19:14
I use fat clients
19:14
I think I copied the old amd64 image to fat-amd64 as a backup at one point
19:14
<vagrantc>
basically, you just install the server with the software you want, and then build an image out of that
19:15
<JuJUBee>
But only have fat clients for now.
19:15
<vagrantc>
no separate chroot to maintain
19:15
<JuJUBee>
the thought of starting over from scratch worries me as the school year is well underway.
19:15
<vagrantc>
indeed
19:15
JuJUBee: have you upgraded the chroot ever?
19:15
<JuJUBee>
yes
19:16
I stick with lts releases only
19:17
<vagrantc>
JuJUBee: in the bug report, include the ls -l /etc/timezone /etc/localtime /opt/ltsp/amd64/etc/timezone /opt/ltsp/amd64/etc/localtime, your lts.conf (sanitized, if you need to), the ltsp-info output
19:17
JuJUBee: and also the contents of /etc/timezone and /opt/ltsp/amd64/etc/timezone
19:17
<JuJUBee>
OK, working on it now...
19:18
<vagrantc>
might also be worth checking if such a bug report already exists
19:18
https://bugs.launchpad.net/ltsp/+bug/1596448
19:18
following up to that might be good
19:19
https://bugs.launchpad.net/ltsp/+bug/1660392
19:19
<JuJUBee>
do you want me to submit the ls -l for each of those initial dirs or only the first and contents of the rest?
19:19
<vagrantc>
and/or that one
19:21
actually, the latter bug looks more appropriate
19:22
and that would also affect using TIMEZONE in lts.conf ...
19:22
which wouldn't matter weather you're using ltsp-pnp or a chroot
19:28
<JuJUBee>
Done, I commented on second bug
19:32
SO I edited the incorrect timezone file to America/New_York and after rebuilding the image and rebooting client the time seems correct
19:32
We will see what happens Monday morning...
19:32
Thanks for the assistance
19:33
Gotta go...
19:33JuJUBee has left IRC (JuJUBee!~knichel@24.148.115.153, Quit: Leaving)
20:02
<JerryT>
Any reason why a ltsp fatclient can't access the libraries?
20:02
Or open a socket bind()???
20:02
Thinclients have no issues with either.
20:04
<||cw>
JerryT: what libraries?
20:04
<JerryT>
./usr/lib
20:05
Really any of them. The application looks in several locations and has an issue finding them. They're on the Host machine, and the image was rebuilt.
20:05
<||cw>
and they made it into the image?
20:06
if the client boots to a desktop, it's accessing /usr/lib just fine
20:07
<vagrantc>
JerryT: is /usr on a separate partition?
20:07
<JerryT>
Yah, I'm not sure what the issue is. Maybe LD_LIBRARIES or something is flaky. I'm not sure.
20:08
vagrantc, no, everything resides on /dev/sda1
20:14
<vagrantc>
network flakiness?
20:14
seems more likly than LD_LIBRARIES going wonky
20:15
though that should usually crash a client
20:18Da-Geek has left IRC (Da-Geek!~Da-Geek@88.98.221.152, Quit: Leaving)
20:19GodFather has joined IRC (GodFather!~rcc@47.33.250.142)
20:35quinox1 has left IRC (quinox1!~quinox@ghost.qtea.nl, Remote host closed the connection)
20:46
<alkisg>
JerryT: what is the command that you run and the error message that you see? put them to pastebin...
20:57
<JerryT>
SSH_FOLLOW_SYMLINKS=False
20:58
What's that do exactly?
20:58
Or what's it's affect on systems?
21:09
<alkisg>
Answer mine first :P
21:09
It doesn't affect the nbd image
21:09
/usr, /lib etc are accessed via nbd, not ssh
21:10
It allows /home/user/folder symlink to follow the contents to /some/server/dir
21:18quinox has joined IRC (quinox!~quinox@ghost.qtea.nl)
21:20lucascastro has joined IRC (lucascastro!~lucas@189.89.0.136)
21:28kjackal has left IRC (kjackal!~quassel@2a02:587:3114:a000:8827:89cc:f506:13, Ping timeout: 258 seconds)
21:32
<alkisg>
(follow them from the client to the server)
21:55lucascastro has left IRC (lucascastro!~lucas@189.89.0.136, Remote host closed the connection)
22:25lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
22:29GodFather has left IRC (GodFather!~rcc@47.33.250.142, Ping timeout: 240 seconds)
22:30GodFather has joined IRC (GodFather!~rcc@47.33.250.142)
22:31lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Remote host closed the connection)
23:12ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection)
23:44lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)