LTSP 5 is in minimal maintenance mode
The new LTSP is hosted at https://ltsp.github.io

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


Channel log from 7 January 2019   (all times are UTC)

00:39markit has left IRC (markit!~marco@78-134-15-138.v4.ngi.it, )
01:48vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
02:00vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
06:57vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
07:42ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
08:22kjackal has joined IRC (kjackal!~quassel@62.103.222.236)
11:34kjackal has left IRC (kjackal!~quassel@62.103.222.236, Ping timeout: 250 seconds)
11:34kjackal has joined IRC (kjackal!~quassel@62.103.222.236)
13:39spaced0ut has joined IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut)
13:48
<mwalters>
aside from some (non-ltsp related) hiccups. All my 14.04 servers are gone, and I now have 4 18.04 ltsp servers. The LTSP part of all this went very smooth. Thanks for all your hardwork into this project everyone.
14:45GodFather has joined IRC (GodFather!~rcc@2600:1011:b123:50d6:95d3:6e04:4912:c01f)
15:35
<alkisg>
You're welcome :)
15:55mmarconm has joined IRC (mmarconm!~mmarconm@unaffiliated/mmarconm)
16:48mmarconm has left IRC (mmarconm!~mmarconm@unaffiliated/mmarconm, Quit: Konversation terminated!)
17:18
<mwalters>
Can I adjust the fstab file in my chroot to mount extra stuff from the ltsp server?
17:19
e.g., I have a /public dir that has some scripts that "everyone" might use
17:19
I guess I could just move them to the chroot
17:20
/thinking out loud ;)
17:31GodFather has left IRC (GodFather!~rcc@2600:1011:b123:50d6:95d3:6e04:4912:c01f, Ping timeout: 252 seconds)
17:45vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
17:52
<alkisg>
mwalters: FSTAB_xxx="line" in lts.conf
17:52
Or, LTSP_EXTRAMOUNTS="/public"
17:52
Don't forget to also exclude /public in /etc/ltsp/ltsp-update-images.excludes
17:54
<mwalters>
nice, thanks! I've also had a couple fat clients hard-freeze today (can't move mouse or anything)... Any common issues there?
17:54
e.g., "Oh, that's usually ____" ?
17:56
<alkisg>
"Oh, that's usually __network or graphics drivers__"
17:56
<mwalters>
First through was network issue with one of them... old buildings, questionable cabling... but then had an issue with a client in another building (same server, fiber backhaul)
17:56
<alkisg>
Or out of ram, if they have little ram
17:56
<mwalters>
yeah, that's what I thought... time to go down the rabbit hole
17:56
p sure both of the frozen clients have 4gb
17:57
of memory
17:57
yah
17:58
<alkisg>
4 GB is fine for casual use; but it can still cause OOM if you have firefox + thunderbird + libreoffice + gimp open...
17:58
So just run `top` when they're in the middle of their work
17:58
<mwalters>
most clients are basically just chrome
17:58
...which is probably the equiv to all of those things ;)
17:59
<alkisg>
Chrome with 30 tabs can do that too :)
18:00
<mwalters>
maybe I can set up a script to grab vmstat output every so often if it becomes a consistent thing
18:26spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Ping timeout: 252 seconds)
18:26spaced0ut has joined IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut)
18:31spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Remote host closed the connection)
18:32
<alkisg>
mwalters: if you can, file a bug against ltsp, so that it sets LDM to be killed first on OOM. This will at ensure no hangs; just xorg crashes, which can at least notify the sysadmin about OOM issues.
18:32
!ltsp-bug
18:32
<ltsp>
ltsp-bug: To file a bug report for upstream LTSP, go to https://bugs.launchpad.net/ltsp
18:32
<mwalters>
That'd be helpful, I'll do that!
18:35mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Quit: Leaving)
18:35
<alkisg>
In your local installation, you could run chrome with the highest oom score, so that it's killed first, and xorg / session survive
18:38spaced0ut has joined IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut)
18:58
<mwalters>
I suspected that's what was happening on our old thin client set up, but nothing ever made it to syslog
18:58
on the client or the server (we were using ltsp-localapps w/ chrome)
18:59
it really seemed to happen at random, though... sometimes you could go days, othertimes you couldn't even log into gapps with a single tab
19:29
<alkisg>
To see things in server syslog, you'd need to set up remote syslogging in lts.conf
19:30
"The Ethernet Alliance’s new roadmap traces Ethernet’s path from 10 Mb/s through present-day speeds of 1 to 400 gigabit Ethernet (GbE), and looks ahead to future speeds achieving up to 1.6 terabits (TbE) and beyond."
19:31
1 tbps would make thin clients feasible again :P
19:31
<mwalters>
lol
20:04kjackal has left IRC (kjackal!~quassel@62.103.222.236, Ping timeout: 258 seconds)
20:19
<mwalters>
alksig: didn't the old thin client setup use NBD swap?
20:19
alkisg, rather
20:20
<alkisg>
mwalters: all ltsp clients should use nbd swap by default for the last 10 years or so...
20:21
But at some point it defaulted to just 64mb, which was too low
20:21
<mwalters>
Just checked the manual, looks like it's off for fat clients w/ more than 800MB
20:21
<alkisg>
I increased it to 512, but I don't remember well
20:21
That's true
20:22
if boolean_is_true "$LTSP_FATCLIENT"; then NBD_SWAP_THRESHOLD=2100
20:22
else NBD_SWAP_THRESHOLD=800 fi
20:22
Fat clients with more than 2100 don't get swap
20:22
And thin clients with more than 80
20:22
*800
20:23
<mwalters>
Is there any server side config if I were to explicitly enable it?
20:23
(other than modifying lts.conf)
20:24
<alkisg>
The size can be configured in /etc/ltsp/nbdswapd.conf
20:25
Otherwise, it's on by default, with 512 mb swaps
20:25
To force all clients to use swap, NBD_SWAP=True in lts.conf
20:26
<mwalters>
specify SWAPDIR and SIZE (in megabytes?) in nbdswapd.conf?
20:27
<quinox>
(I decided to disable swap-over-network entirely and buy more RAM when clients crash)
20:27
<alkisg>
Just SIZE, no reason to set SWAPDIR
20:27
<mwalters>
That would be ideal, for sure ;)
20:27
but I feel like I'm playing whack-a-mole right now ;)
20:27
<alkisg>
But if you're doing all this to avoid client crashes without investigating first... you're following a bad approach
20:28
<mwalters>
Yeah, I get what you're saying there
20:45
<vagrantc>
also, since encrypted nbd swap is broken, there was at least a window of time where i had NBD swap disabled in Debian ...
20:49
<mwalters>
What you're saying is that any client could potentially peer into swap used by another client?
20:59
<vagrantc>
anyone on the network who can spoof the ip address of a client
20:59
or anyone on the server able to read the swap files
21:07
<alkisg>
They're owned by nbd though, right? So only root could read them on the server
21:08
<vagrantc>
right
21:09
or, at least, shoudl be
21:09
<alkisg>
Actually, they're deleted upon creation, so nah, they're not even accessible by root, unless he does very fancy things
21:10
And the "fake ip" nbd-client wouldn't be able to set up a new nbd connection, as the file isn't there
21:11
It would need to fake the "previous client" as well; I don't know if that's possible; it depends on the nbd internal state
21:18
<vagrantc>
ah right, we finally managed to remove the file, so yeah ... it's a lot harder
21:19
for some years the files just sat there and re-used connections from old ip addresses
21:19
er, reused files from old ip addresses
21:19
<alkisg>
Yeah I think I changed that 3-4 years ago
21:19
Server space was the initial problem; but the deletion had good side effects :)
21:19
<vagrantc>
heh
21:21* alkisg => pumpkin
22:14ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)
23:34
<mwalters>
thanks for thinking all that through for me ;)