|00:04||map7 has joined IRC (email@example.com)|
|00:31||andygraybeal has joined IRC (firstname.lastname@example.org)|
I've setup a LTSP-PNP system under Xbuntu 14.04 and I can boot my fat client, but I cannot access the internet
I can do a dns lookup using dig
but I cannot ping an outside IP address such as 18.104.22.168
two network cards in your server, or one?
here is my dnsmasq ltsp-server-dnsmasq.conf file http://pastie.org/9468560
here is my lts.conf file http://pastie.org/9468562
I'm setting the DNS in my lts.conf file
If I boot a none thin client on the network, it gets it's DHCP & DNS configured correctly from the ltsp server
so your LTSP server is handling DHCP?
yes through dnsmasq
all other DHCP servers have been turned off on the network
and any VPN connections have been closed
from a client: traceroute -n 22.214.171.124
map7: and what's in the client's /etc/resolv.conf ?
|00:51||* vagrantc has to head out soon|
map7: try with one or the other DNS_SERVER
map7: i.e. DNS_SERVER=126.96.36.199
map7: in lts.conf
I don't have traceroute installed yet, in the resolv.conf I've got nameserver 188.8.131.52 & nameserver 184.108.40.206
nevermind, on that, it should support multiple entries in DNS_SERVER
well, traceroute will help you figure out where it's not routing...
yep installing now, just have to redo the image
and reboot the thin client.
|00:56||* map7 rebuilding image...|
|00:59||* map7 booting thin client|
vagrantc, I just get a heap of asterisks when using traceroute -n 220.127.116.11
from 1 to 30
dig debian.org seems to be failing with a timed out now on the thin client.
but works on the server
I'm using dnsmasq 2.68-1, that should be ok shouldn't it?
it's a routing problem, not a dnsmasq problem, per se.
anyways, hopefully someone can help you sort it out, i have to head out
vagrantc, cool thanks for pointing me in the right direction, I'll have a look at the routing table
my guess is somehow it's getting told to use a broken route
which might be a dnsmasq configuration issue
|01:15||vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)|
|01:23||map7_ has joined IRC (email@example.com)|
|01:27||map7_ has left IRC (firstname.lastname@example.org, 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)|
The default route is different on the client than that on the server, could this be the cause of my issues?
Still cannot ping the outside world from a fat client.
I'm still thinking that it's something to do with the dnsmasq config.
|03:54||adrianorg has left IRC (email@example.com, Ping timeout: 255 seconds)|
|03:55||adrianorg has joined IRC (firstname.lastname@example.org)|
|05:31||alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)|
|05:43||vsuojanen has left IRC (email@example.com, Remote host closed the connection)|
!learn alkisg-todo fix vendor:pxe in ltsp-server-dnsmasq.conf and add more options
(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.
!learn alkisg-todo as fix vendor:pxe in ltsp-server-dnsmasq.conf and add more options
The operation succeeded.
!learn alkisg-todo as change COMPRESS=gzip (19899456 bytes) to either lzma (14710842) or xz (14633624), in /etc/initramfs-tools/initramfs.conf
The operation succeeded.
|06:14||vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)|
|06:21||vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)|
|06:23||||cw has left IRC (||cw!~chris@phpgroupware/cw, Ping timeout: 240 seconds)|
|06:32||alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)|
|06:36||||cw has joined IRC (||cw!~chris@phpgroupware/cw)|
|06:53||alexxtasi has joined IRC (alexxtasi!~alex@unaffiliated/alexxtasi)|
|07:51||cyberorg_ has joined IRC (cyberorg_!~cyberorg@opensuse/member/Cyberorg)|
|07:53||cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 255 seconds)|
|08:33||xiphias256 has left IRC (firstname.lastname@example.org, Quit: Leaving.)|
|08:41||cyberorg_ is now known as cyberorg|
|08:47||mealstrom has left IRC (mealstrom!~Thunderbi@18.104.22.168, Ping timeout: 260 seconds)|
|09:26||mealstrom has joined IRC (mealstrom!~Thunderbi@22.214.171.124)|
|11:04||andygraybeal has left IRC (email@example.com, Quit: Ex-Chat)|
|12:11||Faith has joined IRC (Faith!~paty@unaffiliated/faith)|
|12:41||xiphias256 has joined IRC (firstname.lastname@example.org)|
|12:55||Aetos has joined IRC (Aetos!29f94098@gateway/web/freenode/ip.126.96.36.199)|
Hi people :)
I'm encountering a rather odd difficulty regarding my thin client.
I installed LTSP on my desktop Ubuntu 12.04
and configured it
everything seems to be working fine since the client connects to the server
starts the loading screen (boot)
then ends up in a command line interface
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:07||xiphias256 has left IRC (email@example.com)|
|13:13||Phantomas has joined IRC (Phantomas!~phantomas@ubuntu/member/phantomas)|
here's an alternative source for the image
|13:30||adrianorg has left IRC (firstname.lastname@example.org, Ping timeout: 272 seconds)|
|13:31||adrianorg has joined IRC (email@example.com)|
|13:37||Aetos has left IRC (Aetos!29f94098@gateway/web/freenode/ip.188.8.131.52, Ping timeout: 246 seconds)|
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:02||alexxtasi has left IRC (alexxtasi!~alex@unaffiliated/alexxtasi)|
|14:10||freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)|
|14:28||championofcyrod1 has joined IRC (firstname.lastname@example.org)|
|14:36||freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Quit: So long and thanks for all the fish.)|
|14:38||championofcyrod1 has left IRC (email@example.com)|
|14:39||Aetos has joined IRC (Aetos!29f94098@gateway/web/freenode/ip.184.108.40.206)|
|14:43||Aetos has left IRC (Aetos!29f94098@gateway/web/freenode/ip.220.127.116.11, Ping timeout: 246 seconds)|
|14:48||telex has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|14:50||telex has joined IRC (email@example.com)|
|14:52||vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)|
|15:37||mealstrom has left IRC (mealstrom!~Thunderbi@18.104.22.168, Ping timeout: 240 seconds)|
|15:39||boospy has joined IRC (firstname.lastname@example.org)|
|16:06||mealstrom has joined IRC (mealstrom!~Thunderbi@22.214.171.124)|
|16:16||boospy has left IRC (email@example.com)|
|16:20||boospy has joined IRC (firstname.lastname@example.org)|
|16:21||boospy has left IRC (email@example.com)|
|16:35||boospy has joined IRC (firstname.lastname@example.org)|
|16:41||lns has joined IRC (email@example.com)|
|16:41||lns has joined IRC (lns!~lns@pdpc/supporter/professional/lns)|
bennabiy: yay. the ltsp/ldm support for LDM_PASSWORD_HASH is all available in Debian Jessie.
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.
i.e. if the corresponding ltsp package isn't installed, the file that LDM generates lingers there idefinitely.
maybe ldm should have a clean-up hook of it's own.
|17:18||Phantomas has left IRC (Phantomas!~phantomas@ubuntu/member/phantomas)|
|18:04||sligett has joined IRC (sligett!c71589a3@gateway/web/freenode/ip.126.96.36.199)|
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
Can you suggest fixes, or where to look for fixes? many thanks.
I do not know about 'mint', but I do know about these similar topics: 'LinuxMint'
!linuxmint | echo sligett
sligett linuxmint: https://launchpad.net/~bennabiy/+archive/testing Developmental Branch for Mint support
sligett: you might also want to check in with 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.
For now, you can do ltsp-build-client --dist trusty --mint-dist none
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)
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
does ltsp-pnp work with mint?
the best option for fat client would be ltsp-pnp
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
Options -- Sounds cool, thanks. In the past, I've had thin clients, and some that ran local apps, but not fat clients.
ltsp-pnp also works fine for thin clients or localapps, it just takes more disk space and longer to build the image.
since it's building a fat-client capable image, there's more there
it would be fine for localapps, you can even manually go in and debuntuize the chroot and pull in ldm-mint-theme
I cannot stay and talk right now, running wire, but didn't want to leave you hanging
I will be around more probably after the weekend
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?
!ltsp-pnp | echo sligett
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
bennabiy - great, thanks.
basically, it uses your server as the basis for generating the client image
|18:28||* bennabiy waves|
I'll try the build-client with options for now, and then go down the pnp road if need be.
|18:33||mealstrom1 has joined IRC (mealstrom1!~Thunderbi@188.8.131.52)|
|18:41||mealstrom has left IRC (mealstrom!~Thunderbi@184.108.40.206, *.net *.split)|
|18:41||zamba has left IRC (firstname.lastname@example.org, *.net *.split)|
|18:41||workingcats has left IRC (email@example.com, *.net *.split)|
|18:47||workingcats has joined IRC (firstname.lastname@example.org)|
|18:48||zamba has joined IRC (email@example.com)|
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 --
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
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:32||cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 272 seconds)|
|19:33||cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)|
|19:34||alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)|
Hi - anyone out there have a working Linux Mint 17 Mate LTSP server? I can't get ltsp-build-client to succeed.
bennabiy: is that the latest mint, including your latest changes? ^
vagrantc: # grep COMPRESS /etc/initramfs-tools/initramfs.conf
# COMPRESS: [ gzip | bzip2 | lzma | lzop | xz ]
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
Check the byte difference... I think lzma would make a nice default :)
It would speed up client booting a lot
Yes, I may have to wait until bennabiy drops in again.
The ltsp-build-client goes well, until --
Creating config file /etc/default/grub with new version grub-probe: error: cannot find a device for / (is /dev mounted?).
|19:55||boospy has left IRC (firstname.lastname@example.org)|
|20:05||boospy has joined IRC (email@example.com)|
|20:05||boospy has left IRC (firstname.lastname@example.org)|
!pastebin | echo sligett:
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.
sligett: you could put all the output there
In order for grub-probe to work in a chroot, /dev, /sys etc need to be mounted
So either blacklist grub, or use ltsp-chroot -a
alkisg: i got the impression xz replaced/deprecated lzma...
alkisg: also, i'm not inclined to change defaults in other packages by default.
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...
alkisg: if we really want that, we should ask for the default to get changed in Debian/Ubuntu
sure, an option to enable it is fine.
There's also /etc/initramfs-tools/conf.d/
Defaults in other packages make sense as "defaults"
When we install ltsp-client in a system, we significantly change the "defaults"...
We don't care about some modules, we care about the others, we care about initramfs size...
alkisg: i've got various XZ options in the debian kerne
Heck, previously we even made boot=ltsp default, instead of boot=local...
yeah, but we've been reducing the changes to default by enabling things at runtime
Not in initramfs
obviously, initramfs generation can't be done at runtime
we can't modify that at runtime
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|
ltsp-config can check if that file contains COMPRESS=, before offering that option
Thus, in e.g. Ubuntu 10.04 it wouldn't offer it
alkisg: but really, if there's a reason to change the default for LTSP, chances are that reason is also true distro-wide.
No, because it's a different medium
Disks have 50 MB/sec bandwidth, network doesn't
so the bandwidth vs. cpu time tradeoff isn't as good a trade-off?
CPU matters more than size while loading an initramfs locally, while bandwidth (size) matters most when netbooting it
alkisg: what kind of numbers did you see so far?
I think that benchmarks will show that: "xz is faster for netbooting, gzip is faster for local booting"
For netbooting, it's 25% smaller size
It would load in e.g. 3 seconds instead of 4
also depends on the hardware ... i.e. using xz requires a lot more ram, i believe
If one has a lot of clients, it does make a significant difference
I'm not sure about that, because the whole file is in RAM
might bump the minimum ram requirements
It's different than decompressing it from disk
So, suppose xz is 5 MB smaller, and needs 4 MB more RAM for decompression
That would mean that it would need *less* RAM for netbooting
oh, also, the initramfs generated by ubuntu is much larger than the one generated in debian, last i looked.
in which case the size savings would likely be less significant
True, but I removed a few things and now in 14.04 it's 7 MB smaller
It's closer to debian than ever before, nowadays...
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).
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|
I like faster booting, but not when it has serious downsides like e.g. being unable to type in initramfs, like plymouth does...
That change could even lower the ram requirements... but I'd need to check it out to make sure
Anyways, just an idea, nothing significant
the compression/decompression speed differences are also CPU bound, which may impact slower clients
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|
although i've done an amazing job of not backporting ltsp this release cycle
It's there in wheezy and 12.04, it isn't in 10.04, but adding an unknown variable wouldn't hurt
It would just still use gzip
Wow, lzop compression doesn't produce smaller size, but it does decompress 300% faster...
xz and lzma are about 100% slower
xz/lzma slower in general, or just in decompression?
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)
alkisg: thanks - I'll check w bennabiy. And thanks for the pastebin note.
So yeah the savings aren't as great as I imagined them at first
sligett: I mean, if you pastebin the output, we might be able to help a bit even without bennably
But OK waiting is fine too
Well, if you see something obvious here, I'll make another attempt. http://pastebin.com/q11GX9zP thanks.
sligett: you should also put the full command, and your ltsp-build-client.conf, if you're using one
E.g. now we can't even see if you're building a thin or a fat chroot
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)|
Thank you - I'll make another stab at it tomorrow.
|21:08||sligett has left IRC (sligett!c71589a3@gateway/web/freenode/ip.220.127.116.11)|
|21:12||kwmiebach__ has joined IRC (kwmiebach__!sid16855@gateway/web/irccloud.com/x-nbndarpaijwhilpy)|
|21:12||kwmiebach_ 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:13||map7 has left IRC (email@example.com, Ping timeout: 260 seconds)|
|21:14||map7 has joined IRC (firstname.lastname@example.org)|
|21:35||alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)|
|21:50||boospy has joined IRC (email@example.com)|
|21:59||Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)|
|23:04||cryptrat has joined IRC (cryptrat!481f0c3c@gateway/web/freenode/ip.18.104.22.168)|
is there anyway to add something like a startup script to thin clients to automount samba shares? kinda like a windows netlogin file?
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
that way you don't need to recompress the image.
thank you very much
|23:59||andygraybeal has joined IRC (firstname.lastname@example.org)|