IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 5 February 2019 (all times are UTC)
| 00:47 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 04:26 | GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Read error: Connection reset by peer) | |
| 04:42 | GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net) | |
| 05:20 | quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: WeeChat 2.2) | |
| 05:49 | <alkisg> !client-list
| |
| 05:49 | <ltsp> client-list: to get a list of all nbd-clients (which sometimes is the same as ltsp clients), run: ss -n | sed -n 's/.*:10809 *\([0-9.]*\):.*/\1/p' | sort -Vu
| |
| 06:02 | kjackal has joined IRC (kjackal!~quassel@109.236.135.66) | |
| 06:27 | kjackal has left IRC (kjackal!~quassel@109.236.135.66, Ping timeout: 240 seconds) | |
| 06:28 | kjackal has joined IRC (kjackal!~quassel@109.236.135.66) | |
| 06:49 | kjackal has left IRC (kjackal!~quassel@109.236.135.66, Ping timeout: 240 seconds) | |
| 06:57 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 07:49 | kjackal has joined IRC (kjackal!~quassel@193.191.158.60) | |
| 08:52 | statler has joined IRC (statler!~Georg@gwrz.lohn24.de) | |
| 09:55 | kjackal has left IRC (kjackal!~quassel@193.191.158.60, Ping timeout: 272 seconds) | |
| 10:10 | kjackal has joined IRC (kjackal!~quassel@193.191.158.60) | |
| 10:56 | Faith has joined IRC (Faith!~Paty_@unaffiliated/faith) | |
| 11:05 | GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Ping timeout: 245 seconds) | |
| 11:12 | GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net) | |
| 12:07 | kjackal has left IRC (kjackal!~quassel@193.191.158.60, Ping timeout: 246 seconds) | |
| 12:42 | <statler> Test debian buster on client:
| |
| 12:42 | Server does not support NBD_OPT_GO and dropped connection after sending NBD_OPT_EXPORT_NAME. Try -g
| |
| 12:43 | nbd-client or nbd-server doesnt have an option -g
| |
| 12:51 | <alkisg> statler: that usually means that you didn't configure /etc/nbd-server/conf.d correctly,or that you're using the wrong name
| |
| 12:51 | !nbd-client
| |
| 12:51 | <ltsp> nbd-client: To try mounting the NBD image from the client initramfs: nbd-client 192.168.67.1 -N /opt/ltsp/i386 /dev/nbd0
| |
| 12:51 | <alkisg> Use this command line to test
| |
| 12:52 | And pastebin your nbd-server configuration
| |
| 12:59 | <statler> alkisg, the clients with debian-stretch-image doesn't have problems
| |
| 12:59 | now testet with nfs instead of nbd works
| |
| 13:07 | To try mounting the NBD image from the client: "unrecognized Option `-g`" :-D
| |
| 13:07 | https://github.com/NetworkBlockDevice/nbd/blob/master/nbd-client.c#L469
| |
| 13:12 | found in syslog: Negotiation failed/8a: Requested export not found, or is TLS-only and client did not negotiate TLS
| |
| 13:14 | is it possible to increase the verbosity?
| |
| 13:20 | <alkisg> statler: please answer the questions , other wise it takes a long time
| |
| 13:20 | grep -r . /etc/nbd-server | nc termbin.com 9999
| |
| 13:21 | kjackal has joined IRC (kjackal!~quassel@193.191.158.62) | |
| 13:22 | JuJUBee has joined IRC (JuJUBee!~knichel@24.148.115.153) | |
| 13:22 | <alkisg> It's the first part, "export not found", because your configuration is wrong
| |
| 13:23 | No need to try stretch or whatever, just paste your configuration so that we see its error
| |
| 13:23 | <JuJUBee> Is it OK to update-image while users are logged in?
| |
| 13:23 | <alkisg> Yes
| |
| 13:23 | Clients will get the image on the next reboot
| |
| 13:24 | <JuJUBee> alkisg, thanks, I just keep getting errors about file size changed attempting to re-read...
| |
| 13:24 | <alkisg> Which files? Are they in /home?
| |
| 13:24 | E.g. if you update the image while running apt update... shame on you :D
| |
| 13:25 | Or if you have web server data files and you didn't exclude them from the image
| |
| 13:25 | <JuJUBee> mostly in /tmp
| |
| 13:25 | Don't recall if any others...
| |
| 13:25 | <alkisg> /tmp should be excluded from the image anyway
| |
| 13:26 | Check /etc/ltsp/ltsp-update-image.conf, /tmp should be there already
| |
| 13:26 | ltsp-update-image.excludes
| |
| 13:28 | <JuJUBee> Yep, its there
| |
| 13:35 | <statler> https://termbin.com/imkjt
| |
| 13:36 | <alkisg> statler: and what nbd-client connect command did you try?
| |
| 13:37 | !nbd-client
| |
| 13:37 | <ltsp> nbd-client: To try mounting the NBD image from the client initramfs: nbd-client 192.168.67.1 -N /opt/ltsp/i386 /dev/nbd0
| |
| 13:37 | <alkisg> nbd-client 192.168.67.1 -N /opt/ltsp/buster /dev/nbd0
| |
| 13:37 | <statler> yes
| |
| 13:37 | <alkisg> Try it now
| |
| 13:38 | And also check that /opt/ltsp/images/buster.img is there
| |
| 13:38 | Of course, put your server IP there
| |
| 13:38 | <statler> sure ;)
| |
| 13:38 | <alkisg> Finally, I assume you restarted your nbd-server after generating that export
| |
| 13:38 | <statler> the image is there
| |
| 13:39 | <alkisg> OK, then it's not related to ltsp; it's just plain nbd-server and nbd-client
| |
| 13:39 | If you can't connect them, it's an nbd issue, but I bet you mistype something
| |
| 13:39 | Or you didn't restart nbd-server, etc etc
| |
| 13:40 | <statler> the nbd-server was restarted
| |
| 13:40 | <alkisg> And you run that command from the ltsp client initramfs
| |
| 13:40 | And it can ping the server
| |
| 13:40 | And the nbd server can access the /opt/ltsp/images/buster.img image
| |
| 13:41 | (e.g. it's not a file permissions issue)
| |
| 13:41 | <statler> when i boot the stable debian stretch everything goes fine
| |
| 13:41 | <alkisg> That tell me nothing though
| |
| 13:41 | If you can't connect nbd-client with nbd-server in buster, it's an nbd bug
| |
| 13:41 | You can try from another client if you want
| |
| 13:42 | <statler> the diofeerent between the images is the version of the nbd-client
| |
| 13:42 | <alkisg> So that you verify it's not related to nbd
| |
| 13:42 | Yes, I can accept an nbd bug, but I've seen that issue multiple times due to mistypes etc
| |
| 13:42 | Here's a test
| |
| 13:42 | Put break=mount while booting the buster client
| |
| 13:42 | Sorry
| |
| 13:43 | The stretch client
| |
| 13:43 | <statler> in debian strecht (stable) it ist 3.15.2-3
| |
| 13:43 | <alkisg> If you can connect to the buster image at the initramfs> prompt there, it's a good proof that it's an nbd-client regression
| |
| 13:43 | <statler> in debian buster it is 3.18-1
| |
| 13:43 | 3.15 works fine
| |
| 13:43 | 3.18 gives the error
| |
| 13:43 | <alkisg> I know that 1:3.16.2-1ubuntu works
| |
| 13:43 | I don't know about 3.18
| |
| 13:44 | But you can test like I said above ^
| |
| 13:44 | And if it's an nbd regression, you can file a bug in the nbd github bug tracker
| |
| 13:44 | I've filed 5-6 regression bugs already there :)
| |
| 13:45 | <statler> where to put the break=mount?
| |
| 13:45 | <alkisg> Boot the stretch client with "break=mount" in the kernel cmdline, and see if you can connect to the buster image from there
| |
| 13:45 | !quiet
| |
| 13:45 | <ltsp> quiet: to enable the Debian kernel and initramfs to show up more messages, in order to better troubleshoot the boot process, remove "quiet" from /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default
| |
| 13:45 | <statler> ah ok
| |
| 13:45 | <alkisg> There; instead of quiet put break
| |
| 13:46 | <statler> i do this in the evening, when no one is in office ;)
| |
| 13:46 | <alkisg> Sure
| |
| 13:46 | You can also test in MVs
| |
| 13:46 | *VMs
| |
| 13:46 | I.e. just have any buster machine with nbd-client, connect to another buster machine with nbd-server
| |
| 13:46 | There's no need to involve ltsp at all
| |
| 13:50 | <statler> the nbd-server is 3.15
| |
| 13:51 | <alkisg> statler: ah, ok, this changes things
| |
| 13:51 | <statler> i only test on the clinet side
| |
| 13:51 | <alkisg> I did report a regression like that in nbd
| |
| 13:51 | Let me find it
| |
| 13:51 | <statler> is 3.18 clinet incompatible with 3.15 server?
| |
| 13:51 | <alkisg> Something like that, let me get you the report
| |
| 13:52 | https://github.com/NetworkBlockDevice/nbd/issues/66
| |
| 13:53 | <statler> i have found this but i got another error in syslog
| |
| 13:54 | and i dont understand where to put this magic "-g"-option
| |
| 13:55 | the 3.18-client does not know the -g
| |
| 13:55 | <alkisg> You can comment about all those in the bug report that I linked
| |
| 13:55 | I can help you with the ltsp code, not the nbd code
| |
| 13:55 | You need to talk to wouter about the nbd code
| |
| 13:56 | In the meanwhile, I believe buster <=> buster should work
| |
| 13:56 | It's the stretch <=> buster that has the issue
| |
| 14:02 | <statler> ok
| |
| 14:02 | thank you
| |
| 14:03 | nfs work, then i can use nfs for this test-client
| |
| 14:54 | GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Ping timeout: 250 seconds) | |
| 15:06 | kjackal has left IRC (kjackal!~quassel@193.191.158.62, Ping timeout: 245 seconds) | |
| 15:12 | adrianorg has left IRC (adrianorg!~adrianorg@186.215.19.173, Ping timeout: 240 seconds) | |
| 15:12 | adrianorg has joined IRC (adrianorg!~adrianorg@186.215.19.173) | |
| 15:21 | Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Read error: Connection reset by peer) | |
| 15:37 | Faith has joined IRC (Faith!~Paty_@unaffiliated/faith) | |
| 16:13 | kjackal has joined IRC (kjackal!~quassel@193.191.158.60) | |
| 16:24 | kjackal has left IRC (kjackal!~quassel@193.191.158.60, Remote host closed the connection) | |
| 16:36 | kjackal has joined IRC (kjackal!~quassel@193.191.158.60) | |
| 16:54 | GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net) | |
| 16:58 | kjackal has left IRC (kjackal!~quassel@193.191.158.60, Ping timeout: 272 seconds) | |
| 17:19 | GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Remote host closed the connection) | |
| 17:20 | GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net) | |
| 17:36 | kjackal has joined IRC (kjackal!~quassel@109.236.135.66) | |
| 18:17 | <mwalters> are there any considerations I'd need to think about if I wanted to use LUKS to encrypt /home? (Beyond having to unlock it every boot)
| |
| 18:17 | default home mounts (not nfs)
| |
| 18:52 | adrianor1 has joined IRC (adrianor1!~adrianorg@187.58.140.54) | |
| 18:55 | adrianorg has left IRC (adrianorg!~adrianorg@186.215.19.173, Ping timeout: 240 seconds) | |
| 19:04 | <alkisg> Whole of /home or /home/username?
| |
| 19:04 | Just make sure you don't need pam to unlock it from ldm
| |
| 19:04 | As ldm doesn't support pam
| |
| 19:40 | <Hyperbyte> alkisg, I think he only has to unlock it once during boot of the server.
| |
| 19:43 | Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving) | |
| 19:53 | <mwalters> yeah, at rest encryption of /home
| |
| 20:30 | statler has left IRC (statler!~Georg@gwrz.lohn24.de, Remote host closed the connection) | |
| 22:11 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection) | |
| 22:33 | kjackal has left IRC (kjackal!~quassel@109.236.135.66, Remote host closed the connection) | |
| 22:34 | kjackal has joined IRC (kjackal!~quassel@109.236.135.66) | |