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


Channel log from 11 January 2022   (all times are UTC)

05:44quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: WeeChat 3.3)
05:47quinox has joined IRC (quinox!~quinox@ghost.qtea.nl)
06:57ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
08:00vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Quit: leaving)
11:12woernie has left IRC (woernie!~werner@p5b296789.dip0.t-ipconnect.de, Ping timeout: 240 seconds)
11:12woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de)
11:26woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 256 seconds)
13:35woernie has joined IRC (woernie!~werner@p5b296789.dip0.t-ipconnect.de)
13:48woernie has left IRC (woernie!~werner@p5b296789.dip0.t-ipconnect.de, Remote host closed the connection)
13:49woernie has joined IRC (woernie!~werner@p5b296789.dip0.t-ipconnect.de)
13:50woernie has left IRC (woernie!~werner@p5b296789.dip0.t-ipconnect.de, Remote host closed the connection)
13:51woernie has joined IRC (woernie!~werner@p5b296789.dip0.t-ipconnect.de)
15:58danboid has joined IRC (danboid!~danboid@146.87.136.62)
16:01
<danboid>
Im at a loss as to whats happening with ltsp. I removed the old images then created a new one but its still booting the old one somehow yet I can,t see how thats posibble. There is only one ltsp image file under /srv/ltsp and its got todays date. Very weird!
16:02
I know its the old one as my current image is using lightdm but the previous image was using gdm and thats what Im seeing
16:06
Ah but I see it hasnt updated the files in /srv/tftp/ltsp/Ubuntu-20.04
16:07
maybe I had to delete that dir too?
16:07lucascastro has left IRC (lucascastro!~lucascast@192-140-51-251.static.oncabo.net.br, Remote host closed the connection)
16:07
<danboid>
I presumed 'ltsp image' woulf
16:07
dve
16:08
updated that every time it got run?
16:09lucascastro has joined IRC (lucascastro!~lucascast@192-140-51-251.static.oncabo.net.br)
16:09
<danboid>
I was just going off a wiki article on how to remove old images
16:10
It said you just needed to remove tge
16:10
the image file basically but it seems there is more to it
16:10
I used the same name for the image
16:15
<alkisg>
The .img image get renamed to .old when you run ltsp image
16:16
<danboid>
OK so this time Ive deleted the /srv/tftp/ltsp/Ubuntu-20.04/ dir and the ltsp image and Im trying again
16:16
<alkisg>
The already booted clients keep using the .old image until they're rebooted
16:16
If that's not what you mean, then maybe you have a second server that you forgot... it's pretty common :)
16:16
<danboid>
The old image was deleted and the client had been turned off for weeks
16:17
we can use lightdm right? Its not the ltsp scripts reverting my image back to gdm is it?
16:20
I thought you use Ubuntu MATE alkisg? That defaults to lightdm, I think
16:20
<alkisg>
ltsp doesn't touch the default dm configuration at all
16:21
So yeah, for my ubuntu mate it's lightdm, but if you install gdm there, it'll switch to gdm because of ubuntu/debian, not because of ltsp
16:21
<danboid>
I didnt think so. Its the weirdest bug
16:21
Ive seen in along time
16:21
<alkisg>
It sounds more like a sysadmin bug :D
16:21
You have some wrong configuration somewhere in your image
16:22
<danboid>
What is the procedure for deleting / replacing an image?
16:23
If you want to use the same name
16:23
Are the any gotchas?
16:24
There was no .old image as I deleted the old one first
16:24
<alkisg>
It's nothing notable, you just rename / move things
16:24
<danboid>
Oh I know what it must be
16:25
I used created a snapshot in the vm. Ill have to get rid of that first right?
16:27
.vmdk lets you create snapshots but ltsp image probably doesnt know which one to use
16:28
Thats the only thing I can think of
16:28
<alkisg>
ltsp doesn't support snapshots
16:28
It's using the underlying image
16:28
It's just a mount command
16:28
There's no fancy library that reads snapshots etc involved
16:29
mount can't read snapshots, so ltsp can't read snapshots
16:29
<danboid>
I created the image in virtualbox so yes, that does let you create snapshots
16:29
Im going to remove the snapshot and see if that fixes it
16:54
Yes, it was the snapshot causing probs. You have to delete all snapshots in virtualbox before running ltsp image
16:55
<alkisg>
No, ltsp image will work if you have snapshots, but it will take the underlying image, the first one that you see in the "vbox snapshots" window
16:55
<danboid>
Correct but 99% of the time the user wants to current state of the vm
16:58
So it seems pamltsp cannot mount my home dirs via sshfs, any idea why? /home is mounted on ZFS
17:01
alkisg - I thought you used zfs for your home dirs?
17:01
<alkisg>
In one of 1000 setups, sure
17:01
<danboid>
I cant quite see the full error on the lightdm login page
17:02
What I can see is
17:02
.Pamltsp failed to mount home via SSHFS:read
17:06
Presumably I need to tweak pamltsp to work with ZFS?
17:13
<alkisg>
You can try to login in vt2 to see the full error message
17:18
<danboid>
Yes, full error is
17:19
.Pamltsp failed to mount home via SSHFS: read: Connection reset by peer
17:20
So is this more likely a zfs config issue or does the pamltsp script need to be changed?
17:24
The LTSP server is using mdraid10 xfs for its disks except for /home which is ZFS
17:24
<alkisg>
The server home is not related to the client sshfs mount
17:24
Try to run sshfs manually from elsewhere and see what the problem is
17:25
The server home can be zfs, samba, whatever; sshfs doesn't care about that
17:26
<danboid>
OK, I'll try mounting the same users home via sshfs on my laptop
17:28
This command works fine to mount the same home dir
17:28
sshfs sgs548@asteria.cs.salford.ac.uk:/home/sgs548 /home/dan/mnt/
17:28lucascastro has left IRC (lucascastro!~lucascast@192-140-51-251.static.oncabo.net.br, Ping timeout: 256 seconds)
17:29
<danboid>
That is the ZFS home dir / user that pamltsp cant mount
17:31
Im not running iptables on the LTSP server yet so its not that
17:33
Ah! I;
17:33
Ive disabled ssh password logins on the LTSP server
17:34
Ill have to enable that wont I? :)
17:35
I think I know the answer to that one
17:44
Nah, still getting the same error
17:44
with ssh passwords enabled
17:45
Do I have to do some special config to get pamltsp to work with ldap?
17:46
Im using nslcd and I could login on a Ubuntu VM using nslcs but not LTSP
17:46
using nslcd for LDAP but no LTSP
17:52
Is LTSP known to work with nslcd?
17:53
nslcd seems much easier to configure than sssd-ldap
17:54
and I expected it wouldn;t care which one I used but maybe it does matter
17:55
In fact sssd-ldap wasnt a choice for us yet as we're still using LDAP not LDAPS. sssd only supports LDAPS
17:57
Think Ill have to leave this g
17:57
for today as Im all out of ideas
17:59
alkisg - Have you heard any reports of people successfully using nslcd with LTSP?
18:02
<alkisg>
danboid: I've added support for sssd to work out of the box
18:02
For other variants, there's no autodetection, and you'll need to manually set PAMLTSP=0 etc, see the ltsp.conf man page
18:04
<danboid>
etc? Are there any other vars you knoe
18:04
know Ill have tochange?
18:04
Sorry typing on a crappy pocket BT keyboard
18:16
alkisg - PAMLTSP doesnt have an entry in the ltsp.conf man page. Shall I open a bug report for that?
18:16
So I dont know which section of ltsp.conf to add it to
18:17
Its not in the included ltsp.conf either
18:32
<alkisg>
danboid: indeed, sorry, it's PAM_AUTH_TYPE: https://github.com/ltsp/ltsp/issues/338#issuecomment-735230997
18:33
If you want LDAP authentication with SSHFS homes, it's PAM_AUTH_TYPE=Additional under [clients]
18:44
<danboid>
Nope. Ive added that line, ran 'ltsp initrd' and rebooted but still get the same error
18:49
<alkisg>
And can you ssh from the ltsp client to the server?
18:49
Open a root shell and try `ssh user@server`
18:49
If that doesn't work, then you can't use sshfs
18:54
<danboid>
I have successfully ssh'd from VT2 of a LTSP client onto the LTSP server
18:55
not as root tho'
18:55
why would that matter?
18:59
Maybe i should try PAM_AUTH_TYPE=0 ?
19:01
Hmm no, that disables sshfs
19:08
<alkisg>
Because sshfs doesn't work if ssh doesn't work
19:09
<danboid>
So will I have to switch to using NFS for the home dirs toget this to work?
19:10lucascastro has joined IRC (lucascastro!~lucascast@177-185-131-162.corp.isotelco.net.br)
19:10
<danboid>
Are there any disadvantages to using NFS vs SSHFS fo rthe home dirs?
19:10
<alkisg>
With PAM_AUTH_TYPE=Additional, you should be able to login to vt2 even if sshfs didn't work
19:10
I.e. even if pamltsp isn't working, your own pam should allow the login
19:13
<danboid>
Im getting the same sshfs mount error using Additional but I can ssh into the LTSP server fine
19:13
<alkisg>
It's not an ltsp issue then
19:13
it's bad pam configuration
19:17
<danboid>
Ive only configured nslcd. You mean my nslcd config is bad or is there something else I need to configure?
19:18
I installed libpam-ldapd
19:18
as part of installing nslcd
19:20
https://paste.ubuntu.com/p/XprmJF87KY/
19:20
Thats my nslcd config
19:21
I realise youve prob never used nslcd but you might spot something?
19:21
I removed the password obvs
19:29
<alkisg>
I mean that with PAM_AUTH_TYPE=0, YOU are responsible to have the clients login work, as ltsp then isn't involved at all
19:29
And if that isn't working, then you need to fix pam
19:30
<danboid>
OK well I didnt test 0, Ive only bben tryinh with Additional
19:31
<alkisg>
It's pretty much the same
19:31
additional means "stuff to do after the login succeeds"
19:31
<danboid>
Id have to read up on NFS before I try 0 tho as Ive never really used it
19:31
<alkisg>
So you should be able to login even without a mounted home
19:32
And it will tell you "no home, logging in with HOME=/"
19:32
AFTER you have that working, then you can look at mounting home
19:32
<danboid>
Yes, its doing that
19:32
"no home, logging in with HOME=/"
19:33
Using Additional
19:34
I can login, its just not mounting home
19:38lucascastro has left IRC (lucascastro!~lucascast@177-185-131-162.corp.isotelco.net.br, Ping timeout: 256 seconds)
19:39lucascastro has joined IRC (lucascastro!~lucascast@177-185-131-162.corp.isotelco.net.br)
19:44lucascastro has left IRC (lucascastro!~lucascast@177-185-131-162.corp.isotelco.net.br, Ping timeout: 240 seconds)
19:50danboid has left IRC (danboid!~danboid@146.87.136.62, Quit: Client closed)
20:33ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
20:51p00l3r has joined IRC (p00l3r!~p00l3r@190-82-246-246.adsl.tie.cl)
20:56
<p00l3r>
hi i have some problem with ltsp, im a user of a server with an image of ubuntu without pass of root or superuser, but when i installed virtualbox and created an ubuntu machine the problem is inside of the VM dont work the share file or usb (the guset addittion and extension pack are instaalled), someone can help me about this
20:56
thanks
20:57vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e)
20:57
<p00l3r>
in the host i dont have the problem of usb, just on VM (guest)
20:58
disculpen mi ingles xD
20:59
<vagrantc>
no hay problema :)
21:02
p00l3r: i missed what you said earlier ... what is the problem with usb ?
21:11
<alkisg>
p00l3r: you mean that you have a virtualbox issue? There's a #vbox IRC channel afaik
21:13
Also AFAIK to do USB forwarding, your user needs to be a member of the vboxusers group
21:13
But ask in #vbox, they'll tell you, it's not an LTSP issue
22:00lucascastro[m] is now known as LucasCastro[m]
23:28bcg_ has left IRC (bcg_!~b@dg4ybwyyyyyyyyyyyyyyt-3.rev.dnainternet.fi, Ping timeout: 268 seconds)
23:49bcg_ has joined IRC (bcg_!~b@dg4ybwyyyyyyyyyyyyyyt-3.rev.dnainternet.fi)