00:55 | TheProf has joined IRC (TheProf!TheProf@72.53.213.81) | |
00:56 | <TheProf> Hello. I hope everyone is well. I am trying to use pwmerge to migrate my users from my old LTSP server to my new one. I think I got it to work but I have two questions please:
| |
00:56 | a) does it reset or does it migrate the password and
| |
00:56 | b) how can I get it to skip a user who exists on both?
| |
00:57 | For b) the administrator account on the new server is different from the old one, so the script is assigning someone else as user 1000 and moving the new user 1000 to 14000 I am not sure if that is OK or will mess up my ability to log in
| |
01:00 | the script is found in /usr/share/ltsp/client/login/pwmerge
| |
02:22 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
03:51 | <alkisg> TheProf: (a) => it can do either, (b) => with -dur or -sur
| |
03:52 | <TheProf> alkisg: Hello. for (b) -dur or -sur can I reference it as -dur="username" ? The instructions mention regex but I have no idea where to start with that :)
| |
03:54 | <alkisg> -dur=username means "keep this destination user"
| |
03:54 | Which administrator user do you want to preserve, the source or the destination?
| |
03:55 | <TheProf> The destination
| |
03:56 | <alkisg> Try --sur="^(?!administrator)" --dur="administrator"
| |
03:57 | <TheProf> Thank you.
| |
03:57 | With regards to (a), the password, is the default to migrate the password over as well?
| |
03:57 | <alkisg> Yes
| |
03:59 | <TheProf> Great thank you. I was seeing text related to pamltsp which I was unclear of what it meant
| |
03:59 | <alkisg> In ltsp mode, the default is not to migrate passwords, but you're not using --ltsp mode
| |
04:00 | <TheProf> I think that may have been my issue. Since both machines are LTSP servers I put --ltsp mode
| |
04:00 | <alkisg> ltsp mode is for creating the ltsp.img, not for migrating users
| |
04:00 | <TheProf> Ahhhh I see.
| |
04:01 | That explains it.
| |
04:04 | So I would run it without the --ltsp flag, then update the image on the server as per usual.
| |
04:07 | <alkisg> LTSP image updating? This should be a completely unrelated task...
| |
04:08 | <TheProf> Sorry I meant after updating the users and groups do I need to update the image pushed to the clients to reflect this or is it automatic?
| |
04:09 | <alkisg> In the new ltsp, every time a user is added or removed to the server, we need to run: ltsp initrd
| |
04:09 | This takes a second
| |
04:09 | There's no need for ltsp image
| |
04:10 | <TheProf> OK I understand. Thank you.
| |
04:33 | lucas_ has joined IRC (lucas_!~lucascast@186.193.183.215.jupiter.com.br) | |
04:36 | lucascastro has left IRC (lucascastro!~lucascast@177-185-133-213.dynamic.isotelco.net.br, Ping timeout: 246 seconds) | |
04:43 | TheProf has left IRC (TheProf!TheProf@72.53.213.81) | |
06:47 | ltspbot has joined IRC (ltspbot!~supybot@devs.ts.sch.gr) | |
06:49 | RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro) | |
08:33 | Fenchi has joined IRC (Fenchi!d5b53206@213.181.50.6) | |
08:36 | Fenchi has left IRC (Fenchi!d5b53206@213.181.50.6, Remote host closed the connection) | |
08:40 | Fenchi has joined IRC (Fenchi!d5b53206@213.181.50.6) | |
08:42 | Fenchi has left IRC (Fenchi!d5b53206@213.181.50.6, Remote host closed the connection) | |
08:43 | Fenchi has joined IRC (Fenchi!d5b53206@213.181.50.6) | |
08:48 | <Fenchi> alkisg: Bonjour, sur https://github.com/ltsp/ltsp/issues/132#issuecomment-636280668 tu parles de remplacer nolock par lock. Y a-t-il une raison de ne pas avoir fait le changement ? Autre que supporter les serveurs NFS qui ne supportent pas le lock.
| |
08:48 | <alkisg> !english
| |
08:48 | <ltspbot> Error: "english" is not a valid command.
| |
08:49 | <alkisg> Fenchi: I you talk in French and me in Greek we won't really understand each other :)
| |
08:49 | Let's try both in English
| |
08:50 | <Fenchi> Sorry
| |
08:50 | alkisg: Hello, on https://github.com/ltsp/ltsp/issues/132#issuecomment-636280668 you are talking about replacing nolock with lock. Is there a reason not to have made the change? Other than supporting NFS servers which do not support the lock.
| |
08:50 | <alkisg> Fenchi: that change is outside of ltsp, it's in initramfs-tools
| |
08:51 | So if we test it and see that it works better, we'll need to file a bug in initramfs-tools to change it
| |
08:58 | <Fenchi> alkisg: I thought we could replace the locked nolock in /ltsp/client/init/25-ro-root.sh in order to change it. But this is in LTSP?
| |
08:59 | <alkisg> Fenchi: $ grep -rw nolock /usr/share/initramfs-tools
| |
08:59 | /usr/share/initramfs-tools/scripts/nfs: nfsmount -o nolock ${roflag} ${NFSOPTS} "${NFSROOT}" "${rootmnt?}"
| |
08:59 | This is the one that needs to be changed
| |
09:00 | I wonder if we can override it by passing NFSOPTS=lock
| |
09:01 | Yup, it's possible with NFSOPTS="-o lock"
| |
09:02 | Fenchi: try adding ,lock in ltsp.ipxe
| |
09:02 | set cmdline_method root=/dev/nfs nfsroot=${srv}:/srv/ltsp,lock ltsp.image=images/${img}.img loop.max_part=9
| |
09:03 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection) | |
09:03 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
09:06 | <Fenchi> alkisg: I'm testing
| |
09:15 | alkisg: Client does not start
| |
09:15 | <alkisg> With what error message?
| |
09:16 | Also, which distro/version?
| |
09:17 | <Fenchi> I'm using Xubuntu 20.04
| |
09:18 | There is no error message
| |
09:19 | The client stays on : DHCPACK of xxx.xxx.xxx.xxx .................
| |
09:19 | bound to xxx.xxx.xxx.xxx -- renewal in 244 seconds.
| |
09:20 | Then only a dash
| |
09:27 | <alkisg> Can you paste your ltsp.ipxe?
| |
09:27 | !paste
| |
09:27 | <ltspbot> paste: To avoid channel flooding, please upload text longer than 3 lines to http://paste.debian.net. Don't forget to paste the resulting URL here.
| |
09:27 | <alkisg> (ignore this one now:)
| |
09:27 | !tag
| |
09:27 | <ltspbot> tag: tag: git tag -s v20.03 -m 'Version 20.03' && git push --tags
| |
09:30 | <Fenchi> ltsp.ipxe : https://paste.debian.net/1156201/
| |
09:32 | <alkisg> Fenchi: seems ok, so I guess a different method is needed to pass that "lock" option; ubuntu keeps changing them...
| |
09:41 | <Fenchi> root=/dev/nfs nfsroot=[<server-ip>:]<root-dir>[:<nfs-options>]
| |
09:41 | Yes, you must replace "," with ":"
| |
09:41 | <alkisg> Try it, they keep changing it in ubuntu
| |
09:41 | Previously they wanted a separate nfsopts
| |
09:43 | <Fenchi> Now I have this loop error: Mount call failed - server replied: Premission denied.
| |
09:45 | Then I have the debug console
| |
09:49 | I have this message in the server logs:
| |
09:49 | Jul 13 11:49:13 srv-ltspaio-ebe rpc.mountd[28535]: message repeated 2 times: [ refused mount request from 10.185.8.210 for /srv/ltsp:lock (/): not exported]Jul 13 11:49:14 srv-ltspaio-ebe rpc.mountd[28535]: refused mount request from 10.185.8.210 for /srv/ltsp:lock (/): not exported
| |
09:53 | <alkisg> Which means that : isn't correct, as it's considered a file name
| |
09:54 | # nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>]
| |
09:55 | NFSOPTS="-o ${NFSROOT#*,}"
| |
09:55 | ,lock sounds correct then
| |
09:59 | <Fenchi> With : set cmdline_method root=/dev/nfs nfsroot=${srv}:/srv/ltsp nfsopts=lock ltsp.image=images/${img}.img loop.max_part=9
| |
09:59 | The client starts correctly
| |
10:00 | But how do you check if he's using lock?
| |
10:02 | <alkisg> Put a break=bottom, and cat /proc/mounts
| |
10:02 | By default, nolock should show in the mount
| |
10:02 | 10.161.254.11:/srv/ltsp /tmp/mnt nfs rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nolock,proto=tcp,port=2049,timeo=600,retrans=3,sec=sys,local_lock=all,addr=10.161.254.11 0 0
| |
10:02 | ...hard,nolock...
| |
10:03 | (the break=bottom goes in the cmdline again)
| |
10:06 | <Fenchi> I always have nolock
| |
10:08 | <alkisg> And this won't boot? nfsroot=${srv}:/srv/ltsp,lock
| |
10:08 | This is supposed to be the correct one
| |
10:10 | <Fenchi> If it starts
| |
10:11 | But he ignored the lock
| |
10:11 | <alkisg> Are you using chrootless?
| |
10:11 | Or a chroot/vm?
| |
10:12 | <Fenchi> I use the chroot
| |
10:20 | <alkisg> Try to update the nfs script directly: $ grep -rw nolock /usr/share/initramfs-tools/
| |
10:20 | /usr/share/initramfs-tools/scripts/nfs: nfsmount -o nolock ${roflag} ${NFSOPTS} "${NFSROOT}" "${rootmnt?}"
| |
10:20 | Do that in the chroot, then run update-initramfs -u inside the chroot, etc
| |
10:30 | (i.e. to remove "-o nolock" from initramfs-tools)
| |
10:31 | `ltsp kernel` is needed, but not `ltsp image`
| |
10:36 | <Fenchi> alkisg: I made the modification but I still have nolock
| |
10:46 | alkisg: It does not matter, I will continue with nolock
| |
10:57 | The reason I'm trying to activate the lock is that I don't want to syncrhonize via rsync (as you explained, with symbolic links) but with zsync. I want to start a zsync every day but if a client has been connected for more than 2 days, it will crash. The lock of NFS is very practical to avoid the crash.I see a workaround (which is not very clean):
| |
10:57 | Mount each client a second time on the nfs server and mount the image there. It would just stop the server from deleting the file while a client is still connected to it.
| |
10:58 | alkisg: What do you think ?
| |
11:03 | mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Ping timeout: 258 seconds) | |
11:06 | <alkisg> Fenchi: sure, you can put a POST_INIT command to do that, but I imagine that you did something while removing nolock, it should work without it...
| |
11:06 | Sorry but I don't have time to test this right now, if you want comment in the github issue and I'll take a look another day
| |
11:06 | jeremy3811 has joined IRC (jeremy3811!~jeremy381@123.252.244.230) | |
11:08 | <Fenchi> D'accord pas de soucis
| |
11:08 | *Sure no worries
| |
11:08 | Many thanks for your help
| |
11:08 | <alkisg> np
| |
11:08 | jeremy3811: here
| |
11:09 | <jeremy3811> got it
| |
11:09 | I am trying to boot rw now, to run some updates, configuration changes etc on the client
| |
11:09 | <alkisg> jeremy3811: for nfsrw, don't use init=
| |
11:09 | <jeremy3811> so I changed the boot cmd to rw, nfs export is already rw
| |
11:09 | ohh got it
| |
11:10 | <alkisg> (or at least set ADMINISTRATIVE_CLIENT=1)
| |
11:11 | <jeremy3811> that would be in the [clients] section correct?
| |
11:11 | <alkisg> Yes but inside the chroot, not in /etc/ltsp on the server
| |
11:11 | As at that point, the client doesn't yet have ltsp.img
| |
11:11 | <jeremy3811> understood
| |
12:03 | Fenchi has left IRC (Fenchi!d5b53206@213.181.50.6, Remote host closed the connection) | |
12:13 | mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy) | |
12:19 | jeremy3811 has left IRC (jeremy3811!~jeremy381@123.252.244.230, Ping timeout: 256 seconds) | |
12:40 | lucascastro has joined IRC (lucascastro!~lucascast@177-185-133-213.dynamic.isotelco.net.br) | |
12:42 | lucas_ has left IRC (lucas_!~lucascast@186.193.183.215.jupiter.com.br, Ping timeout: 246 seconds) | |
13:27 | thefinn93 has left IRC (thefinn93!finn@unaffiliated/thefinn93, *.net *.split) | |
13:27 | bengoa has left IRC (bengoa!~alberto@194.50.55.200, *.net *.split) | |
13:28 | Hyperbyte has left IRC (Hyperbyte!~jan@middelkoop.cc, *.net *.split) | |
13:28 | thefinn93 has joined IRC (thefinn93!finn@unaffiliated/thefinn93) | |
13:28 | bengoa has joined IRC (bengoa!~alberto@194.50.55.200) | |
13:28 | Hyperbyte has joined IRC (Hyperbyte!~jan@middelkoop.cc) | |
13:28 | jeremy3811 has joined IRC (jeremy3811!~jeremy381@14.96.81.222) | |
14:35 | jeremy3811 has left IRC (jeremy3811!~jeremy381@14.96.81.222, Quit: Leaving) | |
16:14 | mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Ping timeout: 256 seconds) | |
17:13 | mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy) | |
17:18 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
18:22 | lucascastro has left IRC (lucascastro!~lucascast@177-185-133-213.dynamic.isotelco.net.br, Ping timeout: 240 seconds) | |
18:35 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Remote host closed the connection) | |
18:37 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
19:26 | lucascastro has joined IRC (lucascastro!~lucascast@dynamic-45-167-143-6.netfacil.inf.br) | |
19:29 | lucascastro has left IRC (lucascastro!~lucascast@dynamic-45-167-143-6.netfacil.inf.br, Remote host closed the connection) | |
19:30 | Fenchi has joined IRC (Fenchi!551b56bf@host-85-27-86-191.dynamic.voo.be) | |
19:30 | lucascastro has joined IRC (lucascastro!~lucascast@dynamic-45-167-143-6.netfacil.inf.br) | |
19:31 | Fenchi has left IRC (Fenchi!551b56bf@host-85-27-86-191.dynamic.voo.be, Remote host closed the connection) | |
19:36 | lucascastro has left IRC (lucascastro!~lucascast@dynamic-45-167-143-6.netfacil.inf.br, Ping timeout: 240 seconds) | |
19:44 | RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.) | |
20:19 | lucascastro has joined IRC (lucascastro!~lucascast@177-185-133-213.dynamic.isotelco.net.br) | |
23:10 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Remote host closed the connection) | |
23:12 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
23:33 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Ping timeout: 260 seconds) | |
23:34 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
23:44 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |