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


Channel log from 31 January 2017   (all times are UTC)

00:13ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection)
01:10gehidore is now known as man
01:10man is now known as gehidore
02:26lee_ has joined IRC (lee_!43f63279@gateway/web/freenode/ip.67.246.50.121)
02:27lee_ is now known as Guest78403
02:27
<Guest78403>
guys i am looking for a little help with the ltsp-localapps process
02:31
when i type the command in i get command not found
02:33
i dont know if it matters but i am on the raspberry pi2 client. It works as expected except for the local apps
02:34Guest78403 has left IRC (Guest78403!43f63279@gateway/web/freenode/ip.67.246.50.121, Quit: Page closed)
02:38Lee_ has joined IRC (Lee_!43f63279@gateway/web/freenode/ip.67.246.50.121)
02:39Lee_ is now known as Guest77238
02:39
<Guest77238>
hi
02:39
looking for help with ltsp-localapps
02:49
i have installed ltsp server and i can boot a client to the lubuntu desktop. i have been in the chroot and also install the lubuntu desktop in there
02:51
my goal is to get a hand full of apps to run directly from the pie...no apps would be run at the same time...with the main app being kodi
02:53
in the terminal when i type ltsp-localapps i get command not found from the client side...i can type this in one the server and it looks like it does nothing
02:53
local apps is set in the lts.conf
05:18Freejack has left IRC (Freejack!~Freejack@unaffiliated/freejack, Ping timeout: 255 seconds)
05:23Freejack has joined IRC (Freejack!~Freejack@unaffiliated/freejack)
06:08Statler has joined IRC (Statler!~Georg@p4FC87FA9.dip0.t-ipconnect.de)
06:14
<alkisg>
Guest77238: do you have epoptes installed?
06:14
!epoptes
06:14
<ltsp`>
epoptes: Epoptes is a computer lab administration and monitoring tool. It works on Ubuntu and Debian based labs with LTSP or non-LTSP servers, thin and fat clients, standalone workstations, NX clients etc. More info: http://www.epoptes.org
06:46gdi2k has joined IRC (gdi2k!~gdi2k@119.94.27.63)
07:24ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:38
<alkisg>
!client-list
07:38
<ltsp`>
client-list: to get a list of all nbd-clients (which sometimes is the same as ltsp clients), run: netstat -tn | sed -n 's/.*:10809 *\([0-9.]*\):.*/\1/p' | sort -Vu
08:06
<alkisg>
!nbd-client
08:06
<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
08:06mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
08:35Statler has left IRC (Statler!~Georg@p4FC87FA9.dip0.t-ipconnect.de, Remote host closed the connection)
09:33Statler has joined IRC (Statler!~Georg@mail.lohn24.de)
09:40gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
09:58markus_e92 has left IRC (markus_e92!~markus_e9@62-46-102-153.adsl.highway.telekom.at, Ping timeout: 255 seconds)
10:00markus_e92 has joined IRC (markus_e92!~markus_e9@91-115-16-135.adsl.highway.telekom.at)
11:52
<Statler>
systemd-udevd[xxx]: Process 'ltspfs_entry add nbd5' failed with exit code 1
11:53
has someone seen this
11:55markus_e92 has left IRC (markus_e92!~markus_e9@91-115-16-135.adsl.highway.telekom.at, Ping timeout: 258 seconds)
11:55
<Statler>
got this for all nbds excluding nbd9
11:57markus_e92 has joined IRC (markus_e92!~markus_e9@91-115-159-57.adsl.highway.telekom.at)
11:59
<alkisg>
Statler: I don't think ltsp uses nbd5
12:00
Anything customized there?
12:03
<Statler>
I got this fpr nbd2 to nbd13
12:03
excepting nbd 9
12:03
[ 13.864409] block nbd9: NBD_DISCONNECT
12:03
[ 13.864492] block nbd9: shutting down socket
12:03
[ 13.864652] block nbd9: Receive control failed (result -32)
12:03
[ 44.047869] block nbd9: Connection timed out, shutting down connection
12:03
[ 44.047881] blk_update_request: I/O error, dev nbd9, sector 3956416
12:03
[ 44.048058] block nbd9: Attempted send on closed socket
12:10
devices/virtual/block/nbd9' is taking a long time
12:10
and when I ask via "fdisk -l" nothing is connected to nbd9
12:17lucascastro has left IRC (lucascastro!~lucas@186.227.186.18, Remote host closed the connection)
12:33lucascastro has joined IRC (lucascastro!~lucas@186.227.185.10)
13:29lucascastro has left IRC (lucascastro!~lucas@186.227.185.10, Remote host closed the connection)
13:32ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 240 seconds)
13:33ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
13:39mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
13:43
<Guest77238>
<alkisg> no i do not hae epoptes installed
14:01vsuojanen has joined IRC (vsuojanen!~valtteri@83-136-248-31.uk-lon1.host.upcloud.com)
14:06
<alkisg>
Statler: nbd0 is root (/), nbd1 is swap, and nbd9 is a test for updated root
14:06
The rest are unused, so maybe udev calls ltspfs_entry and nothing happens
14:07
Guest77238: eh, it will be hard to help if you answer once every 8 hours :D
14:08
<Statler>
alkisg, "nbd9 is a test for updated root" and was accessed after disconnecting it?
14:08
what is the sense of it?
14:09
<alkisg>
Statler: I haven't checked that part of the code recently, but it's just a check of "if a newer image is available, and we're at ldm, reboot"
14:09
Insignificant...
14:09
It may have issues, sure, and also nbd-client is kinda buggy...
14:12
<Statler>
im looking for the reason why kworker and nbd-client hang
14:12
<alkisg>
At which point does nbd-client hang?
14:13
<Statler>
different
14:13
'/devices/virtual/block/nbd9' is taking a long time
14:13
<alkisg>
I don't get the actual issue
14:14
nbd-client hangs while accessing nbd9?
14:14
So if you actually remove that part of the code, everything works fine?
14:14
Or do you think it's a problem with nbd-client/server in your distro/version, unrelated to ltsp?
14:16
<Statler>
i paste you a part of the syslog
14:18
http://pastebin.com/hEjYt7u5
14:28
<Guest77238>
<alkisg> sorry have to get ready for work
14:29
but i do have a fe minutes
14:30
<alkisg>
Guest77238: no problem, come back some other day...
14:30
when you'll be more available
14:30
<Guest77238>
<alkisg> have you seen that error before?
14:30
<alkisg>
Guest77238: only if packages are missing
14:30
Statler: that message usually happens when the connection is lost
14:31
Statler: like, actual networking issues, cables, switch, that kind of stuff
14:31
or, nbd-server restarted server-side etc etc
14:32
<Guest77238>
<alkisg> that is a posibility as i have never done this before...idea on what package i might search for?
14:32
<alkisg>
Guest77238: the package that provides ltsp-localapps is ltsp-client-core
14:33
<Guest77238>
<alkisg> i know that package is installed
14:33
<alkisg>
# dpkg -S /usr/bin/ltsp-localapps
14:33
ltsp-server: /usr/bin/ltsp-localapps
14:33
Sorry, ltsp-server provides ltsp-localapps
14:33
While ltsp-client-core provides ltsp-localappsd
14:33
<Statler>
alkisg, I01-nbd-checkupdate do this. I have found it :)
14:33
<alkisg>
If you installed a desktop in the chroot, it's a fat client now
14:34
So it doesn't have ltsp-localapps because it's not running on the server anymore
14:34
It's already running as "localapps"
14:34
<Guest77238>
<alkisg> yes it a fat client
14:34
<alkisg>
yes
14:34
Statler: yes, that is what tests nbd9, but it's surely not what's causing the kernel panic
14:35
Guest77238: I think you don't realize what a fat clients is
14:35
A fat client runs everything as "localapps"
14:35
So ltsp-localapps wouldn't do anything in this case
14:36
If you set LTSP_FATCLIENT=False in lts.conf, then it will be thin again
14:36
So then you can enable "some localapps"
14:36
Now you have "everything is a localapp"
14:36
<Statler>
this test only takes effect after a user logs out from the X. Than they normal shut down the client. Makes not really sense for me to reboot the client when the user wants to go home ;)
14:36
<Guest77238>
<alkisg> that was my goal i just dont think it is happening...if i open firefox it opens it through the server
14:37
<alkisg>
Guest77238: if you open a terminal and run `hostname`, do you see ltsp123 or server there?
14:37
This will tell you if things run locally or on the server
14:37
So, what do you see? ltsp123?
14:37
<Guest77238>
ltsp230
14:37
<alkisg>
Now run `firefox` in that terminal
14:37
It will run locally
14:38
Why do you think it runs from the server?
14:38
<Guest77238>
ok? why is there so much lag?
14:39
<alkisg>
Because pis are really really lame computers that should never be used as desktop pcs
14:39
!cheap-client
14:39
<ltsp`>
cheap-client: http://www.gearbest.com/tv-box-mini-pc/pp_343636.html
14:39
<alkisg>
Take something like that ^ instead, less money, and runs 10 times faster than rpi3
14:41
<Guest77238>
ok thanks. will i have better luck with thin client?
14:42
<alkisg>
rpi as thin client?
14:42
<Guest77238>
ya instead of using it as a fet
14:42
fat
14:42
<alkisg>
It depends on how many clients, what server, network speed etc
14:43
In general, we don't recommend thin clients anymore
14:43
Especially for tasks like web browsing etc
14:43
<Guest77238>
4 clients hooked up a a 48 port switch
14:43
<alkisg>
Server cpu and ram?
14:43
<Guest77238>
server is amd 6 core 16 gigs of ram
14:43
<alkisg>
It should work a bit better then, yes, except for videos
14:44
!flash
14:44
<ltsp`>
flash: Yes, flash sucks. An HD full screen 30 fps video needs 2.5 Gbps bandwidth (1920×1080×4×30)! Make sure you have LDM_DIRECTX=True in your lts.conf file, or if it's just youtube you're after, try some flash replacing plugin like http://linterna-magica.nongnu.org
14:44
<alkisg>
2.5 gbps bandwidth per client is surely unfeasible
14:45
<Guest77238>
ok thanks again will be back
14:45
<alkisg>
bb
14:45
Please throw away the rpis :D
14:45
Then, be back :D
14:48
<rlyshw>
isn't youtube mostly dumping flash? I guess that still doesn't really change the bandwidth requirement too much
14:53ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
14:56
<alkisg>
rlyshw: it's not a problem with flash, all screen updates have that issue, even if it's just simple window scrolling
14:56
That's why ltsp 6 will switch to fat clients by default
14:57
Fat clients transfer disk data from the network, which is a whole less than monitor data
15:05Freejack has left IRC (Freejack!~Freejack@unaffiliated/freejack, Ping timeout: 240 seconds)
15:08
<rlyshw>
Yeah, makes sense
15:08
btw, I'm getting an error with ltsp-build-client...
15:09
"The following packages have unmet dependencies:"
15:09
then it lists things, "dh-python : Depends: python3:any (>=3.#.#)"
15:10Freejack has joined IRC (Freejack!~Freejack@unaffiliated/freejack)
15:10
<rlyshw>
I'm trying to install a xenial chroot
15:10
Also says things like Depends: dbus but it is not going to be installed
15:11
It seems like output from apt-get but I don't recognize it not auto-resolving deps. Is there some module I can change in the Ubuntu plugins to fix it?
15:11
Otherwise I just ltsp-chroot in and do it manually, but then I'm not sure how to generate the initramfs.. The /boot/ dir in the chroot remains empty
15:23Grembler has joined IRC (Grembler!~Ben@cpc87179-aztw31-2-0-cust6.18-1.cable.virginm.net)
15:25
<alkisg>
ltsp-build-client is getting removed in ltsp6 too :D
15:35
rlyshw: pastebin the chroot /etc/apt/sources.list...
15:41lucascastro has joined IRC (lucascastro!~lucas@186.227.186.18)
16:13forum has joined IRC (forum!~Icedove@194-118-247-7.hdsl.highway.telekom.at)
16:16Grembler has left IRC (Grembler!~Ben@cpc87179-aztw31-2-0-cust6.18-1.cable.virginm.net, Quit: I Leave)
16:30Freejack has left IRC (Freejack!~Freejack@unaffiliated/freejack, Ping timeout: 255 seconds)
16:54
<rlyshw>
alkisg: removing ltsp-build-client? Are there docs on ltsp6 somewhere?
16:56
http://pastebin.com/xCf91TfK
16:59gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
17:04Freejack has joined IRC (Freejack!~Freejack@unaffiliated/freejack)
17:26forum1 has joined IRC (forum1!~Icedove@194-118-247-7.hdsl.highway.telekom.at)
17:26forum has left IRC (forum!~Icedove@194-118-247-7.hdsl.highway.telekom.at, Remote host closed the connection)
17:26forum1 is now known as forum
17:50
<rlyshw>
looks like this is most likely an issue in the debootstrap thing again... ugh
17:59forum has left IRC (forum!~Icedove@194-118-247-7.hdsl.highway.telekom.at, Ping timeout: 240 seconds)
17:59forum has joined IRC (forum!~Icedove@194-118-247-7.hdsl.highway.telekom.at)
18:02vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
18:05forum has left IRC (forum!~Icedove@194-118-247-7.hdsl.highway.telekom.at, Remote host closed the connection)
18:06forum1 has joined IRC (forum1!~Icedove@194-118-247-7.hdsl.highway.telekom.at)
18:10forum1 has left IRC (forum1!~Icedove@194-118-247-7.hdsl.highway.telekom.at, Ping timeout: 252 seconds)
18:13forum has joined IRC (forum!~Icedove@194-118-247-7.hdsl.highway.telekom.at)
18:21Statler has left IRC (Statler!~Georg@mail.lohn24.de, Remote host closed the connection)
18:43
<alkisg>
rlyshw: only some draft plans for ltsp6, it's not developed yet
18:43
rlyshw: ports.ubuntu.com? is that armhf?
18:43
If you're trying to build cross-distro, you'll need some weird syntax...
18:43
If it's just cross-arch, it's easier
18:44
About the /boot dir being empty, that would mean ltsp-build-client didn't finish and no kernel was installed
18:45
I don't think you should work upon that chroot; better re-create it
19:07
<rlyshw>
yeah, running builds trying to figure out what's going wrong
19:23sasho_ has joined IRC (sasho_!5549aa13@gateway/web/freenode/ip.85.73.170.19)
19:26
<alkisg>
rlyshw: ok if you need help give more info
19:30
<rlyshw>
It looks like the version of lsb-base in the trusty repos 4.1+Debian11ubuntu6 is too old. ltsp-client-core requires (>=)4.1+Debian11ubuntu6
19:30
so now instead of trying cross-dist stuff I'm just going to upgrade the dist on the server
19:41sasho_ has left IRC (sasho_!5549aa13@gateway/web/freenode/ip.85.73.170.19, )
19:57
<alkisg>
rlyshw: building xenial from trusty should be easy, it's not really cross distro like e.g. building ubuntu from debian
19:57
The dependencies of packages shouldn't be broken when on the same distro (chroot), so I can't believe that ltsp-client-core depends on a newer lsb-base than what's offered by the distro
19:58
But if you're using "ports.ubuntu.com", that's something broken in your setup
19:58
(unless you use armhf and didn't say so yet)
19:59
ltsp-client-core in trusty depends on lsb-base without version number, see http://packages.ubuntu.com/trusty/ltsp-client-core
20:13forum has left IRC (forum!~Icedove@194-118-247-7.hdsl.highway.telekom.at, Quit: forum)
21:07eddytv has joined IRC (eddytv!~eddy@c-68-60-64-128.hsd1.mi.comcast.net)
21:10
<eddytv>
Is there a way to rename NICs on LTSP clients? The normal /etc/udev/rules.d/10-network.rules approach doesn't seem applicable.
21:47eddytv has left IRC (eddytv!~eddy@c-68-60-64-128.hsd1.mi.comcast.net, Quit: My MacBook has gone to sleep. ZZZzzz…)
21:48eddytv has joined IRC (eddytv!~eddy@c-68-60-64-128.hsd1.mi.comcast.net)
22:25ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection)
22:48eddytv has left IRC (eddytv!~eddy@c-68-60-64-128.hsd1.mi.comcast.net, Quit: My MacBook has gone to sleep. ZZZzzz…)
22:50eddytv has joined IRC (eddytv!~eddy@c-68-60-64-128.hsd1.mi.comcast.net)
22:58
<vagrantc>
eddytv: why do you want to or need to do that?
23:01
<eddytv>
I am trying to use LTSP on systems that have multiple NICs, and I want to control the naming of the interfaces
23:03ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
23:04
<vagrantc>
why do you want or need to control the naming of the interfaces?
23:04markit has joined IRC (markit!~marco@88-149-177-66.v4.ngi.it)
23:05
<eddytv>
Trying to match the configuration of existing systems that have existing udev rules that rename the interfaces for consistency and to avoid "re-training"
23:06
<vagrantc>
i just don't understand why the interface name would matter in an LTSP setup
23:06
what needs to be retrained?
23:07
if i understand what problem you're actually trying to solve, it'll be easier to resolve the issue
23:07
because renaming interfaces on your rootfs is likely to be problematic, and probably not the best way forward...
23:07
<eddytv>
The users of the existing non-LTSP systems. I'm trying to setup LTSP as a proof-of-concept for these systems, but unless the interface names can match the "traditional boot from disk" systems, it will probably be a no-go.
23:08
<vagrantc>
what sort of things are they doing that require knowing the name of the interface?
23:10
<eddytv>
Network training. Setting up virtual interfaces, routes, iptables, etc.
23:10
<vagrantc>
basically, this is a shoot yourself in the foot situation you're asking for, so really need to know why you need it to be the way you're asking
23:11
managing network interfaces on devices used for your rootfs is a *bad* idea.
23:16
<eddytv>
The existing training materials already reference the NICs using names that are set via udev.d rules. The systems currently use "traditional" disk-based installs. I'm trying to see if it is possible to have them boot from an LTSP server and end up in the same state, so the benefit is that when they are rebooted, they come up in a "known good" state.
23:16
<vagrantc>
you might try one of the LTSP on disk approaches
23:17
but that would involve installing to all the machines
23:17
but you could reset to a known state with it
23:17
<eddytv>
That's what I'm trying to avoid; it would be a benefit to be able to remove the storage devices from the machines.
23:18
<vagrantc>
another approach would be to load the rootfs into ram, then you wouldn't rely on having the boot interface once it's booted
23:18
you'd still have to figure out how to rename the interfaces
23:19
but you don't want to rename the interface that the rootfs is running off of in a typical LTSP environment
23:19
it's essentially like unplugging the disk while the OS is running...
23:19
<eddytv>
I've been futzing around and it seems that if I put the udev rules in /opt/ltsp/amd64/etc/udev/rules.d and rebuild the initrd with ltsp-chroot update-initramfs -c and update the image, it works!
23:20
<vagrantc>
if the initramfs renames the interface early enough in the process, i guess it might work
23:21
good luck, in any case
23:21
if your install works out for you, consider adding it:
23:21
!worldmap | echo eddytv
23:21
<ltsp`>
eddytv worldmap: If you're using LTSP, please let the world know and share your story at http://www.ltsp.org/stories/ Your can add a nice pin to our world map at your location, plus your setup will count towards the global LTSP usage statistics.
23:21
<vagrantc>
it would be a novel use of LTSP
23:22
<eddytv>
Sure thing. I'll continue to do some testing and if the proof-of-concept works out, will definitely add it. Thanks!
23:24eddytv has left IRC (eddytv!~eddy@c-68-60-64-128.hsd1.mi.comcast.net, Quit: Textual IRC Client: www.textualapp.com)
23:30markit has left IRC (markit!~marco@88-149-177-66.v4.ngi.it, )