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


Channel log from 13 August 2014   (all times are UTC)

00:04map7 has joined IRC (map7!~map7@teksup41.lnk.telstra.net)
00:31andygraybeal has joined IRC (andygraybeal!~andy@h229.229.22.98.dynamic.ip.windstream.net)
00:42
<map7>
I've setup a LTSP-PNP system under Xbuntu 14.04 and I can boot my fat client, but I cannot access the internet
00:42
I can do a dns lookup using dig
00:42
but I cannot ping an outside IP address such as 8.8.8.8
00:44
<vagrantc>
two network cards in your server, or one?
00:44
<map7>
just one
00:44
here is my dnsmasq ltsp-server-dnsmasq.conf file http://pastie.org/9468560
00:47
here is my lts.conf file http://pastie.org/9468562
00:47
I'm setting the DNS in my lts.conf file
00:48
If I boot a none thin client on the network, it gets it's DHCP & DNS configured correctly from the ltsp server
00:49
<vagrantc>
so your LTSP server is handling DHCP?
00:49
<map7>
yes through dnsmasq
00:50
all other DHCP servers have been turned off on the network
00:50
and any VPN connections have been closed
00:50
<vagrantc>
from a client: traceroute -n 8.8.8.8
00:51
map7: and what's in the client's /etc/resolv.conf ?
00:51* vagrantc has to head out soon
00:52
<vagrantc>
map7: try with one or the other DNS_SERVER
00:52
map7: i.e. DNS_SERVER=8.8.8.8
00:52
map7: in lts.conf
00:52
<map7>
I don't have traceroute installed yet, in the resolv.conf I've got nameserver 8.8.8.8 & nameserver 208.67.222.222
00:53
<vagrantc>
nevermind, on that, it should support multiple entries in DNS_SERVER
00:53
well, traceroute will help you figure out where it's not routing...
00:54
<map7>
yep installing now, just have to redo the image
00:54
and reboot the thin client.
00:56* map7 rebuilding image...
00:59* map7 booting thin client
01:03
<map7>
vagrantc, I just get a heap of asterisks when using traceroute -n 8.8.8.8
01:03
from 1 to 30
01:04
dig debian.org seems to be failing with a timed out now on the thin client.
01:04
but works on the server
01:08
I'm using dnsmasq 2.68-1, that should be ok shouldn't it?
01:13
<vagrantc>
it's a routing problem, not a dnsmasq problem, per se.
01:13
anyways, hopefully someone can help you sort it out, i have to head out
01:14
<map7>
vagrantc, cool thanks for pointing me in the right direction, I'll have a look at the routing table
01:14
<vagrantc>
my guess is somehow it's getting told to use a broken route
01:14
which might be a dnsmasq configuration issue
01:15vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
01:23map7_ has joined IRC (map7_!~map7@teksup41.lnk.telstra.net)
01:27map7_ has left IRC (map7_!~map7@teksup41.lnk.telstra.net, Client Quit)
01:37||cw has left IRC (||cw!~chris@phpgroupware/cw, Ping timeout: 240 seconds)
01:50||cw has joined IRC (||cw!~chris@phpgroupware/cw)
03:00
<map7>
The default route is different on the client than that on the server, could this be the cause of my issues?
03:22
Still cannot ping the outside world from a fat client.
03:23
I'm still thinking that it's something to do with the dnsmasq config.
03:54adrianorg has left IRC (adrianorg!~adrianorg@179.179.74.164, Ping timeout: 255 seconds)
03:55adrianorg has joined IRC (adrianorg!~adrianorg@179.179.74.164)
05:31alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
05:43vsuojanen has left IRC (vsuojanen!~valtteri@pc-37-238.cable.aina.net, Remote host closed the connection)
05:57
<alkisg>
!learn alkisg-todo fix vendor:pxe in ltsp-server-dnsmasq.conf and add more options
05:57
<ltsp>
(learn [<channel>] <key> as <value>) -- Associates <key> with <value>. <channel> is only necessary if the message isn't sent on the channel itself. The word 'as' is necessary to separate the key from the value. It can be changed to another word via the learnSeparator registry value.
05:57
<alkisg>
!learn alkisg-todo as fix vendor:pxe in ltsp-server-dnsmasq.conf and add more options
05:57
<ltsp>
The operation succeeded.
06:06
<alkisg>
!learn alkisg-todo as change COMPRESS=gzip (19899456 bytes) to either lzma (14710842) or xz (14633624), in /etc/initramfs-tools/initramfs.conf
06:06
<ltsp>
The operation succeeded.
06:14vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
06:21vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
06:23||cw has left IRC (||cw!~chris@phpgroupware/cw, Ping timeout: 240 seconds)
06:32alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)
06:36||cw has joined IRC (||cw!~chris@phpgroupware/cw)
06:53alexxtasi has joined IRC (alexxtasi!~alex@unaffiliated/alexxtasi)
07:51cyberorg_ has joined IRC (cyberorg_!~cyberorg@opensuse/member/Cyberorg)
07:53cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 255 seconds)
08:33xiphias256 has left IRC (xiphias256!~finn@cm-84.208.202.70.getinternet.no, Quit: Leaving.)
08:41cyberorg_ is now known as cyberorg
08:47mealstrom has left IRC (mealstrom!~Thunderbi@46.63.63.163, Ping timeout: 260 seconds)
09:26mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.71.254)
11:04andygraybeal has left IRC (andygraybeal!~andy@h229.229.22.98.dynamic.ip.windstream.net, Quit: Ex-Chat)
12:11Faith has joined IRC (Faith!~paty@unaffiliated/faith)
12:41xiphias256 has joined IRC (xiphias256!~finn@cm-84.208.202.70.getinternet.no)
12:55Aetos has joined IRC (Aetos!29f94098@gateway/web/freenode/ip.41.249.64.152)
12:55
<Aetos>
Hi people :)
12:55
I'm encountering a rather odd difficulty regarding my thin client.
12:56
I installed LTSP on my desktop Ubuntu 12.04
12:56
and configured it
12:56
everything seems to be working fine since the client connects to the server
12:56
starts the loading screen (boot)
12:57
then ends up in a command line interface
13:05
I don't know if this will show but here's how my client boots : https://www.facebook.com/photo.php?fbid=424254384382014&set=a.424254364382016.1073741832.100003923699120&type=3&theater
13:07xiphias256 has left IRC (xiphias256!~finn@cm-84.208.202.70.getinternet.no)
13:13Phantomas has joined IRC (Phantomas!~phantomas@ubuntu/member/phantomas)
13:20
<Aetos>
here's an alternative source for the image
13:20
https://imageshack.com/i/pd29pJrSj
13:30adrianorg has left IRC (adrianorg!~adrianorg@179.179.74.164, Ping timeout: 272 seconds)
13:31adrianorg has joined IRC (adrianorg!~adrianorg@177.156.231.83)
13:37Aetos has left IRC (Aetos!29f94098@gateway/web/freenode/ip.41.249.64.152, Ping timeout: 246 seconds)
13:37
<||cw>
that could be a lot of things. often some driver issue. edit the kernel command line and remove "splash quiet" and see if it gives you more info
14:02alexxtasi has left IRC (alexxtasi!~alex@unaffiliated/alexxtasi)
14:10freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)
14:28championofcyrod1 has joined IRC (championofcyrod1!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
14:36freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Quit: So long and thanks for all the fish.)
14:38championofcyrod1 has left IRC (championofcyrod1!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
14:39Aetos has joined IRC (Aetos!29f94098@gateway/web/freenode/ip.41.249.64.152)
14:43Aetos has left IRC (Aetos!29f94098@gateway/web/freenode/ip.41.249.64.152, Ping timeout: 246 seconds)
14:48telex has left IRC (telex!~telex@freeshell.de, Remote host closed the connection)
14:50telex has joined IRC (telex!~telex@freeshell.de)
14:52vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
15:37mealstrom has left IRC (mealstrom!~Thunderbi@46.63.71.254, Ping timeout: 240 seconds)
15:39boospy has joined IRC (boospy!~loma@darkbox.osit.cc)
16:06mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.63.163)
16:16boospy has left IRC (boospy!~loma@darkbox.osit.cc)
16:20boospy has joined IRC (boospy!~loma@darkbox.osit.cc)
16:21boospy has left IRC (boospy!~loma@darkbox.osit.cc)
16:35boospy has joined IRC (boospy!~loma@darkbox.osit.cc)
16:41lns has joined IRC (lns!~lns@173-16-196-23.client.mchsi.com)
16:41lns has joined IRC (lns!~lns@pdpc/supporter/professional/lns)
16:51
<vagrantc>
bennabiy: yay. the ltsp/ldm support for LDM_PASSWORD_HASH is all available in Debian Jessie.
16:52
although having had ldm migrate, and ltsp get stuck for a few days reminds me of why i wish we put the rc.d hook in ldm itself.
16:52
i.e. if the corresponding ltsp package isn't installed, the file that LDM generates lingers there idefinitely.
16:53
maybe ldm should have a clean-up hook of it's own.
17:18Phantomas has left IRC (Phantomas!~phantomas@ubuntu/member/phantomas)
18:04sligett has joined IRC (sligett!c71589a3@gateway/web/freenode/ip.199.21.137.163)
18:08
<sligett>
Hi - I'm trying to set up an LTSP server w Linux Mint 17 Mate. I'm getting an error on ltsp-build-client: The following packages have unmet dependencies: mint-meta-core : Depends: mintsources but it is not going to be installed E: Unable to correct problems, you have held broken packages. error: LTSP client installation ended abnormally
18:09
Can you suggest fixes, or where to look for fixes? many thanks.
18:21
<vagrantc>
!mint
18:21
<ltsp>
I do not know about 'mint', but I do know about these similar topics: 'LinuxMint'
18:21
<vagrantc>
!linuxmint | echo sligett
18:21
<ltsp>
sligett linuxmint: https://launchpad.net/~bennabiy/+archive/testing Developmental Branch for Mint support
18:21
<vagrantc>
sligett: you might also want to check in with bennabiy
18:23
<bennabiy>
I just happened to check in for a minute. Between 16 and 17 some of the meta packages changed, causing the current method for generating a chroot to fail. I am going to be updating the code soon to pull the right packages.
18:23
For now, you can do ltsp-build-client --dist trusty --mint-dist none
18:24
that will build a stock ubuntu chroot, which should be fine for a thin client (since your actual desktop environment would be the mint 17 on the server)
18:24
For fat client, I am pinning down the order of packages which need to be installed and or removed to make a true mint fat client
18:24
<vagrantc>
does ltsp-pnp work with mint?
18:24
<bennabiy>
the best option for fat client would be ltsp-pnp
18:25
and then you can take that .img file and decompress it into a folder if you want to modify your image apart from changing your server environment
18:25
<sligett>
Options -- Sounds cool, thanks. In the past, I've had thin clients, and some that ran local apps, but not fat clients.
18:26
<vagrantc>
ltsp-pnp also works fine for thin clients or localapps, it just takes more disk space and longer to build the image.
18:26
since it's building a fat-client capable image, there's more there
18:26
<bennabiy>
it would be fine for localapps, you can even manually go in and debuntuize the chroot and pull in ldm-mint-theme
18:27
I cannot stay and talk right now, running wire, but didn't want to leave you hanging
18:27
I will be around more probably after the weekend
18:27
<sligett>
When I first hear of ltsp-pnp, I couldn't find anything to tell me what it is. I'm guessing "pnp" means plug and play?
18:27
<bennabiy>
!ltsp-pnp | echo sligett
18:27
<ltsp>
sligett ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
18:27
<sligett>
bennabiy - great, thanks.
18:28
<bennabiy>
basically, it uses your server as the basis for generating the client image
18:28* bennabiy waves
18:30
<sligett>
I'll try the build-client with options for now, and then go down the pnp road if need be.
18:33mealstrom1 has joined IRC (mealstrom1!~Thunderbi@46.63.63.163)
18:41mealstrom has left IRC (mealstrom!~Thunderbi@46.63.63.163, *.net *.split)
18:41zamba has left IRC (zamba!marius@flage.org, *.net *.split)
18:41workingcats has left IRC (workingcats!~workingca@212.122.48.77, *.net *.split)
18:47workingcats has joined IRC (workingcats!~workingca@212.122.48.77)
18:48zamba has joined IRC (zamba!marius@flage.org)
19:25
<sligett>
I got closer, but still not to a running ltsp server. I don't know if it is due to using Mint or not. Here's the errors --
19:25
Creating config file /etc/default/grub with new version grub-probe: error: cannot find a device for / (is /dev mounted?). grub-probe: error: cannot find a device for /boot (is /dev mounted?). grub-probe: error: cannot find a device for /boot/grub (is /dev mounted?). Processing triggers for libc-bin (2.19-0ubuntu6.1) ... Updating /var/lib/tftpboot directories for chroot: amd64 ionice: executing mksquashfs failed: No such file or direct
19:27
So, I don't know if the grub-probe errors are the problem, or something related to using amd64 arch. Any clues you can see?
19:32cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 272 seconds)
19:33cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
19:34alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
19:44
<sligett>
Hi - anyone out there have a working Linux Mint 17 Mate LTSP server? I can't get ltsp-build-client to succeed.
19:44
<alkisg>
bennabiy: is that the latest mint, including your latest changes? ^
19:45
vagrantc: # grep COMPRESS /etc/initramfs-tools/initramfs.conf
19:45
# COMPRESS: [ gzip | bzip2 | lzma | lzop | xz ]
19:45
COMPRESS=gzip
19:45
!alkisg-todo
19:45
<ltsp>
alkisg-todo: (#1) Hooks for running scripts on these phases: INITRD/INIT/RC/DM/AUTH/LOGIN/SESSION/PERIODIC/LOGOUT/SHUTDOWN, or (#2) implement ltsp-config aoe, or (#3) fix vendor:pxe in ltsp-server-dnsmasq.conf and add more options, or (#4) change COMPRESS=gzip (19899456 bytes) to either lzma (14710842) or xz (14633624), in /etc/initramfs-tools/initramfs.conf
19:45
<alkisg>
Check the byte difference... I think lzma would make a nice default :)
19:45
It would speed up client booting a lot
19:49
<sligett>
Yes, I may have to wait until bennabiy drops in again.
19:50
The ltsp-build-client goes well, until --
19:51
Creating config file /etc/default/grub with new version grub-probe: error: cannot find a device for / (is /dev mounted?).
19:55boospy has left IRC (boospy!~loma@darkbox.osit.cc)
20:05boospy has joined IRC (boospy!~loma@darkbox.osit.cc)
20:05boospy has left IRC (boospy!~loma@darkbox.osit.cc)
20:12
<alkisg>
!pastebin | echo sligett:
20:12
<ltsp>
sligett: pastebin: the LTSP pastebin is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebin, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here.
20:12
<alkisg>
sligett: you could put all the output there
20:13
In order for grub-probe to work in a chroot, /dev, /sys etc need to be mounted
20:13
So either blacklist grub, or use ltsp-chroot -a
20:17
<vagrantc>
alkisg: i got the impression xz replaced/deprecated lzma...
20:19
alkisg: also, i'm not inclined to change defaults in other packages by default.
20:19
<alkisg>
vagrantc: I think lzma decompression is in-kernel, while xz isn't; initramfs-tools introduced them both at the same time afaik, but I would like to check other distros before selecting one of them...
20:19
ltsp-config ...
20:19
<vagrantc>
alkisg: if we really want that, we should ask for the default to get changed in Debian/Ubuntu
20:19
sure, an option to enable it is fine.
20:20
<alkisg>
There's also /etc/initramfs-tools/conf.d/
20:20
Defaults in other packages make sense as "defaults"
20:20
When we install ltsp-client in a system, we significantly change the "defaults"...
20:20
We don't care about some modules, we care about the others, we care about initramfs size...
20:20
<vagrantc>
alkisg: i've got various XZ options in the debian kerne
20:20
<alkisg>
Heck, previously we even made boot=ltsp default, instead of boot=local...
20:21
<vagrantc>
yeah, but we've been reducing the changes to default by enabling things at runtime
20:21
<alkisg>
Not in initramfs
20:21
<vagrantc>
obviously, initramfs generation can't be done at runtime
20:21
<alkisg>
we can't modify that at runtime
20:21
Right
20:22
Well, if we really wanted to, we could re-compress it as part of ltsp-update-kernels
20:22* vagrantc wonders if all arches support other initramfs compression types
20:22
<alkisg>
ltsp-config can check if that file contains COMPRESS=, before offering that option
20:23
Thus, in e.g. Ubuntu 10.04 it wouldn't offer it
20:23
<vagrantc>
alkisg: but really, if there's a reason to change the default for LTSP, chances are that reason is also true distro-wide.
20:24
<alkisg>
No, because it's a different medium
20:24
<vagrantc>
?
20:24
<alkisg>
Disks have 50 MB/sec bandwidth, network doesn't
20:24
<vagrantc>
so the bandwidth vs. cpu time tradeoff isn't as good a trade-off?
20:24
<alkisg>
CPU matters more than size while loading an initramfs locally, while bandwidth (size) matters most when netbooting it
20:25
<vagrantc>
alkisg: what kind of numbers did you see so far?
20:25
<alkisg>
I think that benchmarks will show that: "xz is faster for netbooting, gzip is faster for local booting"
20:25
For netbooting, it's 25% smaller size
20:25
It would load in e.g. 3 seconds instead of 4
20:26
<vagrantc>
also depends on the hardware ... i.e. using xz requires a lot more ram, i believe
20:26
<alkisg>
If one has a lot of clients, it does make a significant difference
20:26
I'm not sure about that, because the whole file is in RAM
20:26
<vagrantc>
might bump the minimum ram requirements
20:26
<alkisg>
It's different than decompressing it from disk
20:26
So, suppose xz is 5 MB smaller, and needs 4 MB more RAM for decompression
20:27
That would mean that it would need *less* RAM for netbooting
20:27
<vagrantc>
oh, also, the initramfs generated by ubuntu is much larger than the one generated in debian, last i looked.
20:27
in which case the size savings would likely be less significant
20:27
<alkisg>
True, but I removed a few things and now in 14.04 it's 7 MB smaller
20:27
It's closer to debian than ever before, nowadays...
20:28
<vagrantc>
well, my basic stance is don't change it if we don't need to, but if there's a strong argument for changing it, make it optional (either opt-out or opt-in).
20:29
<alkisg>
To sum up the argument, I'd say "2 seconds faster boot times, on average, more on slow networks or with a lot of clients"
20:30* vagrantc has never been convinced by 20 vs 40 vs 60 second boot times
20:31
<alkisg>
I like faster booting, but not when it has serious downsides like e.g. being unable to type in initramfs, like plymouth does...
20:31
That change could even lower the ram requirements... but I'd need to check it out to make sure
20:31
Anyways, just an idea, nothing significant
20:31
<vagrantc>
the compression/decompression speed differences are also CPU bound, which may impact slower clients
20:33
if /etc/initramfs-tools/conf.d/*.conf is an option, though (or /usr/share/initramfs-tools/conf.d) makes divergence more of an option
20:33* vagrantc wonders about backportability, too
20:34
<vagrantc>
although i've done an amazing job of not backporting ltsp this release cycle
20:34
<alkisg>
It's there in wheezy and 12.04, it isn't in 10.04, but adding an unknown variable wouldn't hurt
20:34
It would just still use gzip
20:35
Wow, lzop compression doesn't produce smaller size, but it does decompress 300% faster...
20:37
xz and lzma are about 100% slower
20:41
<vagrantc>
xz/lzma slower in general, or just in decompression?
20:42
<alkisg>
In general
20:42
On my 5-year old laptop, gzip decompression = 0.5 sec, xz = 1.5 sec. So it would add 1 sec in the boot time (while removing a couple of secs due to the network)
20:42
<sligett>
alkisg: thanks - I'll check w bennabiy. And thanks for the pastebin note.
20:43
<alkisg>
So yeah the savings aren't as great as I imagined them at first
20:43
sligett: I mean, if you pastebin the output, we might be able to help a bit even without bennably
20:43
But OK waiting is fine too
20:54
<sligett>
Well, if you see something obvious here, I'll make another attempt. http://pastebin.com/q11GX9zP thanks.
20:58
<alkisg>
sligett: you should also put the full command, and your ltsp-build-client.conf, if you're using one
20:58
E.g. now we can't even see if you're building a thin or a fat chroot
20:58
The obvious error is what I said above, about grub being unable to get installed in a chroot without /dev and /sys mounted
20:59||cw has left IRC (||cw!~chris@phpgroupware/cw, Ping timeout: 255 seconds)
21:03
<sligett>
Thank you - I'll make another stab at it tomorrow.
21:08sligett has left IRC (sligett!c71589a3@gateway/web/freenode/ip.199.21.137.163)
21:12kwmiebach__ has joined IRC (kwmiebach__!sid16855@gateway/web/irccloud.com/x-nbndarpaijwhilpy)
21:12kwmiebach_ has left IRC (kwmiebach_!sid16855@gateway/web/irccloud.com/x-drepyjjfupcyhpdk, Ping timeout: 260 seconds)
21:13||cw has joined IRC (||cw!~chris@phpgroupware/cw)
21:13map7 has left IRC (map7!~map7@teksup41.lnk.telstra.net, Ping timeout: 260 seconds)
21:14map7 has joined IRC (map7!~map7@teksup41.lnk.telstra.net)
21:35alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)
21:50boospy has joined IRC (boospy!~loma@darkbox.osit.cc)
21:59Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)
23:04cryptrat has joined IRC (cryptrat!481f0c3c@gateway/web/freenode/ip.72.31.12.60)
23:06
<cryptrat>
is there anyway to add something like a startup script to thin clients to automount samba shares? kinda like a windows netlogin file?
23:12
<map7>
cryptrat, you can put the shares into your /etc/fstab within your thin client image, or better still just put the fstab lines in your lts.conf file
23:12
that way you don't need to recompress the image.
23:12
eg: http://rpm.pbone.net/index.php3/stat/45/idpl/24005700/numer/5/nazwa/lts.conf
23:39
<cryptrat>
thank you very much
23:59andygraybeal has joined IRC (andygraybeal!~andy@h229.229.22.98.dynamic.ip.windstream.net)