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


Channel log from 25 February 2019   (all times are UTC)

05:40tjfwalker_ has joined IRC (tjfwalker_!b280e58f@gateway/web/freenode/ip.178.128.229.143)
05:43tjfwalker has joined IRC (tjfwalker!~tj@178.128.229.143)
05:45tjfwalker_ has left IRC (tjfwalker_!b280e58f@gateway/web/freenode/ip.178.128.229.143)
06:05tjfwalker has left IRC (tjfwalker!~tj@178.128.229.143, Ping timeout: 246 seconds)
06:36statler has joined IRC (statler!~Georg@p5489790B.dip0.t-ipconnect.de)
06:56ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:00GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Ping timeout: 268 seconds)
08:01kjackal has joined IRC (kjackal!~quassel@194.158.46.138)
08:12kjackal has left IRC (kjackal!~quassel@194.158.46.138, Ping timeout: 268 seconds)
08:13kjackal has joined IRC (kjackal!~quassel@conference/ubuntuengineering/x-jwaoirivqncouehu)
08:42uumas_ has joined IRC (uumas_!b9260201@gateway/web/freenode/ip.185.38.2.1)
08:46uumas_ has left IRC (uumas_!b9260201@gateway/web/freenode/ip.185.38.2.1, Client Quit)
08:58statler has left IRC (statler!~Georg@p5489790B.dip0.t-ipconnect.de, Remote host closed the connection)
09:38bengoa has joined IRC (bengoa!~alberto@194.50.55.200)
10:05uumas has joined IRC (uumas!55c2d89c@gateway/web/freenode/ip.85.194.216.156)
10:09
<uumas>
I'm setting up a new ltsp server and got it booting clients, but the clients don't get their hostnames from my dhcp server, but just use the generic ltspXX hostnames. I know the issue isn't with the dhcp server, because clients booted from another ltsp server get their hostnames just fine
10:13
<alkisg>
!ipappend
10:13
<ltsp>
ipappend: o temporarily solve DHCP problems in the initramfs, try putting IPAPPEND 3 after the APPEND line in /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default. More info: http://www.syslinux.org/wiki/index.php/SYSLINUX#IPAPPEND_flag_val_.5BPXELINUX_only.5D
10:13
<alkisg>
uumas: ltsp started defaulting to ipappend 3
10:13
This makes the clients skip the second dhcp request that gets the hostname etc
10:14
So you need to revert back to ipappend 2
10:14
(or, set the hostnames in lts.conf instead of in dhcp)
10:15
<uumas>
Ok, thanks. Why was that change made?
10:15
<alkisg>
It's needed for proxydhcp, which is the default and most common case nowadays
10:15
Otherwise proxydhcp setups don't work
10:16
(the ltsp clients don't know how to contact proxydhcp servers unless ipappend 3 passes a hardcoded ip in the kernel cmdline)
10:18
<uumas>
It seems I need to edit /etc/ltsp/update-kernels.conf right?
10:18
<alkisg>
chrootless or with chroot?
10:19
<uumas>
Without
10:19
<alkisg>
Then yes you edit /etc/ltsp/update-kernels.conf, and then you run ltsp-update-image -c /
10:20
Sorry
10:20
<uumas>
Great, thank you!
10:20
<alkisg>
you edit /etc/ltsp/update-kernels.conf, you run /usr/share/ltsp/update-kernels, and then you run ltsp-update-image -c /
10:20
uumas: ^
10:20
3 steps involved
10:20
<uumas>
Ok
10:20
<alkisg>
The pxe setup was trying to be too clever, and it ended up being hard to use
10:21
In the new one it'll just be a user editable file :D
10:22
<uumas>
What's the difference between running /usr/share/ltsp/update-kernels and ltsp-update-kernels
10:23
<alkisg>
One is run in the chroot, the other on the server
10:23
It's complicated :)
10:24* alkisg explained it in the ltsp-discuss mailing list a few times, but got tired for too many repeats :D
10:28statler has joined IRC (statler!~Georg@gwrz3.lohn24.de)
10:33uumas has left IRC (uumas!55c2d89c@gateway/web/freenode/ip.85.194.216.156, Quit: Page closed)
11:34kjackal has left IRC (kjackal!~quassel@conference/ubuntuengineering/x-jwaoirivqncouehu, Ping timeout: 255 seconds)
11:41uumas has joined IRC (uumas!55c2d89c@gateway/web/freenode/ip.85.194.216.156)
11:47uumas has left IRC (uumas!55c2d89c@gateway/web/freenode/ip.85.194.216.156, Quit: Page closed)
11:49Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
11:50uumas has joined IRC (uumas!b9260203@gateway/web/freenode/ip.185.38.2.3)
11:56
<uumas>
After changing the ipappend setting and updating kernels and image, it starts booting, shows ip-config: ens3 complete with the correct hostname, but drops into a initramfs shell saying: Failure: Insufficient information setting up nbd, quitting (nbdroot=, hostname=<correct ltsp server ip>, name=, port=, nbd-device=/dev/nbd0)
12:16
<Faith>
uumas, what is on your dhcpd.conf?
12:18uumas has left IRC (uumas!b9260203@gateway/web/freenode/ip.185.38.2.3, Quit: Page closed)
12:19uumas has joined IRC (uumas!55c2d89c@gateway/web/freenode/ip.85.194.216.156)
12:19
<uumas>
It doesn't exist
12:20
in /etc/ltsp/ at least
12:21
<Faith>
are you using dnsmasq ou isc dhcp?
12:21
or*
12:21
<uumas>
I'm using isc-dhcp on a separate dhcp server
12:23kjackal has joined IRC (kjackal!~quassel@conference/ubuntuengineering/x-cvtwnqhuqyxmyilk)
12:23
<Faith>
you have to put the image information on the dhcpd.conf, on your dhcp server
12:24
<uumas>
I have filename and next-server set
12:25
The same setup works for the old ltsp server
12:25
<Faith>
you have to use option root-path too
12:25
like:
12:25
filename "/ltsp/chrootname-amd64/pxelinux.0";
12:25
option root-path "/opt/ltsp/chrootname-amd64";
12:25
filename is the path from tftp
12:26
and option root-path is the path for the image
12:28
<uumas>
I have chrootless setup so do I just set root-path "/"
12:32
<Faith>
alkisg, is it possible to use nbd with chrootless?
12:54
<uumas>
It boots fine with ipappend=3, but doesn't get hostname (or it seems dns) from dhcp. The clients are also able to boot from the old ltsp server, which has ipappend=2, has a chroot and has no option root-path setting either.
12:56uumas_ has joined IRC (uumas_!b9260203@gateway/web/freenode/ip.185.38.2.3)
12:57uumas__ has joined IRC (uumas__!554c2bcb@gateway/web/freenode/ip.85.76.43.203)
12:59uumas has left IRC (uumas!55c2d89c@gateway/web/freenode/ip.85.194.216.156, Ping timeout: 256 seconds)
13:00uumas_ has left IRC (uumas_!b9260203@gateway/web/freenode/ip.185.38.2.3, Ping timeout: 256 seconds)
13:03
<Faith>
uumas, I got it wrong, I thought it's not booting. Well, if the problem is the hostname, it's not to do with nbd options...
13:06spaced0ut has joined IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut)
13:20uumas__ has left IRC (uumas__!554c2bcb@gateway/web/freenode/ip.85.76.43.203, Quit: Page closed)
13:33uumas has joined IRC (uumas!2e84bf08@gateway/web/freenode/ip.46.132.191.8)
13:35
<uumas>
With ipappend=3 it doesn't get the hostname from DHCP but boots fine
13:35
With ipappend=2 it gets the hostname but doesn't boot
13:47uumas has left IRC (uumas!2e84bf08@gateway/web/freenode/ip.46.132.191.8, Ping timeout: 256 seconds)
14:04
<alkisg>
(02:32:03 PM) Faith: alkisg, is it possible to use nbd with chrootless? => yes, nbd is actually the only current choice with chrootless
14:08
<Faith>
really? I thought it was nfs, cause you need to build an image to use nbd, so I imagined people use chrootless to make changes on server and it's already on clients...
14:08
I always used chroot with nbd, never try chrootless...
14:10
<alkisg>
Faith: ltsp-update-image -c /, takes a snapshot of the server, cleans it up from sensitive information, and exports it via nbd
14:23
<Faith>
alkisg, it makes sense, case if you use nfs you will export all the system with the sensitive informations...
15:05kjackal has left IRC (kjackal!~quassel@conference/ubuntuengineering/x-cvtwnqhuqyxmyilk, Ping timeout: 250 seconds)
15:51kjackal has joined IRC (kjackal!~quassel@conference/ubuntuengineering/x-kpmzelnrunlgfwvh)
16:17uumas has joined IRC (uumas!2e84bf08@gateway/web/freenode/ip.46.132.191.8)
16:40GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net)
16:48kjackal has left IRC (kjackal!~quassel@conference/ubuntuengineering/x-kpmzelnrunlgfwvh, Ping timeout: 250 seconds)
16:54
<alkisg>
uumas: ok with ipappend?
16:58
<uumas>
No luck, still getting the same error as earlier
16:58
Failure: Insufficient information setting up nbd, quitting (nbdroot=, hostname=<correct ltsp server ip>, name=, port=, nbd-device=/dev/nbd0)
16:58
And then it drops me into an initramfs shell
17:03kjackal has joined IRC (kjackal!~quassel@conference/ubuntuengineering/x-zyuqtqmbehdjohdy)
17:06
<uumas>
I'm kind of stuck with this now, because I can't find the difference between the old server's configs and the new ones that makes the difference
17:14
<alkisg>
uumas: what's the output of this, on the client?
17:14
ipconfig -n enp2s0
17:14
Actually run this on the server:
17:14
/usr/lib/klibc/bin/ipconfig -n enp2s0 | nc termbin.com 9999
17:14
And paste the output
17:15
So that we see if your server is configured properly
17:15
*dhcp server
17:18
<uumas>
Here you go: https://pastebin.com/SK3nk1Yc
17:19
I changed the interface name to be correct and snipped a few possibly sensitive details
17:31
Here's the same run on a client: https://pastebin.com/T4JfjMiD
17:33
The client was booted from the old ltsp server and that's why it's eth0 rather than the new format
17:41
<alkisg>
uumas: so your dhcp server doesn't return the filename
17:41
fix your dhcp server
17:53
<uumas>
It does, just not for the server (and it isn't supposed to). Look at the paste from the client
17:53
<alkisg>
uumas: it doesn't return a rootpath on the client
17:53
So the client doesn't know where to mount nbd from
17:54
Send rootpath=/opt/ltsp/amd64 there
17:54
<uumas>
That path doesn't exist, because it's chrootless
17:54
<alkisg>
It refers to the nbd mount
17:54
It's the header of /etc/nbd-server/conf.d/ltsp_amd64.conf
17:59
!nbd-client
17:59
<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
17:59
<alkisg>
So, the client needs it to run that ^ command at that point where it breaks for you
18:00
<uumas>
Hmm, I'll try that. Any idea why it's working for the older ltsp server without needing that?
18:01
<alkisg>
There's been a change to prefer BOOT_IMAGE from the client cmdline
18:01
If you paste the output of `cat /proc/cmdline` from old/new client, I'll be able to tell you exactly
18:02
(otherwise, it falls back to /opt/ltsp/<ARCH>, so the fallback was on effect on the old server)
18:12
<uumas>
Success! (I think). The test machine (a kvm virtual machine) still doesn't manage to boot on the new server, but starts throwing squashfs errors before it completes boot, but that happened earlier also, so I'll have to test tomorrow when I have access to the physical clients to make sure.
18:17
I can't get the new /proc/cmdline now, but this is what it's based on right: https://pastebin.com/aJYdPbyL
18:25
<alkisg>
Yeah it doesn't have a path there, so it's justified
18:26kjackal has left IRC (kjackal!~quassel@conference/ubuntuengineering/x-zyuqtqmbehdjohdy, Ping timeout: 255 seconds)
18:42uumas has left IRC (uumas!2e84bf08@gateway/web/freenode/ip.46.132.191.8, Ping timeout: 256 seconds)
19:06spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Quit: Leaving)
19:27vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
19:29
<alkisg>
"liveclone", how does that sound for a new name? :P :D
19:31
...or, "twinboot"?
19:31
I don't think there are *any* 4 letter project names left unclaimed in github...
19:47
<vagrantc>
context?
19:50kjackal has joined IRC (kjackal!~quassel@conference/ubuntuengineering/x-mvsvsljpmtpffolz)
19:56vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 250 seconds)
20:02statler has left IRC (statler!~Georg@gwrz3.lohn24.de, Remote host closed the connection)
20:13vsuojanen has left IRC (vsuojanen!~vsuojanen@cable-hml-585686-205.dhcp.inet.fi, Ping timeout: 246 seconds)
20:15vsuojanen has joined IRC (vsuojanen!~vsuojanen@cable-hml-585686-205.dhcp.inet.fi)
20:44vsuojanen has left IRC (vsuojanen!~vsuojanen@cable-hml-585686-205.dhcp.inet.fi, Ping timeout: 246 seconds)
20:46vsuojanen has joined IRC (vsuojanen!~vsuojanen@cable-hml-585686-205.dhcp.inet.fi)
20:47Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
20:48ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)
20:54white-wizard has joined IRC (white-wizard!~white-wiz@82.16.136.77.rev.sfr.net)
20:54
<white-wizard>
hi
20:54
i would like install an ltsp server en thin client over the adsl connexion... it's possible ?
20:54
and*
20:55
s/en/and
20:55
for my mother and me
21:00
<mwalters>
white-wizard: you're probably better off just using x2go/rdp
21:01
let me rephrase, you're definitely better off just using x2go/rdp ;)
21:07
<alkisg>
You can install over adsl, you cannot use ltsp over adsl:D
21:08
<white-wizard>
ok
21:23telex has joined IRC (telex!teletype@94.247.40.156)
21:33adrianorg has left IRC (adrianorg!~adrianorg@189.58.236.27.dynamic.adsl.gvt.net.br, Ping timeout: 250 seconds)
21:33adrianorg has joined IRC (adrianorg!~adrianorg@189.58.236.27.dynamic.adsl.gvt.net.br)
22:07kjackal has left IRC (kjackal!~quassel@conference/ubuntuengineering/x-mvsvsljpmtpffolz, Ping timeout: 245 seconds)