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 5 November 2019   (all times are UTC)

01:41R4F4EL has left IRC (R4F4EL!b1149819@177.20.152.25, Ping timeout: 260 seconds)
02:12robert45 has left IRC (robert45!~robert45@r179-24-26-9.dialup.adsl.anteldata.net.uy, )
02:42eu^c-24-19-187-1 has joined IRC (eu^c-24-19-187-1!1813bbb6@c-24-19-187-182.hsd1.wa.comcast.net)
02:46
<eu^c-24-19-187-1>
hey guys .. noob to LTSP here .. I have a setup "at home" and I copied it to somebody "remote" but he gets this error
02:46
NBP filename is ltsp/snponly.efifilesize is 0 bytes
02:47
the file is there and size is ok
02:47
any idea why this would happen?
02:47
the "server" is a hyperv
04:04
<quinox>
https://sourceforge.net/p/nbd/mailman/message/31803583/ "How to test NBD"
04:24
<alkisg>
Morning all
04:25
NBD isn't NBP... eu^c-24-19-187-1, does the client have a hard disk, to put ipxe in it? Or a floppy/cdrom?
04:25
https://ltsp.github.io/docs/netboot-clients/
04:28
Or he could try a BIOS/UEFI firmware update
04:32
Finally, he could overwrite snponly.efi with https://boot.ipxe.org/ipxe.efi, but I think that this ^ issue is before ipxe gets loaded...
04:33
Oh and of course he could just switch to BIOS legacy netbooting from the UEFI options
04:33
<quinox>
ooh I thought it was a typo, searching for "NBP" I only get bank sites. "NBP boot" gives me more relevant results
04:34
<eu^c-24-19-187-1>
it's uefi, PXE booting; has HDD but not in the boot chain
04:34
<alkisg>
Network boot ... protocol? I dont remember the last part
04:34
<eu^c-24-19-187-1>
iPXE / tftp
04:34
<alkisg>
eu^c-24-19-187-1: yeah, these are the options
04:35
Putting ipxe in the hard disk and the boot order would probably work
04:35
<eu^c-24-19-187-1>
thanks .. it's 22:30 here, I'll try again in the am .. cheers!
04:36
<alkisg>
We don't know too much about UEFI firmware bugs yet, as it was just implemented in LTSP this summer
04:36
Cheers
05:29kjackal has joined IRC (kjackal!~quassel@2a02:587:3107:2e00:4854:7acc:13a8:95cb)
05:35os_a has joined IRC (os_a!~Thunderbi@195.112.116.22)
05:58statler has joined IRC (statler!~Georg@p5B30EE2F.dip0.t-ipconnect.de)
06:09
<alkisg>
vagrantc: ah we'll also need Raspbian's "bootcode.bin" in ltsp-binaries, to be able to netboot raspberries. I think this one can't even be compiled from source at all
06:10
Never mind we might be able to get that from the chroot
06:20kjackal has left IRC (kjackal!~quassel@2a02:587:3107:2e00:4854:7acc:13a8:95cb, Ping timeout: 276 seconds)
07:31ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:36
<vagrantc>
alkisg: indeed.
07:43vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
07:47statler has left IRC (statler!~Georg@p5B30EE2F.dip0.t-ipconnect.de, Quit: Leaving)
08:04eu^c-24-19-187-1 has left IRC (eu^c-24-19-187-1!1813bbb6@c-24-19-187-182.hsd1.wa.comcast.net, Ping timeout: 260 seconds)
08:07kjackal has joined IRC (kjackal!~quassel@2a02:587:3107:2e00:4854:7acc:13a8:95cb)
08:24
<alkisg>
LTSP binaries have been downloaded 480 times so far... not bad for a such new release :) https://www.somsubhra.com/github-release-stats/?username=ltsp&repository=binaries
08:25
<eu^37-247-30-164>
woop woop
08:25
working on the client template now
08:25
will see what I can manage to get working :)
08:25
<alkisg>
eu^37-247-30-164: try this: /nick your-user-name
08:26
It's much friendlier than "eu^number"
08:26eu^37-247-30-164 is now known as enoch85
08:26
<enoch85>
hej
08:26
:)
08:26
<alkisg>
;)
08:26
<enoch85>
btw, ping Ark74 didn't expect to see you here :)
08:29
btw alkisg, would this work you think: https://pastebin.com/NiznCVu8
08:29
<alkisg>
enoch85: don't set MAC_ADDRESS it's already set by the ltsp code
08:29
<enoch85>
I tried "echo $MAC_ADDRESS" but there doesn't seem to be a built in $var for that
08:29
aaaah
08:29
nice
08:31
and to modify the guest account I guess I change the stuff in /home/guest (like RDP shortcuts and stuff)?
08:31
<alkisg>
Right, you login as guest on the server and modify things in your /home/guest account
08:31
<enoch85>
perfect
08:31
no need for sudo ltsp nfs --nfs-home=1 ?
08:32
<alkisg>
No, because of the local.conf file that I mentioned, that only exports /home/nfs
08:32
Hmm
08:32
Wait you also need to export /home as read only
08:32
So ok yeah, run ltsp nfs --nfs-home=1
08:32
Let me see what I wrote in issues...
08:32
<enoch85>
I just copied and pasted your stuff here: https://github.com/ltsp/community/issues/47#issuecomment-549017534
08:32
haven't given it a try yet
08:33
<alkisg>
OK
08:33
Either those, or --nfs-home=1
08:33
Not both
08:33
<enoch85>
ok
08:33
I'll make an image now
08:33
let's see
08:33
<alkisg>
I guess what I wrote in the issue is a bit harder, but more secure, as it doesn't expose /home/administrator over nfs
08:34
<enoch85>
yeah, and that's exactly what we want
08:34
if this works I'm super stoked!
08:35
but this: "And on each login, you can run the rsync command that @Dur0k mentions in his wiki page." is that done on the thin client connecting to ltsp or is that set in the server somehow?
08:35
<alkisg>
This is done on the client
08:36
From the session script
08:36
Read the wiki page that Dur0k wrote
08:36
It's already documented there
08:36
<enoch85>
ok
08:36
thanks
08:56statler has joined IRC (statler!~Georg@gwrz.lohn24.de)
08:59Da-Geek has joined IRC (Da-Geek!~Da-Geek@5.154.189.38)
09:02
<enoch85>
alkisg sorry for my ignorance, but the paths should be different from the wiki, right? I mean we rsync from /home/guest (and put everything there) and not /etc/ltsp/template? https://github.com/ltsp/community/wiki/Guest-session#create-the-guest-session
09:03
<alkisg>
enoch85: right, as we're using NFS to share the template and not `ltsp initrd`
09:03
Putting things to NFS allows them to become larger without affecting the boot times
09:04
<enoch85>
so the script should be: rsync -rtvp /home/guest /home/nfs/$MAC_ADRESS ?
09:05
<alkisg>
No, rsync /etc/guest-template /home/guest
09:05
With the appropriate options
09:05
(--delete should also be needed)
09:06
The server /home/guest is /etc/guest-template on the client. That's the rsync source.
09:06
The server /home/nfs/mac/home/guest is /home/guest on the client. That's the rsync destination.
09:11
<enoch85>
what I would like is to make changes on the server, that are sent to the clients using ltsp, shouldn't it be the other way around? Sorry, trying to wrap my tiny head around this :)
09:12
<alkisg>
This is exactly what I described, from server to clients
09:12
<enoch85>
ok
09:12
will try :)
09:12
<alkisg>
You don't even have to reboot clients for the changes to take effect
09:12
<enoch85>
awesome!
09:13
and adding this POST_INIT_link="ln -s /etc/ltsp/guest.desktop /usr/share/xsessions/guest.desktop" to ltsp.conf is still needed I guess?
09:14
<alkisg>
Yes
09:14
<enoch85>
ok, thanks
09:14
<alkisg>
np
09:24
<meo>
alkisg: /snap/bin is missing, is that normal
09:24
<alkisg>
meo: is it there on the server but not on the client?
09:25* alkisg isn't using snaps, and only tested them for a bit
09:53woernie has joined IRC (woernie!~werner@p50867A20.dip0.t-ipconnect.de)
09:58nikoh77 has joined IRC (nikoh77!~nikoh77@93-55-122-94.ip263.fastwebnet.it)
09:58
<meo>
alkisg: aye, it looks like /snap/xxx mounts exist for individual package
09:59
<enoch85>
hey, been trying to get the guest session to work, but I fail...
09:59
https://pastebin.com/fQd9MVxC
09:59
1. It doesn't autologin to guest
09:59
2.
09:59
<meo>
alkisg: I actually dont _need_ /snap/bin because I can run the binary from /snap/xxx but there's another problem with it that probably has to do with snap itself that I'm trying to figure out
09:59
<enoch85>
2. It doesn't find the setupsession.sh
10:00
<meo>
alkisg: also, do you accept pizza/beer money
10:00
<enoch85>
https://cloud.danielhansson.nu/f/378513
10:01
sorry, wrong link: https://cloud.danielhansson.nu/s/LnoBj3fMyWLkPYA
10:01
I did chmod +x on setupsession.sh, but still same error
10:02
when I boot the thin client I'm presented with three users: administrator | guest | guest-session
10:02
<alkisg>
meo: sure, thanks, at paypal alkisg@gmail.com. Can I help over vnc?
10:02
!vnc-dide
10:02
<ltsp>
vnc-dide: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect srv1-dide.ioa.sch.gr - this is a reverse connection, it doesn't need port forwarding etc.
10:02
<meo>
alkisg: probably not, the setup is on another floor behind pfsense in a closet
10:02
but maybe I'll ask later
10:03
<alkisg>
Sure, also ping me if you want me to test snaps locally
10:03
enoch85: try vnc:
10:03
!vnc-edide
10:03
<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
10:04
<meo>
alkisg: money out
10:04
thanks for help!
10:04
<alkisg>
Thank you too :)
10:06
<meo>
hmm actually when I run the binary directly on the client it complains about being unable to create /.config folder
10:06
something wrong with paths
10:06
I need to rtfm
10:07* alkisg fires up a VM to test...
10:08
<meo>
the package in question is flock-chat
10:09
<alkisg>
Haha funny I did `snap install hello-world` and xubuntu said "the cd was mounted succesfully"
10:10
Hello world ran fine, testing flock-chat...
10:10
Ah needs amd64, changing vm...
10:11
<meo>
do bear in mind I upgraded ltsp from the version that didnt have snaps working (october or so)
10:11
<alkisg>
You did run `ltsp initrd` since, right?
10:11
<meo>
I regenerated image and initrd after the upgrade but nothing else
10:11
<alkisg>
OK image wasn't needed
10:11nikoh77 has left IRC (nikoh77!~nikoh77@93-55-122-94.ip263.fastwebnet.it)
10:13
<alkisg>
I do have /snap/bin
10:13
<enoch85>
alkisg, strange, now I can't start epotes https://imgur.com/a/vMP33eO even though it is installed
10:13
I'll go for lunch now
10:14
<alkisg>
enoch85: sudo systemctl restart epoptes
10:14
<enoch85>
too easy!
10:15
now it's working
10:15
<meo>
alkisg: I don't, on ppa version from 2nd Nov
10:15
<alkisg>
meo: 18.04?
10:15
<enoch85>
I'll be back in a bit, need some fooood
10:15
<meo>
alkisg: .3, LTS
10:15
<alkisg>
OK, same here
10:15
<meo>
alkisg: maybe something carried over in config from the old version?
10:15
<alkisg>
The snap part wasn't adjustable by configs, so that sounds strange
10:16
Do you see denied messages from apparmor in `journalctl -fe` ?
10:16
if you try to run snaps...
10:16
<meo>
the user is unprivileged, I dunno
10:16
tell you what
10:17
I'll go there and look
10:17
<alkisg>
Eeeh "go there"... use remote desktop :P
10:17
<meo>
can't, separate network
10:18
havent set up S2S VPN or anything
10:18
<enoch85>
alkisg sent you some cash, hope it's enough
10:18* alkisg uses reverse connections to avoid the need for port forwarding, forward connections etc
10:18
<enoch85>
will be back after lunch
10:18
<alkisg>
enoch85: thank you, see you then
10:19
meo, for me, snaps run, but I'm getting this issue in this test: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552
10:19
I'm using NFS home and they take a long time to load
10:20
I guess ltsp could apply the workaround mentioned in that bug report
10:20
<meo>
ill try the 'classic' snap mode
10:20
<alkisg>
meo: flock ran fine too, after taking a while to load because of nfs
10:20
(home)
10:21* alkisg checks with sshfs...
10:21
<meo>
nope, fails to start, as it tries to create /.stuff
10:21
<alkisg>
Is this a "per user" snap, or a system one?
10:21
<meo>
it's either not picking up the location of ~ or not actually executes in a container
10:21
<alkisg>
I installed flock chat with sudo snap install flock-chat
10:21
<meo>
system one installed on the server
10:21
same
10:22
<alkisg>
I installed it on the client as I was testing from a VM, but the other ones that were preinstalled also worked
10:27
<meo>
think rebooting the server would help?
10:27
<alkisg>
I can't imagine why. Let me test with sshfs...
10:28
Oh, much faster
10:29
The snap launcher has a bug, it doesn't like the fact that "Desktop" in Greek is "Επιφάνεια εργασίας" with a space there, but other than that, it runs fine and very fast
10:32kjackal has left IRC (kjackal!~quassel@2a02:587:3107:2e00:4854:7acc:13a8:95cb, Remote host closed the connection)
10:40meo2 has joined IRC (meo2!~administr@94.155.133.5)
10:40
<meo2>
alkisg: reinstalled the snap, regenerated initrd, nada
10:41
wanna take a look?
10:41
<alkisg>
Sure
10:41
<meo2>
!vide
10:41
<ltsp>
I do not know about 'vide', but I do know about these similar topics: 'video-without-flash', 'video-test'
10:41
<alkisg>
!vnc-dide
10:41
<ltsp>
vnc-dide: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect srv1-dide.ioa.sch.gr - this is a reverse connection, it doesn't need port forwarding etc.
10:41
<alkisg>
or:
10:41
!vnc-edide
10:41
<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
10:43kjackal has joined IRC (kjackal!~quassel@2a02:587:3107:2e00:4df2:7425:ba6f:da10)
10:53
<alkisg>
meo2, I'm using VMs, so I'm not running ltsp image, so I'm not excluding snap/*
10:55
So...
10:55
<meo2>
i see what you did there
10:55
<alkisg>
I think that /snap should NOT be excluded
10:55
<meo2>
ill refresh to edge version
10:55
<alkisg>
No no no
10:55
<meo2>
and /snap/bin shouldnt be excluded
10:55
<alkisg>
All those refreshes and installations were not needed
10:55
<meo2>
but the rest are mount points
10:56
<alkisg>
After this ltsp image, everything should work
10:56
Without edge channels nor snap installations
10:56
snap seems to also need the dirs there, the mount points
10:56
<meo2>
but then the image would export /snap/packagename too no?
10:56
<alkisg>
Now, ltsp image doesn't propagate to mounts anyway
10:56
So the contents won't be included
10:56
<meo2>
aha, lets try it
10:56
<alkisg>
Right
10:56
<meo2>
ill reboot the client soon as image finishes
10:56
<alkisg>
Exactly
10:57
And if everything works, then the fix is to just remove a line from image.excludes
10:57
<meo2>
actually its the most important time of the day
10:57
lunch
10:57
<alkisg>
I didn't notice it because I wasn't running `ltsp image`
10:57
<meo2>
thanks for your help
10:57
<alkisg>
Haha
10:57
OK, thank you too
10:57
<meo2>
ill let you know how it worked out
10:57
<alkisg>
(closed VNC)
10:57
<meo2>
but didnt /snap/bin only appear on the client once you upgraded both snap core and flock to edge versions?\
10:59
<alkisg>
Yes, snap install creates /snap/bin
10:59
So reinstalling, make some things work
10:59
But now that `ltsp image` won't exclude /snap, it'll already be there
11:02
<meo2>
alkisg: confirmed the solution works
11:02
all good
11:02
customer happ
11:02
..y.
11:02
<alkisg>
Great
11:02
<meo2>
food time!
11:02meo2 has left IRC (meo2!~administr@94.155.133.5, Quit: leaving)
11:05
<alkisg>
meo: when you come back and if the food was good, file an issue about it so that I can close it with the commit; it's good to keep users notified...
11:05
<meo>
ill do it now
11:05* alkisg is off to lunch to, will commit afterwards :)
11:07
<meo>
https://github.com/ltsp/ltsp/issues/63
11:21
<enoch85>
alkisg, I'm back from lunch, fyi
11:26woernie has left IRC (woernie!~werner@p50867A20.dip0.t-ipconnect.de, Remote host closed the connection)
11:36
<enoch85>
another strange issue, when hitting "Shutdown" in Ubuntu (when on the login screen for Ubuntu) on the thin client it shuts down, and then won't boot again. I have to take a new thin client to test with
12:03Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
12:07section1 has joined IRC (section1!~section1@178.33.109.106)
12:14woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de)
12:14
<meo>
what do you mean wont boot
12:14
what happens when you power it on?
12:25
<enoch85>
meo nothiong
12:25
the screen won't even turn on
12:25
getting a new thin client and power it on works though
12:28
<meo>
that.. sounds like a hardware problem
12:28
if you unplug the power, wait 30 sec and plug it back, will it turn on?
12:28
you may want to update the bios
12:34
<enoch85>
meo, problem is this https://support.hp.com/us-en/document/c01926343
12:34
very old hardware
12:35
it's been the same way with the latest 3 clients I've been using
12:36meo has left IRC (meo!~systemdju@unaffiliated/mikeseth, Quit: leaving)
12:57
<alkisg>
enoch85: how many clients like that do you have?
12:57
<enoch85>
we have like 200 clients, but now I'm only testing
12:58
I "wasted" three clients - in other words, they are not booting anymore
12:58
<alkisg>
Then I think it would make sense to install 18.04, which is the last one that supports 32bit, and install the old kernel there
12:58
When they're not booting, try to unplug their power, then press their power button so that the current goes away from capasitors etc, then plug it to power again
12:59
<enoch85>
sorrryyyyyy, now it worked
12:59
had it out of AC for 20 mionutes
12:59
brb phone
12:59
<alkisg>
It only needs 5 secs for what I wrote above ^
13:02
!vnc-edide | echo enoch85:
13:02
<ltsp>
enoch85: 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
13:03
<alkisg>
or:
13:03
!vnc-dide
13:03
<ltsp>
vnc-dide: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect srv1-dide.ioa.sch.gr - this is a reverse connection, it doesn't need port forwarding etc.
13:03
<enoch85>
https://imgur.com/a/WqdMWnd
13:04
<alkisg>
enoch85: try from terminal, x11vnc -connect srv1-dide.ioa.sch.gr
13:05
Or if you have dns issues: x11vnc -connect 81.186.20.0
13:07
<enoch85>
trying now
13:08
nothing, it just sits there
13:08
Do I need to open any ports?
13:08
<alkisg>
No
13:09
Can you ping that ip?
13:09
Well, outgoing 5500, if you have that harsh firewall..
13:09
<enoch85>
yeah I can ping it
13:10
outgoing shouldn't be needed
13:10
https://imgur.com/a/WqdMWnd
13:10
<alkisg>
I restarted my vnc listener in case it hanged (it never did so far)
13:10
Give it another try
13:11
Ah
13:11
Are you trying this from a thin client?
13:11
If so, add -noshm: x11vnc -noshm -connect 81.186.20.0
13:11
<enoch85>
I'm trying from the server
13:11
VMware console
13:12
<alkisg>
Very strange
13:12
I'm not even getting any notification that you're trying to connect
13:12* enoch85 checking firewall
13:13
<enoch85>
pf: 192.168.2.6.34226 > 81.186.20.0.5500: Flags [S], cksum 0xebaa (correct), seq 2843227313, win 29200, options [mss 1460,sackOK,TS val 2020134939 ecr 0,nop,wscale 7], length 0
13:13
<alkisg>
Try to stop firewall for a few seconds, and see if it can connect without it
13:26
enoch85: for some reason, network manager doesn't want to put DNS to resolvconf...
13:26
Let me check a 16.04 VM
13:27
<enoch85>
okok
13:28
<alkisg>
enoch85: do you remember changing anything in network manager or resolvconf?
13:29
<enoch85>
nope
13:29
or sec
13:29
I'll double check
13:29
no nothing changed
13:30
it should get dns from the firewall, which worked if I did what I did in the conf file
13:34
<alkisg>
enoch85: boot a client
13:34
<enoch85>
without making a new image?
13:35
<alkisg>
enoch85: yes
13:35
Changes in /etc/ltsp don't need a new image
13:35
Just ltsp initrd
13:35
<enoch85>
aah ok
13:35
will do now
13:35
but when I reboot the server the old DNS will be back right?
13:36
<alkisg>
No idea
13:36
<enoch85>
I think so
13:36
Will see
13:36
<alkisg>
In 14.04 and 16.04, Ubuntu was experimenting with dns, and broke dnsmasq
13:36
In ltsp5 I put some workarounds, but I'm not sure why they didn't work for you now
13:38
Regarding .0 at the end of the file names, I think it's just your client that's broken; just use a symlink there like the ones I created
13:38
If anyone else reports it too, we'll rethink about it
13:38
Also if you can update their BIOSes, it might help
13:38
<enoch85>
alkisg sorry, I won't upgrade BIOS on 200 clients :)
13:38
<alkisg>
np
13:38
It may make the power issue go away too
13:39
<enoch85>
symlink seems like a OK workaround
13:39
<alkisg>
But I get your point :)
13:39
<enoch85>
I'll send a video soon
13:39
sec
13:39
<alkisg>
You may also use a VM client while testing
13:39
So that things go faster
13:40
<enoch85>
good point
13:41
so LTSP needs lo to function? (dnsmasq)
13:41
<alkisg>
No that was just an ubuntu bug
13:41
They tried to run multiple dnsmasq instances
13:41
Then systemd implemented things properly so they stopped doing that in 18.04
13:42
VNC was stopped; run it again please
13:42
x11vnc -connect srv1-dide.ioa.sch.gr
13:42
<enoch85>
oops thought you where disconnected
13:42
rebooted the server just to test if resolv.conf would revert
13:43
<alkisg>
OK; we mainly want to fix the client now
13:43
Lets focus to quickly solve that
13:43
<enoch85>
sure thing
13:44
https://cloud.danielhansson.nu/s/ER8L3ZHk2p439PR
13:47
<alkisg>
OK that video is fine
13:48
As we only put an xterm for the session
13:48
You had no session at all
13:48
<enoch85>
ok
13:48
<alkisg>
In the wiki, dur0k there had startxfce
13:48
<enoch85>
yeah, I thought tha woudn't matter
13:48
but put it back in and try again maybe?
13:49
<alkisg>
No
13:49
You don't have xfce you have lubuntu
13:49
<enoch85>
aah
13:49
<alkisg>
Where is the client?
13:49
<enoch85>
what I thought
13:49
it's powered off
13:49
and can boot it again
13:49
<alkisg>
Can you boot it?
13:49
Yes I'm trying to see the client :)
13:50
<enoch85>
:)
13:51
it should be online now
13:51
<alkisg>
OK
13:51
Can it be rebooted without issues?
13:51
<enoch85>
yes, afaik
13:51
but now iPXE said it had no connection or somethjing...
13:51
I guess due to the DNS issues
13:54
<alkisg>
enoch85: try it again
13:55
<enoch85>
ok rebooting
13:56
unable to launch setupsession.sh (same error as before)
13:56
same error as before
13:57os_a has left IRC (os_a!~Thunderbi@195.112.116.22, Quit: os_a)
13:57os_a has joined IRC (os_a!~Thunderbi@195.112.116.22)
13:58
<enoch85>
reboot?
13:58
<alkisg>
enoch85: why am I not seeing the client in epoptes, due to firewall again?
13:58
<enoch85>
hmm
13:58
<alkisg>
Yes, reboot
13:58
<enoch85>
maybe
13:58
<alkisg>
Let's disable it for a bit please
13:58
So that we can see the client
13:59
<enoch85>
I can't disable it, but I can open it for the IPs in use
13:59
sec
13:59
<alkisg>
ok
13:59
<enoch85>
2.43 right?
13:59
yup
13:59
<alkisg>
Or 192.168.2.237 ?
14:00
<enoch85>
hmm
14:00
<alkisg>
I wonder if pfsense sends a different ip to the pxe stack vs the initramfs
14:00
Better do both
14:00
<enoch85>
done
14:02
<alkisg>
Did the client boot?
14:02
<enoch85>
yes
14:02
sec
14:02
adding more rules
14:03
<alkisg>
After failure, it retries 1 minute later, so it might need a bit
14:03
(epoptes-client, to reconnect to the server if it fails)
14:04
<enoch85>
https://cloud.danielhansson.nu/s/y4xdJSFeMMXWAM3
14:05
<alkisg>
enoch85: reboot again
14:05
<enoch85>
k
14:05
rebooting
14:06
<alkisg>
enoch85: the end result, is it a normal guest session, or just one program, xfreerdp?
14:06
Will the users see menus etc?
14:07
<enoch85>
we will put remmina on the desktop as a single icon, with all the different TS configured
14:07
<alkisg>
OK then a guest session, not a kiosk session
14:07
<enoch85>
OR, several different rdesktop icons per server
14:07
<alkisg>
Did the client boot?
14:08
<enoch85>
yes
14:08
sorry
14:08
<alkisg>
(epoptes-client isn't shown yet)
14:08
Yey
14:08
Now it shows
14:08
Now watch this
14:08
I put something in the template session, on the server
14:08
<enoch85>
ok
14:09
<alkisg>
This goes to the client /etc/guest-session
14:09
*guest-template
14:10
<enoch85>
cool!
14:10
but it doesn't show on the desktop?
14:10
<alkisg>
Now, if we log off the user, it's suposed to login again, and the new file should be there,
14:10
Yes because the user has logged in
14:11
Eh
14:11
What did I click, the client or the server?
14:11
I lost vnc :D
14:11
I was trying to log off the client
14:11
<enoch85>
haha
14:11
I don't know actually
14:11
will log in again
14:11
<alkisg>
I think I logged off from the server
14:11
Yeah log in again and vnc to me
14:12
<enoch85>
reboot?
14:12
<alkisg>
No
14:12
<enoch85>
k
14:12
<alkisg>
It's supposed to re-login
14:13
Doesn't it?
14:13
<enoch85>
no, I just see the login screen
14:13
<alkisg>
Click login again
14:13
<enoch85>
there are three accounts showing: admnistrator; guest; guest session
14:13
<alkisg>
With guest
14:14
<enoch85>
ok
14:14
I used guest session the last timne
14:14
that one said "failed to authenticate"
14:14
<alkisg>
Put a pass there
14:15
I guess that "guest session" is a lubuntu thing, a temporary guest account, not related to ours
14:15
<enoch85>
I would like for it to autologin to the guest account when booting a client
14:15
okok
14:21
<alkisg>
rsync... doesn't sync :)
14:21
<enoch85>
hmm
14:22
strange
14:24
<alkisg>
Let's see if everything's fine now
14:24
For some reason, epoptes-client was disabled
14:24
<enoch85>
would it be possible to sync the settings as well? for example if I want to hide the dock and such?
14:25
<alkisg>
Everything is synced
14:25
Including the dot files
14:25
<enoch85>
ok
14:25
<alkisg>
Did it autoconnect now?
14:25
<enoch85>
no
14:25
<alkisg>
You had to manually log in?
14:25
<enoch85>
I had to manually cklick login for the guest user
14:26
<alkisg>
Did you wait 2 seconds?
14:26
It needs 2 seconds for login
14:26
<enoch85>
aah
14:26
ok
14:26
sec
14:26
reboot again :)
14:26
<alkisg>
no
14:26
A logoff should be enough
14:26
<enoch85>
ok
14:26
let's see
14:26
WORKED!
14:26
sensasion!
14:26
sensation*
14:27
<alkisg>
OK now just leave it be
14:27
It's supposed to autologin in 2 secs after reboot/login screen
14:28
<enoch85>
ok, perfect!
14:28
thank you so much!
14:29
<alkisg>
It doesn't login, does it?
14:29
<enoch85>
nope
14:29
<alkisg>
There's a bug in lightdm
14:29
I'll put the delay to 3 seconds
14:29
<enoch85>
ok
14:30
<alkisg>
So, if a client is very slow, lightdm doesn't autologin in 1 second,
14:30
so I changed it to 2 seconds upstream,
14:30
but maybe you need 5 seconds because the client is extra slow :D
14:30
<enoch85>
haha yeah that might be the case
14:31
still no autologin
14:31
maybe 10 seconds?
14:33
<alkisg>
So far I've only seen this with "lightdm-gtk-greeter"
14:33
MATE uses "slick-greeter"; I haven't seen it there
14:34
<enoch85>
nope, no autologin
14:34
I chose Lubuntu due to the CPU on the clients
14:34
<alkisg>
MATE is as light as LXDE, but offers more things
14:35
It does waste 50 MB more RAM
14:35
But you have enough RAM anyway
14:35
<enoch85>
good point
14:41
<alkisg>
allow-guest=false
14:45
I think there are some lubuntu-specific bugs there too
14:45
It's trying to execute upstart when ubuntu 16.04 is using systemd
14:45
<enoch85>
okok
14:46
<alkisg>
Yeah I can't make it autologin
14:47
I guess if you installed lubuntu locally and tried it, it wouldn't autologin either
14:47
Maybe you should reinstall with ubuntu mate 18.04 for a better experience...
14:47
(and put the old kernel)
14:48
<enoch85>
how do I put the old kernel?
14:48
just uninstall and install the older one?
14:48
<alkisg>
Google for "ubuntu mainline ppa"
14:48
They have all the kernels there
14:48
Yes but you need to install the older one first
14:48
<enoch85>
okok
14:49
will try that then
14:49
worth saving any configs from this setup?
14:49
<alkisg>
Yes, all the /etc/ltsp dir
14:49
<enoch85>
ok
14:49
will do
14:51
I'll fire up a new ubuntu mate 18.04 next to this server
14:51
<alkisg>
OK, install with 18.04.1 so that it keeps a stable kernel
14:51
As 18.04.3 keeps updating to new ones
14:52
ubuntu-mate-desktop-18.04.1-i386 etc
14:53
<enoch85>
dwonloading as we speak
14:53
downloading*
15:05
alkisg thank you so much for the hel so far, you've been more than great!
15:05
help*
15:13
<alkisg>
You're welcome
15:29statler has left IRC (statler!~Georg@gwrz.lohn24.de, Remote host closed the connection)
15:29
<enoch85>
alkisg another question, doing what I'm trying to do, will the thin clients be direclty in contact with the server consuming ethernet, or will they run on their own hardware once booted?
15:30
<alkisg>
Their own hardware
15:30
It's called "fat clients", vs "thin clients"
15:34
<enoch85>
yeah I got that part - so LTSP are making the clients connecting to it "fat clients" once everything is booted and running? so in my case, it's a fat client, but all the stuff comes from the server, hence the nfs mount and guest sessions that are deleted as the files actually reside on the client side once booted?
15:34
did I got that right? :)
15:49spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Excess Flood)
15:50woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Remote host closed the connection)
15:55
<enoch85>
so I'm now on Ubuntu 18.04 with 4.10 kernel
15:57
<alkisg>
Well disk is still served from the server when client is running
15:57
Does it work fine with 4.10?
16:00
<enoch85>
I haven't tested yet
16:00
installing ltsp soon
16:13
booting on the first try
16:14
amazing!
16:59Da-Geek has left IRC (Da-Geek!~Da-Geek@5.154.189.38, Quit: Leaving)
17:25robert45 has joined IRC (robert45!~robert45@r186-54-65-66.dialup.adsl.anteldata.net.uy)
17:27
<robert45>
hey guys, so I finally have my ltsp server working and providing my thin client with a nice login screen GUI. However, when I attempt to login it goes to a blank screen and back to the login screen. syslog shows this: https://paste.ubuntu.com/p/Pk9p9hPQPj/
17:27
any ideas how to fix it?
17:33
<alkisg>
robert45: ltsp 5 or ltsp 19?
17:34
Better yet, output of sudo ltsp-info
17:35
(or `sudo ltsp info` for ltsp 19)
17:35
<robert45>
alkisg ltsp-server 5.5.10-1build1
17:35
<alkisg>
At first, update it, it's very old
17:35
!greek-schools-ppa
17:35
<ltsp>
greek-schools-ppa: https://launchpad.net/~ts.sch.gr/+archive/ppa/ supports LTS Ubuntu releases with newer LTSP versions, bug fixes etc
17:36
<alkisg>
Both the server and the chroot if you have a chroot
17:36
<robert45>
alkisg how aggresive is the update? I have spent so many days trying to get this work
17:37
and Im almost finally there
17:37
<alkisg>
It's not, it's a very stable ppa for 1000+ schools
17:37
<robert45>
alkisg ok cool. Running the upgrade now
17:37
<alkisg>
Btw I dont remember, did you need thin clients and you want to the old ltsp?
17:37
*went
17:38
<robert45>
alkisg I need thin clients. What do you mean by the old ltsp?
17:40
<alkisg>
You're using ltsp5, which is not really maintained anymore
17:40
The new ltsp19 supports fat clients (remote disk) and xfreerdp/x2go, but not remote xorg (thin clients)
17:41
<robert45>
My machines are all thin clients
17:41
<alkisg>
What cpu model exactly and how much ram?
17:42
<robert45>
alkisg sorry, are you talking about the server or clients?
17:42
<alkisg>
The clients
17:47
<robert45>
alkisg uhmm Im not sure, I can get that info later if you need
17:48
<alkisg>
Nah I don't need it, but if YOU need advice, we can surely help :)
17:48
<robert45>
alkisg nevermind, I found it here. Its 4GB RAM CPU Intel core i5
17:48
<alkisg>
Woah, the client?!
17:49
<robert45>
by the way, have upgraded the packages and Im now running the chroot upgrade
17:49
alkisg yes
17:49
<alkisg>
Eeeh, and what's the output of this command? ls /opt/ltsp/*/usr/share/xsessions
17:49
On the server
17:49
<enoch85>
alkisg, so just a quick update - the NFS mount is working as expected, but it still doesn't autologin and I only have one screen instead of dual (1 X VGA & 1 X DP)
17:50
<||cw>
with those clients you'll get much better performance with fat client.
17:50
<alkisg>
enoch85: put RELOGIN_TIMEOUT=5 in ltsp.conf, run ltsp initrd, and reboot client
17:50
<||cw>
and the user really won't be able to tell the difference otherwise
17:51
<robert45>
alkisg here: https://paste.ubuntu.com/p/QBgBHrhqqf/
17:51
<alkisg>
enoch85: also check that it relogins if you logout (i.e. the problem only happens on first login)
17:51
robert45: ok, so afaik you're using *fat* clients, not thin clients
17:51
It would be best to use ltsp19 then, not the old ltsp5
17:51
<enoch85>
alkisg it automatically logins if I logout
17:51
<alkisg>
!install
17:51
<ltsp>
install: To install LTSP19+: https://ltsp.github.io/docs/installation. To install LTSP5: http://wiki.ltsp.org/wiki/Installation/Ubuntu for Ubuntu, or http://wiki.ltsp.org/wiki/Installation for other distributions
17:51
<alkisg>
I.e. the first link there
17:51
enoch85: ok, try RELOGIN_TIMEOUT=5
17:52
<enoch85>
I put it to 10 ;)
17:52* alkisg wonders if lightdm doesn't like the name "guest"... :D
17:52
<enoch85>
haha
17:52
10 seconds worked!
17:53
<alkisg>
OK try 2
17:53
If 2 works, then we've already fixed it this morning upstream, and we just need to push an update to the ppa
17:53
<robert45>
alkisg what about this one? https://paste.ubuntu.com/p/bNkmDyQcrJ/
17:54
<enoch85>
alkisg great!, and what about dual displays, are that set in the ltsp.conf as well?
17:54
<alkisg>
robert45: if they were empty, it would mean thin clients. Now that there are session files there, it's fat clients
17:54
enoch85: afaik they're autodetected
17:54
Let's VNC and check if you want
17:54
!vnc-edide
17:54
<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
17:54
<enoch85>
alkisg nope they were not
17:55
<alkisg>
enoch85: for example, maybe you're missing modules or have xorg issues etc, we'd need to check
17:55
And we can also test with xrandr after login
17:55
<enoch85>
alkisg I tried to set dual displays in Mate, but only one was detected, it strated to boot on one screen though and then switched to the other
17:55
<alkisg>
Normally you don't need a xorg.conf for displays, but if you do, then you can put one in ltsp.conf
17:56
<enoch85>
2 seconds worked btw, awesome!
17:56
<robert45>
alkisg ok I got it. I have upgraded the packages as you suggested but the same error persists. Would you mind giving me a hand on where to look? If I dont get to fix this one I will switch to lts19 but I believe Im real close of getting a working ltsp server
17:56
<alkisg>
enoch85: OK that was fixed in https://github.com/ltsp/ltsp/issues/58#issuecomment-549711552
17:57
robert45: do you have epoptes installed?
17:57
<enoch85>
thanks!
17:57
<alkisg>
(that's epoptes.org, client monitoring tool)
17:57
<enoch85>
so I'm even more happy about this config than I was this morning, running Ubuntu 18.04 is great!
17:58
now, my wife needs some attention :)
17:58
<alkisg>
It's the last one that supports 32bit, so yeah it's a good one
17:58
Haha
17:58
<enoch85>
talk to you tomorrow :)
17:58
<alkisg>
Go go quickly, it can be a problem if we don't attend to them when they need it :D
17:58
Bye
18:00
robert45: I have just 5 minutes, if you want do a vnc so that I check quickly what's wrong:
18:00
!vnc-dide
18:00
<ltsp>
vnc-dide: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect srv1-dide.ioa.sch.gr - this is a reverse connection, it doesn't need port forwarding etc.
18:03
<robert45>
alkisg yes, I have epoptes and epoptes-client installed on the server
18:04
alkisg sure! One min
18:04
alkisg I think we had a problem with x11vnc which was not working. Let me open the vnc link you gave me the other day
18:05
alkisg done
18:07
<alkisg>
robert45: didn't receive anything
18:07
Are you running wayland?
18:07
vnc doesn't work with wayland
18:08vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
18:08
<robert45>
alkisg its the uvnc-dide app I launched
18:09
<alkisg>
robert45: ah, the headless server? OK run it again I'm ready for that now
18:11
<robert45>
alkisg Oh I thought the apt-get update was for the server only, and then run it the update image. Sorry about that
18:11
<alkisg>
Yeah you didn't have the ppa in the chroot
18:11
But note that you're making it very hard for yourserlf, if you have i5 clients
18:11
You have an i386 chroot, and a headless server,
18:11
when you could just have a desktop template server and no chroots at all, and maintain everything graphically
18:12
(and the newest and maintained ltsp)
18:12
If you have i5 clients there's no reason to have an i386 chroot
18:12
<robert45>
alkisg that would prevent users from login from random desktops, right?
18:12
<alkisg>
Not sure what you mean with random desktops
18:12
Like, an insecure server that people can login to?
18:13
Only if they have ssh access
18:13
<robert45>
alkisg I have multiple desktops, my staff doesnt have an unique desktop for themeselves, they seat on a different one every day
18:14
so I need their login work the same for all the machines
18:14
<alkisg>
You can maintain any number of different images graphically
18:14
There's no software reason to use headless... only hardware reasons to use headless :D
18:15
<robert45>
alkisg I see. If I happen to get this working I will check performance and move to fat clients if you say its better. But would really like to get this working for testing
18:15
alkisg by the way thanks so much for your help so far, its really appreciated
18:15
<alkisg>
vagrantc: ltsp binaries download stats: https://www.somsubhra.com/github-release-stats/?username=ltsp&repository=binaries
18:15
robert45: you're already using fat clients; nothing to move into...
18:16
<robert45>
alkisg do I need to reboot the desktop?
18:17
<alkisg>
robert45: after this is done, yes
18:17
<robert45>
alkisg ok great, becasue I need to do a change in pxelinux.cfg/default first
18:18
still not sure how to save certain settings on this file, everytime I rebuild the image I have to update some kernel values to make the clients boot
18:23woernie has joined IRC (woernie!~werner@p57A0E783.dip0.t-ipconnect.de)
18:26
<vagrantc>
alkisg: is that some third-party site that uses a github api to get the stats?
18:33
<alkisg>
vagrantc: exactly, just a user site that demonstrates the github api
18:34
But it's nice to have 480 ipxe downloads since the summer
18:34
robert45: in ltsp19 it's just KERNEL_PARAMETERS in ltsp.conf; in ltsp5 it ...takes a long time to explain it :)
18:34
<vagrantc>
alkisg: sure
18:37
<robert45>
alkisg sorry office connection died. I have restored the vnc connection
18:37
alkisg its throwin 1 less error but still not logging in
18:37
<alkisg>
robert45: ok let me see
18:38
robert45: the server is headless so we can't run epoptes, right?
18:38
<robert45>
alkisg correct
18:39
<alkisg>
OK go to the server and get me a sudo shell
18:39
<robert45>
alkisg its there
18:40
alkisg you need US keyboard?
18:41
alkisg by the way, if I dont put X_COLOR_DEPTH my desktop shows a black screen
18:42
<alkisg>
robert45: I can't put #
18:42
So where I put ;, change it to #
18:42
Some keyboard layout weirdness
18:42
<robert45>
alkisg ok one sec
18:43
<alkisg>
robert45: ok reboot client
18:43
<robert45>
alkisg doing that now on your screen
18:43
<alkisg>
So... you *were* using thin clients because you were forcing LTSP_FATCLIENT=False in lts.conf
18:43
If this works now, you'll see a lot better performance
18:44
<robert45>
alkisg fingers crossed
18:44
<alkisg>
How much RAM does this VM client have?
18:44
<robert45>
alkisg not much, 1GB I believe
18:44
should I try to login now?
18:44
<alkisg>
Hrm, pretty low for Ubuntu, but it should be enough for login
18:44
Yes
18:44
(MATE is a lot lighter)
18:46
OK it logs in but I think it's very slow due to low RAM
18:46
open a terminal and let's check "free"
18:46
<robert45>
alkisg wow! Finally! Logged in!
18:46
<alkisg>
See, it just needed the defauls :)
18:46
No strange settings in lts.conf :D
18:47
1 GB RAM should cause a lot of swapping with GNOME though... better test with at least 2 GB
18:48
<robert45>
alkisg yeah its hard to test with this vm. Let me try to get to the office!
18:49
alkisg do you recommend network compression disabled?
18:50
<alkisg>
Fat clients don't transfer a lot of data over ssh, it's mostly nbd
18:50
And even for thin clients and remote xorg, LDM_DIRECTX=True makes the traffic not go through ssh
18:50
So I'm not sure if that switch is even used at all
18:54
Btw most of the lts.conf parameters you're using there, do not exist in the new ltsp at all...
18:55
<robert45>
alkisg Thanks a lot! Cant believe we got this working. Im testing in the office right now. So far its good. Our main purpose of upgrading the OS and ltsp was to attempt to resolve some latency problems we had. Im still thinking on testing ltsp19. Based on my current setup, do you still think using this version, with 64bit arch and with fat clients instead would improve this by a lot?
18:55
<alkisg>
I'm not sure how to say this...
18:55
You're already using fat clients now, so you'll see no change in performace
18:55
well, ltsp19 is just a bit faster and more stable, but not significantly,
18:56
But, if you follow the normal ltsp19 installation page, things will be so much simpler for you
18:56
You had to work for days to set up ltsp5; while for ltsp19, it should work immediately
18:57
and you can't even run epoptes now
18:58
<robert45>
alkisg why should I run epoptes?
19:01
<alkisg>
e.g. to troubleshoot issues like this
19:01
in 1 min insetad of hours
19:01
<robert45>
alkisg understood
19:22woernie has left IRC (woernie!~werner@p57A0E783.dip0.t-ipconnect.de, Remote host closed the connection)
19:50meo has joined IRC (meo!~systemdju@unaffiliated/mikeseth)
20:03section1 has left IRC (section1!~section1@178.33.109.106, Quit: Leaving)
20:05kjackal has left IRC (kjackal!~quassel@2a02:587:3107:2e00:4df2:7425:ba6f:da10, Remote host closed the connection)
20:36Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
20:52
<robert45>
alkisg Im not sure why but it looks Im running a i386 chroot image, is there any easy way of changing this to x64? The ltsp server is 64bit but the thin client image seems to be 32bit
20:56
<||cw>
either build a new 64bit chroot, or build using chrootless. ubuntu doesn't provide a 32bit to 64bit upgrade path.
20:56
i'm not away that any distro does really, not even windows
20:57
<robert45>
||cw Thanks
21:12
<alkisg>
robert45: just give up on your path, follow advice, and have ltsp19 with chrootless amd64 in 30 mins :)
21:15
<robert45>
alkisg will do, just trying to get all sorted out before I can compare
21:21robert45- has joined IRC (robert45-!~robert45@r167-57-51-13.dialup.adsl.anteldata.net.uy)
21:21robert45 has left IRC (robert45!~robert45@r186-54-65-66.dialup.adsl.anteldata.net.uy, Read error: Connection reset by peer)
21:25robert45- is now known as robert45
21:26
<robert45>
alkisg ||cw is there any way to convert the current image to 64bit or do I need to build and entirely new one?
21:26
<alkisg>
robert45: you need to build a new one, either with ltsp-build-client or with ltsp-update-image -c /, which then clones the server installation
21:27
<robert45>
alkisg ok thanks
21:27
<alkisg>
(that one is the fastest, and it's what we call chrootless, but if you have no xsessions, it won't do)
22:29
<||cw>
robert45: you can't convert a 32bit OS install (which is what a chroot+image is) from 32bit to 64bit. this is a linux thing directly, not an LTSP limitation
22:50ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
23:06gvy has left IRC (gvy!~mike@altlinux/developer/mike, Ping timeout: 252 seconds)
23:07gvy has joined IRC (gvy!~mike@altlinux/developer/mike)