IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 13 March 2018 (all times are UTC)
| 00:34 | roca has left IRC (roca!~roca@ool-18bfd59d.dyn.optonline.net, Quit: roca) | |
| 00:44 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 01:06 | lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14) | |
| 01:16 | lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Remote host closed the connection) | |
| 01:16 | lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14) | |
| 02:26 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 02:43 | ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 260 seconds) | |
| 02:44 | ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de) | |
| 05:18 | kidar has left IRC (kidar!~kidar@105.225.41.92, Quit: Leaving) | |
| 05:21 | kidar_ has joined IRC (kidar_!~kidar@105.225.41.92) | |
| 05:42 | lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Remote host closed the connection) | |
| 05:42 | lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14) | |
| 06:19 | jgee has left IRC (jgee!~jgee@181.56.72.152, Ping timeout: 252 seconds) | |
| 06:28 | Statler|Home has joined IRC (Statler|Home!~Georg@p5B30EA7C.dip0.t-ipconnect.de) | |
| 06:51 | ricotz has joined IRC (ricotz!~ricotz@p5B2A9D27.dip0.t-ipconnect.de) | |
| 06:51 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 07:12 | <fiesh> alkisg: this morning, my fat client was frozen, could still switch consoles, but everything that seemed to require file system access blocked indefinitely. I suspect something with NBD, but it's not clear of course. Is there anything meaningful for me to do in order to debug this if it happens again?
| |
| 07:13 | <alkisg> fiesh: nfs is more tolerant in client disconnections and reconnections. NBD isn't; it requires a persistent connection. Is it possible that the client was disconnected for a while?
| |
| 07:14 | In general, it's possible to leave a client on for any number of days, but you can't e.g. pull the network cable for an hour and reconnect it...
| |
| 07:14 | Check the nbd-server processes at that point, if the client still has a connection or not:
| |
| 07:14 | !client-list
| |
| 07:14 | <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
| |
| 07:17 | <fiesh> alkisg: no, it's not been disconnected
| |
| 07:18 | <alkisg> fiesh: and I would assume no standby time either... do you have a client shell in some vt? Can you run dmesg on the client?
| |
| 07:18 | <fiesh> but I'll check that list the next time it happens
| |
| 07:18 | alkisg: I couldn't even log in any more, so I'll open up a shell now so that I have something to go to -- however, I guess it won't be possible to run dmesg
| |
| 07:19 | ahh there's another one!
| |
| 07:19 | and this one gives an error
| |
| 07:19 | packet_write_wait: Connection to <ip address> 22: Broken pipe
| |
| 07:20 | so two clients (all that were booted with the fat client so far) stopped working over night
| |
| 07:21 | but nothing else that can be done with it, no log in, no dmesg, nothing :(
| |
| 07:29 | <alkisg> fiesh: port 22 is ssh, not nbd
| |
| 07:29 | NBD is at port 10809
| |
| 07:30 | Ah maybe that's the error message and not the port...
| |
| 07:31 | If we could look at `dmesg`, and we saw "link up/link down" messages, then we'd know if it was a disconnection issue...
| |
| 07:32 | fiesh: it would also be helpful to have a virtual (vbox) client up and running for a few days. The vbox client is guaranteed not to have connection issues. If the others fail and the vbox one doesn't fail, that would point us to connection issues.
| |
| 07:40 | <fiesh> hmmm easier said than done, the server doesn't have any graphical user interface installed
| |
| 07:41 | but you are right, that's an ssh message
| |
| 07:41 | it is the port
| |
| 07:41 | so the server's dmesg is flooded with [5268299.855930] NFSD: client 192.168.3.117 testing state ID with incorrect client ID
| |
| 07:42 | which unfortunately seems to have overwritten any other messages that might have occured
| |
| 07:42 | <alkisg> fiesh: you can boot a thin client, arrange a vbox thin client instead the real thin client, and finally log in to the server locally and launch it headless via vboxmanage
| |
| 07:43 | s/instead/inside
| |
| 07:43 | I can help with the thin client test if you want
| |
| 07:43 | Re: NFSD, I'm not using NFS for /home... I should... but it shouldn't be any different from your previous setup in that part
| |
| 07:44 | <fiesh> https://www.spinics.net/lists/linux-nfs/msg59785.html
| |
| 07:44 | <alkisg> I.e. I don't have much NFS experience to relay here
| |
| 07:44 | <fiesh> this is about the error message
| |
| 07:44 | oh yeah, I can just use a thin client to begin with, you're right
| |
| 07:45 | <alkisg> fiesh: if you think that the clients changing IPs and hostnames may cause NFS issues, it's possible to define static hostnames in many places
| |
| 07:46 | One place is lts.conf. Another is to tell the client to use a hostname based on MAC, not IP.
| |
| 07:46 | And of course the DHCP server can specify the hostname
| |
| 07:47 | <fiesh> hmm I don't think they're changing IP addresses, I see no reason for that, but I'll try to keep an eye open
| |
| 07:47 | <alkisg> Btw about the ssh message... if ssh complains about a broken pipe, that's 99% usually true, i.e. there was indeed a form of disconnection
| |
| 07:47 | <fiesh> hmm maybe our switch went to funky town
| |
| 07:48 | oh but the NFS messages are all from yesterday morning
| |
| 07:48 | so they cannot be related to the disconenct
| |
| 07:48 | <alkisg> And ssh is a lot more tolerant than nbd
| |
| 07:48 | <fiesh> and after them, dmesg logs no device down
| |
| 07:48 | <alkisg> What's the topology? server <=> single switch <=> clients?
| |
| 07:48 | <fiesh> yes
| |
| 07:48 | and the switch is on the same UPS as the server
| |
| 07:49 | so it cannot have had a power down
| |
| 07:49 | <alkisg> Yeah
| |
| 07:49 | <fiesh> hmm ok, I'll just see if the problem persists or not
| |
| 07:49 | if it's the same every morning, I'll have to look into it or tell everybody to log out over night ;)
| |
| 07:50 | <alkisg> Ah, here's an idea. Do you have this file on the server? /usr/share/ldm/rc.d/I01-nbd-checkupdate
| |
| 07:50 | <fiesh> no, only two X... files
| |
| 07:50 | <alkisg> OK, good, then that's not to blame
| |
| 08:01 | wim1 has joined IRC (wim1!~Thunderbi@WEGC203033.UNI-GRAZ.AT) | |
| 08:15 | ZAJDAN has joined IRC (ZAJDAN!4d30954b@gateway/web/freenode/ip.77.48.149.75) | |
| 08:52 | Statler|Home has left IRC (Statler|Home!~Georg@p5B30EA7C.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 09:31 | Statler_Office has joined IRC (Statler_Office!~Georg@gwrz3.lohn24.de) | |
| 10:26 | root^PC has joined IRC (root^PC!d9d98abb@gateway/web/freenode/ip.217.217.138.187) | |
| 10:26 | <root^PC> hey there
| |
| 10:26 | root^PC has left IRC (root^PC!d9d98abb@gateway/web/freenode/ip.217.217.138.187) | |
| 11:40 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 11:42 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 11:53 | Faith has joined IRC (Faith!~Paty_@unaffiliated/faith) | |
| 11:54 | wim1 has left IRC (wim1!~Thunderbi@WEGC203033.UNI-GRAZ.AT, Quit: wim1) | |
| 11:56 | wim1 has joined IRC (wim1!~Thunderbi@WEGC203033.UNI-GRAZ.AT) | |
| 12:54 | wim1 has left IRC (wim1!~Thunderbi@WEGC203033.UNI-GRAZ.AT, Quit: wim1) | |
| 13:38 | kidar_ has left IRC (kidar_!~kidar@105.225.41.92, Quit: Leaving) | |
| 13:42 | ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu) | |
| 13:49 | nehemiah has joined IRC (nehemiah!~nehemiah@137.26.129.150) | |
| 13:51 | <nehemiah> I was just wondering if it would theoretically be possible to write the contents of the LTSP image to a USB thumb drive or a internal hard drive, install grub to it and make it boot able and working as a standalone installation?
| |
| 13:51 | <alkisg> !local-boot
| |
| 13:51 | <ltsp> local-boot: If you want LTSP fat clients on a low-speed network, you can put i386.img on e.g. C:\Boot\LTSP\i386.img and use this command line in pxelinux.cfg: APPEND ro initrd=ltsp/i386/initrd.img init=/sbin/init-ltsp root=/dev/sda1 rootflags=ro loop=/Boot/LTSP/i386.img; IPAPPEND 3
| |
| 13:51 | <alkisg> nehemiah: ^
| |
| 13:52 | <nehemiah> But would that be able to work w/o the ltsp server?
| |
| 13:54 | <||cw> probably not. it's not hard to make an ubuntu bootable image with whatever you want on it
| |
| 13:54 | <nehemiah> No that's true, it's just an idea I had.
| |
| 13:55 | <alkisg> nehemiah: yes of course, that's why I wrote that note there
| |
| 13:56 | <||cw> alkisg: if it can't reach the server, wouldn't login fail?
| |
| 13:57 | <alkisg> Ah he said w/o, those damn shortcuts
| |
| 13:58 | Well if it's an ltsp-pnp image, it should work fine, as long as you dont pass init=/sbin/init-ltsp, when you don't have the server nearby
| |
| 13:58 | I.e. it will work in the same exact sense that the server itself works
| |
| 13:59 | With LightDM or GDM for the login manager, with local users etc etc
| |
| 13:59 | <nehemiah> Sorry for that. Yeah I kind of liked the idea of havinf somebody boot is laptop of the LTSP server and then be able to run a script that would set that laptop up with more or less the identical set-up.
| |
| 13:59 | But I can create a separate image for that.
| |
| 14:00 | <alkisg> nehemiah: if you're using ltsp-pnp or ltsp-manager, you don't need a separate image
| |
| 14:00 | <nehemiah> I'm using LTSP manager
| |
| 14:00 | <alkisg> The clients boot from the server image/template anyway; they have ltsp-server and dnsmasq and everything installed, just not activated
| |
| 14:00 | OK, so yeah what you asked is completely possible
| |
| 14:01 | You can even write it to a real partition, and it would be the same as if you had cloned the server, except for the --cleanup phase, if you're using that
| |
| 14:02 | E.g. I could write a script where you would select a client in epoptes, go to the Execute command menu, and it would install the ltsp client chroot as a local installation there
| |
| 14:02 | All with one command via epoptes
| |
| 14:04 | <nehemiah> Wow, thank you for that. that sounds brilliant.
| |
| 14:05 | I'll look into that
| |
| 14:13 | Statler_Office has left IRC (Statler_Office!~Georg@gwrz3.lohn24.de, Remote host closed the connection) | |
| 14:14 | Statler_Office has joined IRC (Statler_Office!~Georg@gwrz3.lohn24.de) | |
| 14:18 | Statler_Office has joined IRC (Statler_Office!~Georg@gwrz3.lohn24.de) | |
| 14:54 | nehemiah has left IRC (nehemiah!~nehemiah@137.26.129.150, Remote host closed the connection) | |
| 15:03 | JerryT has left IRC (JerryT!~jerry@wsip-70-165-106-163.om.om.cox.net, Quit: Leaving) | |
| 15:18 | jgee has joined IRC (jgee!~jgee@181.56.72.152) | |
| 16:02 | roca has joined IRC (roca!~roca@ool-6ca2297b.static.optonline.net) | |
| 16:03 | mondeydiver has left IRC (mondeydiver!~lfesdaill@static-108-41-107-210.nycmny.fios.verizon.net, Read error: Connection reset by peer) | |
| 16:08 | roca has left IRC (roca!~roca@ool-6ca2297b.static.optonline.net, Quit: roca) | |
| 16:28 | <fiesh> alkisg: ok, I have two more minor issues that maybe you can help me with
| |
| 16:28 | a) /etc/cups/client.conf vanishes -- it's present in the squashfs, but after booting, it's gone, meaning printing doesn't' work... I have no idea how that can be, something must delete it in the overlay? Can I somehow track that?
| |
| 16:29 | b) before ldm starts, it says (took me a while to catch this with ctrl+s at the right millisecond):
| |
| 16:29 | File "/usr/share/ldm/ldminfod", line 186
| |
| 16:29 | print "ERROR: failed to run locale"
| |
| 16:29 | SyntaxError: Missing parantheses in call to 'print'
| |
| 16:30 | maybe this is a python 2 vs 3 issue?
| |
| 16:30 | (locale is present and this appears to be a purely syntactical problem)
| |
| 16:33 | <alkisg> fiesh: CUPS_SERVER=$SERVER which is the default, or localhost, make the ltsp init scripts overwrite cups.conf
| |
| 16:33 | *client.conf
| |
| 16:34 | About ldminfod, let me check locally...
| |
| 16:38 | fiesh: hmm, I don't get any errors running ldminfod in my vbox gentoo...
| |
| 16:39 | If you run it manually on the client, do you see that error?
| |
| 16:40 | Also, try running just `locale`, and see if it outputs a LANG= line
| |
| 16:47 | <fiesh> alkisg: ah, I didn't know about the CUPS lts option, I'll give it a shot
| |
| 16:47 | <alkisg> fiesh: I don't see any option NOT to generate cups/client.conf; do you need something other than the server in that file?
| |
| 16:47 | <fiesh> alkisg: and yes, try python2 vs python3 with ldminfod
| |
| 16:47 | alkisg: it works with python2 but throws this error with 3
| |
| 16:48 | I think it should probably be fixed, I guess print "bla" needs to be chagned to print("bla"), without being a python programmer
| |
| 16:48 | ZAJDAN has left IRC (ZAJDAN!4d30954b@gateway/web/freenode/ip.77.48.149.75, Ping timeout: 260 seconds) | |
| 16:48 | <alkisg> fiesh: you have python symlinked to python3? Isn't that bad?
| |
| 16:48 | <fiesh> yes and no
| |
| 16:48 | <alkisg> When a program has #!/usr/bin/python, isn't it supposed to run with python2, while if it has python3, with python 3?
| |
| 16:49 | <fiesh> I don't think so, gentoo allows you to select the system python version and symlinks python to it
| |
| 16:49 | so far I have not had problems
| |
| 16:49 | (and I've had it for quite a while)
| |
| 16:49 | <alkisg> OK... since ldminfod hasn't been ported to python 3, the first line would need to read python2 in your system
| |
| 16:49 | <fiesh> yes
| |
| 16:51 | <alkisg> fiesh: http://legacy.python.org/dev/peps/pep-0394/
| |
| 16:51 | for the time being, all distributions should ensure that python refers to the same target as python2.
| |
| 16:55 | Statler_Office has left IRC (Statler_Office!~Georg@gwrz3.lohn24.de, Remote host closed the connection) | |
| 16:56 | <quinox1> #!/usr/bin/env python2
| |
| 16:56 | I think that's the preferred way
| |
| 16:57 | py3 has been out for 10 years now
| |
| 17:01 | <alkisg> I think in general it makes sense to keep python a pointer to the older release, even when python 4 and python 5 arrive in the future...
| |
| 17:01 | so each .py file should specify a number in which it runs with
| |
| 17:04 | <quinox1> yeah
| |
| 17:09 | lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Remote host closed the connection) | |
| 17:10 | <fiesh> ah I see, then gentoo doesn't follow this recommendation I suppose
| |
| 17:11 | <quinox1> making it compatible with both 2 and 3 is doable btw, https://pypi.python.org/pypi/six works like a charm
| |
| 17:15 | <alkisg> Just making ltsp python3-only, would be fine, if someone had the time for it :)
| |
| 18:13 | <bcg> Porting small program like ldminfod from py2 to py3 is quite easy even without six. In py2 you can use __future__ imports for print() and similar.
| |
| 18:15 | It could run on both py2 and py3 easily too.
| |
| 18:25 | lucascastro has joined IRC (lucascastro!~lucas@201.182.221.154) | |
| 19:01 | roca has joined IRC (roca!~roca@ool-6ca2297b.static.optonline.net) | |
| 19:47 | roca has left IRC (roca!~roca@ool-6ca2297b.static.optonline.net, Ping timeout: 246 seconds) | |
| 20:16 | ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection) | |
| 20:28 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 20:34 | Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving) | |
| 20:47 | lucascastro has left IRC (lucascastro!~lucas@201.182.221.154, Remote host closed the connection) | |
| 22:19 | roca has joined IRC (roca!~roca@ool-18bfd59d.dyn.optonline.net) | |
| 22:54 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 22:58 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 23:41 | roca has left IRC (roca!~roca@ool-18bfd59d.dyn.optonline.net, Quit: roca) | |