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


Channel log from 27 July 2018   (all times are UTC)

00:21vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
00:32vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
01:21talmid has left IRC (talmid!~talmid@saphar.net, Read error: Connection reset by peer)
01:25talmid has joined IRC (talmid!~talmid@saphar.net)
02:07talmid has left IRC (talmid!~talmid@saphar.net, Quit: Leaving)
02:23vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
04:20lucascastro has left IRC (lucascastro!~lucas@177-185-139-236.isotelco.net.br, Remote host closed the connection)
04:31alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
04:40
<alkisg>
vagrantc: heya! "Epoptes removed from testing", are we supposed to take action there, or are we just waiting for the vnc maintainer to fix the FTBFS?
04:46
<vagrantc>
alkisg: oh!
04:47
alkisg: if we can help ... it would probably be a good thing
04:47* alkisg has just finished with the python3/gtk3 support, hopefully it won't be for nothing!
04:48
<vagrantc>
alkisg: i know we've switched vnc clients before ... not sure if there are other alternatives though
04:48
<alkisg>
vagrantc: ah, if help is needed, we'd better pull Ubuntu's xvnc4viewer fix then
04:48
xvnc4viewer is still available in ubuntu and works much better than tigervnc
04:48
<vagrantc>
alkisg: if there's a known fix commenting on the bug would be good
04:48
<alkisg>
tigervnc doesn't support multiple incoming connection
04:48
That would be for the other bug though, where xvnc4viewer was removed from debian 2 years ago
04:48
<vagrantc>
ah
04:49
alkisg: hmmmm... well, not sure what to do... heading to lunch soon
04:49
<alkisg>
Maybe we can just change the recommended viewer to one that still exists in debian?
04:49
Will that be enough to keep it in testing?
04:50
<vagrantc>
alkisg: should be enough to get it back into testing, if it still works :)
04:50
<alkisg>
Sounds good then
04:50
<vagrantc>
alkisg: will be back in an hour or so, maybe can chat more then?
04:50
<alkisg>
Sure
04:50
Bon appetite! Or however it's spelled :)
04:51* vagrantc waves
04:51
<vagrantc>
here it's spelled with entirely different character set :)
04:51vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
04:58kjackal has joined IRC (kjackal!~quassel@ppp-94-66-220-142.home.otenet.gr)
05:25Statler|Home has joined IRC (Statler|Home!~Georg@p5B30E888.dip0.t-ipconnect.de)
05:39kjackal has left IRC (kjackal!~quassel@ppp-94-66-220-142.home.otenet.gr, Ping timeout: 268 seconds)
06:07vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
06:43vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 256 seconds)
06:45vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
06:49ricotz has joined IRC (ricotz!~ricotz@p5B2A8E37.dip0.t-ipconnect.de)
06:49ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:54kjackal has joined IRC (kjackal!~quassel@adsl-176.46.190.123.tellas.gr)
07:27
<alkisg>
vagrantc: so maybe we can just put ssvnc as the first in the list?
07:27
xvnc4viewer | tigervnc-viewer | ssvnc | vnc-viewer,
07:27
becomes: ssvnc | xvnc4viewer | tigervnc-viewer | vnc-viewer,
07:28
And later on we may examine if we can get xvnc4viewer back to debian...
07:34Statler|Home has left IRC (Statler|Home!~Georg@p5B30E888.dip0.t-ipconnect.de, Remote host closed the connection)
07:41
<vagrantc>
alkisg: seems like a quick workaround
07:41
alkisg: how far along is the python3/gtk update?
07:41
alkisg: i'd just as soon wait for that
07:41
<alkisg>
vagrantc: it's in a much better state than the currently released version is, but it's not over yet; I'll be working on that until about August 20th...
07:42
Ah sure then, we can wait till then
07:44Leolo_2 has left IRC (Leolo_2!~fil@24-54-27-253.mg.cgocable.ca, Ping timeout: 240 seconds)
08:18vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
09:07alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
09:41Yoyoyoooo has joined IRC (Yoyoyoooo!d49f2d5f@gateway/web/freenode/ip.212.159.45.95)
09:41
<Yoyoyoooo>
Hi, how active is this channel?
09:42
Is it a viable source of support regarding NBD?
09:50alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
09:55alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
09:59alkisg has joined IRC (alkisg!c15ccb10@ubuntu/member/alkisg)
10:00
<alkisg>
Yoyoyoooo: it is active for ltsp support
10:00
Specifically for nbd bugs, there's a bug tracker in its github page
10:00
What issue are you having?
10:03
<Yoyoyoooo>
I followed the official LTSP wiki page on how to set up LTSP on Ubuntu Server 18.04, I opted for the chroot option as I want the server to be headless, I don't want Xorg on there, so I didn't include it.
10:03
Depite this wiki claiming it's more stable than the Ubuntu's own guide which is now abandoned and points to the LTSP wiki, I found it's more troublesome.
10:04
I get "Connect Refused" from nbd-client on my Thin Clients then dropped to a shell.
10:04
<alkisg>
!nbd-client
10:04
<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
10:04
<Yoyoyoooo>
I checked nbd-server on the LTSP server, and it's listening and accepting connections.
10:05
<alkisg>
Can you try this from the client shell?
10:05
Replace the server ip, and i386 with amd64 in that line
10:05
<Yoyoyoooo>
Yeah, that's what I did to confirm it's listening and accepting.
10:05
Oh the client shell! Yes, I'll try.
10:05
<alkisg>
Btw, what do you mean "ubuntu's own guide"? The ubuntu wiki? It's just a host; the same users wrote both wikies :)
10:06
<Yoyoyoooo>
I'm confused, when I first installed LTSP server, NBD was on port 2000, now it's on port 9571...
10:06
Yeah
10:06
<alkisg>
It's been changed since 10 years now :)
10:07
With the change from port-based export, to name-based exports
10:07
What is the output of this, on the client? cat /proc/cmdline
10:08
<Yoyoyoooo>
Aaaah, nice, I didn't know I could gain access to the kernel cmdline that way.
10:10
<alkisg>
Btw, what's your dhcp situation, are you using an external dhcp server, or the proxydhcp mode, or the normal one?
10:10
<Yoyoyoooo>
Hmm, I should look into ltsp-init, also root=/dev/nbd0 which looks right, however at busybox, it claims that dev node doesn't access
10:10
proxy-DHCP
10:10
<alkisg>
As for the old ubuntu guide, it was using the alternate installer, which hasn't been available for 5 years now
10:10
So there wasn't even a cd to install from
10:11
<Yoyoyoooo>
There is an 18.04 alternate installer, I have both ISOs on my hypervisor.
10:11
I thought it was only the installer that was different
10:13
I think I might have found the issue
10:13
The nbd0 dev node on the client takes too long to get allocated
10:13
therefore the thinclient is expecting it too soon
10:14
Would this have something to do with rootdelay?
10:26
alkisg: I'm not sure how to change the rootdelay, I tried in /etc/default/grub on the chroot, however there is no update-grub command.
10:27
<alkisg>
Yoyoyoooo: the alternate installer doesn't have ltsp
10:27
It stopped around 2012 or something
10:28
The nbd dev node takes a long time?!! That's rather strange
10:28
<Yoyoyoooo>
However, I installed LTSP from the Greek Schools repo.
10:28
<alkisg>
So if you put `break=mount` in pxelinux.cfg/default, and you run `modprobe nbd`, you don't see the dev node?
10:28
<Yoyoyoooo>
I've tried on several different servers, they all have the same problems.
10:28
<alkisg>
How is the client nbd dev node related to the server?!
10:29
<Yoyoyoooo>
It's not
10:29
<alkisg>
Greek schools ppa => correct, that's where ubuntu is mostly supported
10:32
To verify that your diagnosis is correct, put break=mount in /var/lib/tftpboot/ltsp/amd64/pxelinux.cfg/default, reboot client, wait 10 secs on shell, type exit
10:32
That should give you all the delay that you need to test
10:32
I doubt it though, as the /dev/nbd* nodes are usually immediately available after modprobe
10:43kjackal has left IRC (kjackal!~quassel@adsl-176.46.190.123.tellas.gr, Ping timeout: 268 seconds)
11:01jgee has left IRC (jgee!~jgee@181.56.72.152, Ping timeout: 244 seconds)
11:02jgee has joined IRC (jgee!~jgee@181.56.72.152)
11:34kjackal has joined IRC (kjackal!~quassel@ppp-94-66-220-238.home.otenet.gr)
12:04Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
12:20alkisg has left IRC (alkisg!c15ccb10@ubuntu/member/alkisg, Ping timeout: 252 seconds)
12:20lucascastro has joined IRC (lucascastro!~lucas@177-185-139-236.isotelco.net.br)
12:47alkisg has joined IRC (alkisg!c15ccb10@ubuntu/member/alkisg)
13:08mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Quit: Leaving)
13:10mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy)
13:24
<fiesh>
hmm ltsp-update-image uses mksquashfs using its default gzip by default -- anyone tried lzo or xz? Seems xz might be the best option, saving client ram, and once its in cache, its unpacked anyway?
13:32
<alkisg>
fiesh: I think vagrantc has proposed it at some point; I don't know if anyone has done any cpu/speed benchmarks
13:33
I don't think that it makes any difference wrt RAM. The image is cached in its compressed form, not uncompressed
13:33
I.e. at the block level, while then the file system decodes it when needed, at the file level
14:01alkisg has left IRC (alkisg!c15ccb10@ubuntu/member/alkisg, Quit: Page closed)
14:51agustin^server-B has joined IRC (agustin^server-B!beb24b41@gateway/web/freenode/ip.190.178.75.65)
14:51
<agustin^server-B>
faa
14:51
hxr
14:51
jdtjdt
14:51agustin^server-B has left IRC (agustin^server-B!beb24b41@gateway/web/freenode/ip.190.178.75.65, Client Quit)
15:17ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Ping timeout: 244 seconds)
15:46ricotz has joined IRC (ricotz!~ricotz@p5B2A8FBD.dip0.t-ipconnect.de)
15:46ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
16:02lucascastro has left IRC (lucascastro!~lucas@177-185-139-236.isotelco.net.br, Read error: Connection reset by peer)
16:02lucascastro has joined IRC (lucascastro!~lucas@177-185-139-236.isotelco.net.br)
16:10GodFather has left IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net, Ping timeout: 265 seconds)
16:27lucascastro has left IRC (lucascastro!~lucas@177-185-139-236.isotelco.net.br, Remote host closed the connection)
16:32yanu has left IRC (yanu!~yanu@178-116-60-189.access.telenet.be, Ping timeout: 264 seconds)
16:33yanu has joined IRC (yanu!~yanu@178-116-60-189.access.telenet.be)
16:44
<quinox>
well said
16:46bengoa has joined IRC (bengoa!~alberto@2804:14d:4cdb:1e7d:91b:4143:9b5e:96c1)
16:52lucascastro has joined IRC (lucascastro!~lucas@200.141.207.18)
17:12alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
17:21Yoyoyoooo has left IRC (Yoyoyoooo!d49f2d5f@gateway/web/freenode/ip.212.159.45.95, Ping timeout: 252 seconds)
17:23alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
17:58yanu has left IRC (yanu!~yanu@178-116-60-189.access.telenet.be, Ping timeout: 260 seconds)
17:58yanu has joined IRC (yanu!~yanu@178-116-60-189.access.telenet.be)
18:13yanu_ has joined IRC (yanu_!~yanu@178-116-60-189.access.telenet.be)
18:13yanu has left IRC (yanu!~yanu@178-116-60-189.access.telenet.be, Ping timeout: 244 seconds)
18:20yanu_ has left IRC (yanu_!~yanu@178-116-60-189.access.telenet.be, Ping timeout: 264 seconds)
18:22yanu has joined IRC (yanu!~yanu@178-116-60-189.access.telenet.be)
18:39jammcq has joined IRC (jammcq!~jam@c-68-55-175-208.hsd1.mi.comcast.net)
18:39
<jammcq>
hey all
19:26petr has joined IRC (petr!5b4fcacd@gateway/web/freenode/ip.91.79.202.205)
19:32
<quinox>
hi jammcq
19:32ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
19:33
<petr>
Hello to all :)
19:33petr has left IRC (petr!5b4fcacd@gateway/web/freenode/ip.91.79.202.205, Quit: Page closed)
19:34Petr has joined IRC (Petr!5b4fcacd@gateway/web/freenode/ip.91.79.202.205)
19:34
<Petr>
Can anybody help me? I can't setup fat clients on ubuntu 18.04. My problem is - dns doesn't work. In resolve.conf i has 127.0.0.53. When i change it to external dns service - it starting work. But it's not good idea - i think. How can i fix systemd-resolved?
19:46derick_ has joined IRC (derick_!b646ae38@gateway/web/freenode/ip.182.70.174.56)
19:46
<derick_>
hello :)
19:47
<quinox>
Petr: that's not really a LTSP question... I suppse it depends on why systemd-resolved is broken
19:47
try journalctl -u systemd-resolved
19:47* quinox waves at derick_
19:49
<derick_>
Petr: editing resolve.conf is not a good idea. It would again change back to 127.0.0.53 after some time.
19:51ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
19:52
<derick_>
I was also facing this issue. workaround that I used was to change resolv.conf.d/head and regenerating the resolv.conf . Solution is to use new version of ltsp.
20:06
<bengoa>
jammcq, I guess I know you from somewhere :-)
20:06
<Petr>
Hm. I using last version from ppa...
20:08
Sorry for wait, I departed from the computer
20:17
In journalctl -u systemd-resolved a has not errors.
20:18
it is fresh clean install
20:36Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
20:49lucascastro has left IRC (lucascastro!~lucas@200.141.207.18, Remote host closed the connection)
21:09Petr has left IRC (Petr!5b4fcacd@gateway/web/freenode/ip.91.79.202.205, Ping timeout: 252 seconds)
21:21Leolo_2 has joined IRC (Leolo_2!~fil@24-54-27-253.mg.cgocable.ca)
21:44kjackal has left IRC (kjackal!~quassel@ppp-94-66-220-238.home.otenet.gr, Ping timeout: 256 seconds)
22:09bengoa has left IRC (bengoa!~alberto@2804:14d:4cdb:1e7d:91b:4143:9b5e:96c1, Quit: Leaving)
22:14ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection)
22:32lucascastro has joined IRC (lucascastro!~lucas@177-185-139-236.isotelco.net.br)
22:40derick_ has left IRC (derick_!b646ae38@gateway/web/freenode/ip.182.70.174.56, Ping timeout: 252 seconds)
23:07TheBoyd1 has joined IRC (TheBoyd1!~TheBoyd@45.56.5.132)
23:09TheBoyd1 has left IRC (TheBoyd1!~TheBoyd@45.56.5.132, Client Quit)