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


Channel log from 5 March 2021   (all times are UTC)

00:05bengoa has joined IRC (bengoa!~alberto@194.50.55.200)
00:14alkis[m] has left IRC (alkis[m]!alkismatri@gateway/shell/matrix.org/x-gwzvtjchdvawfees, Ping timeout: 265 seconds)
00:26alkis[m] has joined IRC (alkis[m]!alkismatri@gateway/shell/matrix.org/x-yfpofnfbxhchjkhs)
01:21Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds))
01:22Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
01:48uumas has left IRC (uumas!uumaskapsi@gateway/shell/matrix.org/x-jctksfulodanxevm, Ping timeout: 258 seconds)
01:48alkis[m] has left IRC (alkis[m]!alkismatri@gateway/shell/matrix.org/x-yfpofnfbxhchjkhs, Ping timeout: 240 seconds)
02:22alkis[m] has joined IRC (alkis[m]!alkismatri@gateway/shell/matrix.org/x-npxlypkkfzrbldhv)
02:45uumas has joined IRC (uumas!uumaskapsi@gateway/shell/matrix.org/x-qwejelkbrdxqkvmp)
05:29RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro)
06:45woernie has joined IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de)
06:52ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:19sfrank has joined IRC (sfrank!4d811845@69.24.129.77.rev.sfr.net)
08:12
<alkisg>
sfrank: did you manage to boot your rpis?
08:26
<sfrank>
alkisg yes thank you
08:26
<alkisg>
Great
09:19sfrank has left IRC (sfrank!4d811845@69.24.129.77.rev.sfr.net, Quit: Connection closed)
09:33sfrank has joined IRC (sfrank!4d811845@69.24.129.77.rev.sfr.net)
10:04RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.)
10:50sfrank has left IRC (sfrank!4d811845@69.24.129.77.rev.sfr.net, Quit: Connection closed)
12:58Douglas_br has joined IRC (Douglas_br!bd4cbe5a@189.76.190.90)
12:58
<Douglas_br>
Hello, how are you?
13:02
Please, I have a situation that when I tested a ltsp client out with live usb Linux Image, it ups nice, give me screen system all ok. But, when put it to works in ltsp client, it ups this mode: https://imgur.com/jmGZ2SW
13:03
so, it tries up again but, shows as: https://imgur.com/o2xS2RH
13:04Douglas_br has left IRC (Douglas_br!bd4cbe5a@189.76.190.90, Quit: Connection closed)
13:07Douglas_br has joined IRC (Douglas_br!bd4cbe5a@189.76.190.90)
13:08
<Douglas_br>
sorry! i wiil repeat my question ok
13:09
Please, I have a situation that when I tested a ltsp client out with live usb Linux Image, it ups nice, give me screen system all ok. But, when put it to works in ltsp client, it ups this mode: https://imgur.com/jmGZ2SW
13:09
so, it tries up again but, shows as: https://imgur.com/o2xS2RH
13:09
at the server side there is a video card but I do not install the driver video card.
13:34woernie_ has joined IRC (woernie_!~werner@pd9e8b5cc.dip0.t-ipconnect.de)
13:35Douglas_br has left IRC (Douglas_br!bd4cbe5a@189.76.190.90, Quit: Connection closed)
13:35woernie has left IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de, Ping timeout: 260 seconds)
13:35Douglas_br has joined IRC (Douglas_br!bd4cbe5a@189.76.190.90)
13:35
<Douglas_br>
someone know how can fix this
13:41
<mwalters>
Douglas_br: "OSD Locked" looks like something the monitor is outputting. I'm *guessing* that the display isn't active on the client. The OSD is locked on the monitor, so the monitor is outputting that instead of "no signal" or something similar.
13:43
First thing I would try would be to open a terminal on the client from epoptes and see what xrandr outputs
13:46
<Douglas_br>
mwalters discard the message osd Locked, its simple fail from Monitor, it is used on our room "fix things" it shows images but give this bored message on screen
13:48
<mwalters>
Regardless, I think first step is to check the output of xrandr on the client
13:48
if you can connect to it
13:52
<Douglas_br>
from epoptes, it shows the client but says: disconnected, but shows "screen" ltsp name
13:54
in the other hannd the client made the process to up, only can show the login screen or system screen
13:54
cannot
13:56
<mwalters>
in epoptes, please try: Right click the client > Execute > open terminal > Root, locally
13:57
if it brings up a terminal, please run xrandr in it and take a look at which displays are active
14:00
<Douglas_br>
look at this: https://imgur.com/c0fpDOp
14:02
<alkisg>
mwalters ++ :)
14:02
<Douglas_br>
ok I wiil try
14:02
<alkisg>
Douglas_br: what mwalters says is: right click on the ltsp54 icon in epoptes. Select execute > open a terminal > root, locally
14:02
There, type: xrandr | nc termbin.com 9999
14:02
<Douglas_br>
right
14:02
<alkisg>
This will upload the output of xrandr to termbin. Give us the URL that it will show
14:03
<mwalters>
I've been down this rodeo, willing to bet that client has a LVDS display connector in it ;)
14:03
<alkisg>
Or something with the nouveau driver
14:09
<Douglas_br>
here: https://imgur.com/7swEazO
14:12
@alkis there is a nvidia video card but I do not install the driver.
14:12
<alkisg>
Douglas_br: run the following,it will upload some info:
14:12
( cat /var/log/Xorg.0.log; dmesg; lspci -nn -k | grep -A 3 VGA; ) | nc termbin.com 9999
14:12
Douglas_br: did you install the nvidia driver on the server?
14:13
<Douglas_br>
no, I do not install the nvidia driver on server
14:23
wait please
14:28
https://termbin.com/i1p4
14:59
<alkisg>
[ 75.346254] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:42:pipe A] flip_done timed out
15:00
Douglas_br: it sounds like a kernel/xorg issue, and it only runs in the live usb because it's a different kernel/xorg
15:00
I'd try to update kernel/xorg to -hwe (5.8)
15:06
<mwalters>
Douglas_br: what processor and which linux distro & version
15:06
I had to install HWE packages to support 10th gen intel processors on 18.04
15:54GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net)
15:58adrianorg has joined IRC (adrianorg!~adrianorg@177.156.230.68)
16:00adrianor1 has left IRC (adrianor1!~adrianorg@187.113.247.134, Ping timeout: 265 seconds)
16:18
<Douglas_br>
mwalters the processor is: Intel(R) Core(TM) i3-9100F CPU @ 3.60GHz
16:18
and Linux: Xubuntu 20.04 LTS
16:20
alkisg ohhh ok
16:25
so, Is it better let this client out of LTSP
16:25
<alkisg>
Douglas_br: no, ltsp isn't the problem
16:25
If you install local ubuntu, it will have the same problem
16:26
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
16:26
This ^ page says how to put the 5.8 kernel that Ubuntu 20.04.2 has
16:26
While Ubuntu 20.04.1 has 5.4
16:28
<Douglas_br>
but the client is an old machine, ecs p49 (trash Mobo)
16:28
p49G
16:34
@alkis I will to try follow the link
16:37Douglas_br has left IRC (Douglas_br!bd4cbe5a@189.76.190.90, Quit: Connection closed)
16:37
<mwalters>
i9 is I can't find any solid info... 9100F is marked coffee lake, but 9th gen sku... very confusing
17:07Douglas_br has joined IRC (Douglas_br!bd4cbe5a@189.76.190.90)
17:07
<Douglas_br>
hello
17:13Douglas_br has left IRC (Douglas_br!bd4cbe5a@189.76.190.90, Quit: Connection closed)
17:17
<alkisg>
Douglas_br, it doesn't matter that it's an old client, new kernels (e.g. 5.4) often break things that were working previously, and even newer kernels (e.g. 5.8) may restore functionality
17:23carles-alemany has joined IRC (carles-alemany!53348273@115.red-83-52-130.dynamicip.rima-tde.net)
17:35
<alkisg>
Hi carles-alemany, will be here in 10 mins, wait
17:36carles-alemany has left IRC (carles-alemany!53348273@115.red-83-52-130.dynamicip.rima-tde.net, Quit: Connection closed)
17:36carles-alemany has joined IRC (carles-alemany!53348273@115.red-83-52-130.dynamicip.rima-tde.net)
17:39
<alkisg>
(07:35:38 PM) alkisg: Hi carles-alemany, will be here in 10 mins, wait
17:43
carles-alemany: do you have epoptes installed?
17:43
!vnc-edide
17:43
<ltspbot>
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:43
<alkisg>
If you have it, do that ^
17:44
<carles-alemany>
Let me check. On the client?
17:44
<alkisg>
On the server
17:44
<carles-alemany>
ok
17:44
<alkisg>
If so, you'd share your server screen with me, and we'd visit the client together,
17:44
if not, there are ways to share the client screen too, np there
17:49
<carles-alemany>
it's connecting, do you see anything?
17:50
<alkisg>
carles-alemany: something's blocking it
17:50
I see it trying to connect, but failing
17:50
Firewall?
17:50
No xorg access?
17:51
<carles-alemany>
maybe it's the firewall, I don't have control over it
17:51
<alkisg>
OK let me give you a different command
17:51
Try this: x11vnc -connect alkisg.ltsp.org:80
17:54
carles-alemany: we'll need access to the client,
17:54vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
17:55
<carles-alemany>
alkisg should I login to the client with the same user I did on the server? Or with a domain user?
17:55
<alkisg>
carles-alemany: login with the local admin on the client, and run x11vnc again
17:55
Then we'll switch to root and test things from there
17:55
<carles-alemany>
alkisg on my way
17:55
<alkisg>
You have xorg on the client, right?
17:55
OK, waiting
17:56
<carles-alemany>
installing x11vnc on the client
18:03
<alkisg>
carles-alemany: heh, the problem is that you have an older ltsp that doesn't support ldap :D
18:03
Let me see why...
18:03
<carles-alemany>
D:  I thought 21.01 was the last version
18:04
<alkisg>
I think it's my fault, but let me check...
18:05
https://github.com/ltsp/ltsp/commit/7246dbefe5b60e783af84a22384ece492ab38011#diff-59beab58c85adaf1fc6c96ed556ae7045cd0352516d62a08e3a5950dd84b0770R73
18:05
OK that's on november and yet you're missing it, checking more...
18:11
carles-alemany: is it possible that you manually downloaded a different pamltsp file?
18:11
Let's go to the server and unlock it
18:11
(the screensaver there)
18:11
<carles-alemany>
I don't remember doing that
18:13
<alkisg>
carles-alemany: can you reboot the client and login as admin again and connect to me via x11vnc again?
18:14
<carles-alemany>
alkisg sure
18:14
<alkisg>
You had an older pamltsp file but I've no idea why; everything is new except that file on that client
18:14
So I want to see if after running `ltsp initrd` on the server, the client gets the correct pamltsp script version...
18:17
<carles-alemany>
Now I am unable to login with the adminlocal user on the client. Let me try with a domain one
18:21
I've logged in successfully with a domain user (profetest2), and now the home directory is being loaded from the server. But I cannot login with adminlocal, it seems to be an authentication failure (but the pwd is correct)
18:22
<alkisg>
carles-alemany: that's ok, pamltsp can't work in both modes, local AND remote
18:22
So now that it detected that you have ldap, it doesn't allow local users
18:22
You can login as root if you put an ltsp.conf entry
18:22
!ltsp.conf
18:22
<ltspbot>
ltsp.conf: Configuration file for LTSP: https://ltsp.org/man/ltsp.conf/
18:22
<alkisg>
...the last example there
18:23
<carles-alemany>
and the root pwd is the one from the server?
18:23
<alkisg>
No, you set a custom hash in ltsp.conf
18:23
Read that example there
18:23
And, if you set up epoptes, you can get a root shell from there
18:23
Let's set up epoptes
18:23
<carles-alemany>
Sorry I just read it
18:24
Doing it
18:24
<alkisg>
I'm about to install epoptes-client in your chroot
18:24
Should I?
18:24
<carles-alemany>
sure
18:24
<alkisg>
OK
18:25
So, I think that you initially didn't have the ppa in the chroot
18:25
And you run ltsp initrd, and you got an ltsp.img with the old version
18:25
Then you added the ppa, updated, run ltsp image etc etc, ....but you didn't run ltsp initrd
18:26
So the old ltsp in ltsp.img, was overwritting the new ltsp in the image, giving you the older pamltsp script, breaking ldap :)
18:26
Mystery (probably) solved
18:29
<carles-alemany>
I understand. So, every time I create a new chroot I should run ltsp initrd
18:29
<alkisg>
ltsp initrd is needed when a new ltsp comes out, or when new users are added and people aren't using ldap, or when ltsp.conf gets modified
18:30
In some next ltsp version, I'll introduce a web server to automate that, but I didn't have time to do it the 2 last years
18:31
epoptes-client is ready, if you reboot the client we should see it in epoptes
18:31
<carles-alemany>
Thanks for the clarification on ltsp initrd! Client rebooting
18:35
<alkisg>
Hmm
18:39
carles-alemany: everything is as expected
18:39
I wasn't sure if pamltsp is called when ldap is in effect, it's not
18:39
So it's ok that local users can't login when you have ldap users
18:39
I also added the greek schools ppa in your server, as it has a fixed socat package
18:40
<carles-alemany>
Understood. I had the greek schools ppa on the LTSP5 server too.
18:40
<alkisg>
Do you need anything else, or should we close VNC?
18:42
<carles-alemany>
Just one thing, when I joined the chroot to the domain using realmd join, I had to do it from a client, by sharing the chroot in rw mode via NFS, because I wasn't unable to do it from the server with chroot command. Is that normal?
18:42
<alkisg>
No idea; I'm also not sure if you'll be able to boot many clients at once or just one
18:42
I don't know what restrictions AD has
18:42
AD requires "client joining" while ldap is only about users
18:43
That's why I told you to create a separate topic, I didn't imagine it would be doable without enrolling all the clients into AD
18:43woernie_ has left IRC (woernie_!~werner@pd9e8b5cc.dip0.t-ipconnect.de, Remote host closed the connection)
18:43
<alkisg>
What was the error message when you tried it in a chroot?
18:44
<carles-alemany>
I didn't documented it, I think it was trying to use server's hostname instead of chroot hostname.
18:44
<alkisg>
Can you try to boot multiple clients now?
18:45
E.g. to see if two clients work, or just one...
18:45
<carles-alemany>
I was just about to ask if I should test it. Give me 2 minutes, I'll create some new VMs
18:45
<alkisg>
Maybe ad is doing reverse dns lookup, and it saw that you had already enrolled the server
18:46
<carles-alemany>
That was probably the problem, because when I got the error joining the chroot, the server account was disabled on AD (because it's a reused name). Now I have two computers shown on AD, S-208.domain.lan (the server) and focal.domain.lan (the chroot)
18:49
alkisg: Two clients logged in at the same time with different AD users
18:49
<alkisg>
Great
18:49
It's also possible that the "enrollment" will expire after some time
18:50
And that you'll need to chroot and update it once more; again, no idea about AD, let's see how it goes :)
18:50
I've used the new LTSP with LDAP in production, no problems there for months
18:50
But not with AD
18:50
<carles-alemany>
I see
18:50
<mwalters>
used to be AD had limit for number of computers that could be joined by a single user... I'm guessing you're using the login user to join the domain?
18:51
but I haven't messed much with AD since like 2012
18:53
<carles-alemany>
I've joined the chroot into the domain using realmd join using the administrator user, then built the image and started serving it to clients.
18:54
On the test we've just made, two different clients are capable of booting from the same image and login with domain users (using the same chroot)
18:55
alkisg: I'll test how it works with shared SMB resources and get back confirming if it works or not.
18:55
<alkisg>
carles-alemany: ok, good luck
18:56
<carles-alemany>
Also, I'll start to test with a few users, just to confirm if the enrollment expires. THANK YOU very much for your help!
18:57
<alkisg>
You're welcome. Keep in mind that it might expire weeks later
18:59
<carles-alemany>
I will. The test chroot was joined 5 weeks ago and it still works. Fingers crossed.
19:12carles-alemany has left IRC (carles-alemany!53348273@115.red-83-52-130.dynamicip.rima-tde.net, Quit: Connection closed)
19:12carles-alemany has joined IRC (carles-alemany!53348273@115.red-83-52-130.dynamicip.rima-tde.net)
19:14GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Ping timeout: 260 seconds)
19:17carles-alemany has left IRC (carles-alemany!53348273@115.red-83-52-130.dynamicip.rima-tde.net, Quit: Connection closed)
22:02ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)