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


Channel log from 24 January 2018   (all times are UTC)

00:06vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
00:30ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection)
01:27book` has left IRC (book`!~book`@68.ip-149-56-14.net, Quit: Leaving)
01:30book` has joined IRC (book`!~book`@68.ip-149-56-14.net)
02:57mmarconm has joined IRC (mmarconm!~Marcelo@unaffiliated/mmarconm)
03:56mmarconm has left IRC (mmarconm!~Marcelo@unaffiliated/mmarconm, Quit: Leaving)
05:19gehidore is now known as man
05:19man is now known as gehidore
05:28quinox has joined IRC (quinox!~quinox@ghost.qtea.nl)
05:31quinox1 has left IRC (quinox1!~quinox@ghost.qtea.nl, Ping timeout: 265 seconds)
06:22kjackal has joined IRC (kjackal!~quassel@fpc121872-nmal24-2-0-cust27.19-2.static.cable.virginm.net)
06:24Statler has joined IRC (Statler!~Georg@p5B30EA68.dip0.t-ipconnect.de)
06:31
<NUMG>
Hi there, I have a couple of questions on a brand new installation : Lubuntu 16.04.3 + LTSP-Manager.
06:33
<alkisg>
shoot
06:43ABIX_Adamj_ has joined IRC (ABIX_Adamj_!~quassel@abix-vps.abix.info.pl)
06:46
<NUMG>
The first time I booted my ThinClient, everything went OK. But now, I encouter some NBD errors at the startup
06:47
followed by SQUASHFS error : unable to read directory
06:47ABIX_Adamj has left IRC (ABIX_Adamj!~quassel@2a01:7c8:aab0:3d9:5054:ff:fed3:602b, Ping timeout: 256 seconds)
06:48
<alkisg>
NUMG: do the errors persist if you restart the server?
06:48
<NUMG>
Yes
06:48
I tried to restart the server, update the image with no success
06:48
<alkisg>
And the client doesn't boot then?
06:49
<NUMG>
Sometimes it does, it can pass the error, sometimes I got a Kernel Panic and sometimes it failed at starting up some services
06:49
<alkisg>
Are you testing with just one client? Do other clients boot fine?
06:49
<NUMG>
I tried on my thinclient (HP T520) and on VirtualBox VM, same results
06:50
<alkisg>
OK, I can have a look over VNC with the VM if you like
06:50
!vnc-edide
06:50
<ltsp>
vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
06:52
<NUMG>
Link to VirtualBox screenshot. https://framapic.org/kQndlIdSsM7m/DGdvnM7S8EMf.png
06:52
Also, it seems that there errors are more frequent on the ThinClient than on the VirtualBox
06:55
Do you want me to share the screen on the server or on the ThinClient ?
06:56
<alkisg>
NUMG: usually, the server screen, unless it's headless, which will make things a bit harder
06:59
<NUMG>
This is the first time, I am running Epopter and it says that the user "admin" must be a member of the group epoptes.
06:59
I checked and he is member of this group
07:01
<alkisg>
NUMG: if you added him to the group recently, you need to logout/login to take effect
07:01
Otherwise, just run this:
07:01
!vnc-dide
07:01
<ltsp>
vnc-dide: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect srv1-dide.ioa.sch.gr - this is a reverse connection, it doesn't need port forwarding etc.
07:05
<alkisg>
NUMG: moment, a school called, will get to you in 5 mins
07:05
<NUMG>
OK. I restarted the server, and now I can run epoptes
07:05
OK
07:05
No problem
07:09jgee has left IRC (jgee!~jgee@181.56.72.152, Ping timeout: 240 seconds)
07:13
<alkisg>
NUMG: ah, when you say virtualbox, you mean from another pc?
07:13
OK, so usually the nbd errors you see mean "bad networking". So it was weird that you were seeing them via virtualbox.
07:14
But since you're running virtualbox from another pc, then yeah it makes sense, bad networking again
07:14
I would suggest installing virtualbox or kvm on the server, and test if it happens there
07:15
<NUMG>
Yes, from an other ocmputer
07:16
That's what I thought : our network is not the best in the world :(
07:17
I will try to run a VM directly from the ESX Server where the LTSP Server is virtualized
07:17
<alkisg>
OK, ping me if that doesn't work as expected
07:19
<NUMG>
For reference to photos take from the ThinClient HP with Kernel Panic : https://framapic.org/kwwoueFiMrKx/sgCnS4KAgq2F.jpg
07:19
https://framapic.org/T0KyNburEA8f/AV1oM9naazAT.jpg
07:20
<alkisg>
Some nbd io errors are "normal", you'll see them in the VM too
07:20
I reported them and they were fixed in the 4.15 kernel
07:20
But they're harmless
07:20
Some other nbd errors though, like the "invalid socket" ones, are not expected, and are harmful
07:21
https://github.com/NetworkBlockDevice/nbd/issues/57#issuecomment-333409103
07:21
The ones you see there are the harmless ones
07:21
So up until "unable to read partition table", it's ok
07:23
NUMG: hmm give me vnc again, I'd like to try reverting to the 4.4 kernel as I do with schools here
07:23
It may make things more stable
07:23
<NUMG>
VNC or Epoptes ?
07:24
<alkisg>
No difference to me...
07:25
NUMG: are you able to select another kernel at grub?
07:25
I.e. do you have something like console access?
07:25
<NUMG>
No. I don't have the GRUB menu displayed :(
07:25
<alkisg>
You're supposed to see it if you hold down shift
07:25
But I'm not sure if your console will transfer that to the VM
07:25
<NUMG>
Also, I did try with a VMWare on the same ESX, and I don't have any error
07:26
<alkisg>
4.13 has a whole lot of errors
07:26
I'm reverting all the schools to 4.4
07:26
<NUMG>
OK
07:26
<alkisg>
And I think 4.4 won't show the Buffer IO errors at all
07:27
<NUMG>
OK
07:28
Server is starting with 4.4
07:28
<alkisg>
Cool
07:28
Give me vnc again to remove 4.10/4.13, and then we'll run ltsp-update-image
07:31kjackal has left IRC (kjackal!~quassel@fpc121872-nmal24-2-0-cust27.19-2.static.cable.virginm.net, Ping timeout: 268 seconds)
07:39ricotz has joined IRC (ricotz!~ricotz@p5B2A81A7.dip0.t-ipconnect.de)
07:39ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:41
<alkisg>
NUMG: so after ltsp-update-image finishes, try booting the clients, and see if you get nbd errors
07:41
Btw, you need to run apt dist-upgrade, to properly update your server
07:41
Do it later though
07:43
<NUMG>
OK
07:44
It seems to be OK. I'm going to try to reboot my ThinClient
07:46
<alkisg>
It should solve the buffer io errors on boot, but it shouldn't really help with network stability, maybe only a bit
07:51
<NUMG>
Now I have the Grub Menu on my ThinClient
07:52
<alkisg>
We don't provide grub over the network, so that sounds very strange :)
07:52
Check again
07:54
<NUMG>
https://framapic.org/X69a8mb4k1bX/X2YvDv7yVGol.png
07:54
<alkisg>
That's a pxelinux menu
07:54
It means you enabled the menu from /etc/ltsp/update-kernels
07:54
<NUMG>
Oh OK. I didn't have that before
07:54
<alkisg>
Move the mouse on the server for me to see vnc and verify it
07:55
(now it's in screensaver mode)
07:55
PXELINUX_DEFAULT=menu
07:55
That's normally disabled
07:55
You enabled it yesterday or something, and it took effect today with ltsp-update-image
07:56
<NUMG>
Maybe yes :) I made somes tests...
07:57
It seems that I don't have anymore NBD errors on my ThinClients
07:58
<alkisg>
Yes, the 4.4 kernel solved that
07:58
Cool, keep it that way :)
08:00
<NUMG>
Altough, I still have a problem but only on my ThinClient HP t520. When booting "LTSP, using NBD", it take a long time on the step "Loading vmlinuz-xxx" and a really long time on "Loading initrd-xxx". And, often it restart completely (maybe a timeout). Is this the fault of my cheap network ?
08:01
<alkisg>
Did that client boot before, with the 4.12 kernel, even with errors?
08:01
<NUMG>
No, it was the same
08:01
<alkisg>
Is it 64bit or 32bit?
08:02
<NUMG>
64
08:02
<alkisg>
Wait when you say "often it restarts", it means that some times it boots?
08:03
<NUMG>
sometimes it boot, and sometimes it stay on "Loading initrd or vmlinuz" during a long time then restart
08:03
<alkisg>
OK then yes I assume it's bad networking
08:03
Try putting it directly to the switch
08:04
<NUMG>
Is there an option in the PXE Menu where I could switch a verbose parameters to see what's going on ?
08:05
<alkisg>
Sure, press e to edit the menu options, and remove "quiet splash"
08:05
Nah never mind you don't have quiet splash anyway
08:05
Try adding "debug", sometimes it produces more output
08:08
<NUMG>
I will have try to do some bandwidth and quality test between my switch and the LTSP server
08:09
<alkisg>
NUMG: epoptes has an integrated bandwidth test
08:09
<NUMG>
Great !
08:09
Awesome tools
08:09
<alkisg>
Thanks, it took us years to develop them :D
08:10
NUMG: hehe, 10g on the server, 1 g on the client ==> yet 100 mbps connection
08:11
Something is indeed wrong between them
08:11
Maybe the server 10 g is fake and in reality it's just 100 mbps
08:12
<NUMG>
10G is fake since it's virtualized
08:12
<alkisg>
It's best to give a real estimate to the VM
08:12
otherwise it attempts to start sending at 10 g
08:12
and may cause retransmissions
08:12
<NUMG>
Indeed, I will have a look but it seems that the switches are on 100mbps
08:13
OK
08:14
<alkisg>
The client switch is gigabit, it connected to 1 g
08:31
<NUMG>
I just did an Iperf test on the ThinClient, and I have a 100Mbps bandwidth. Is this enough ?
08:31
<alkisg>
Sure
08:32
It's the quality that matters
08:35
<NUMG>
In UDP, 0.073ms of Jitter and 0 Lost diagrams !
09:09
I'm going to do some tests and give you some results after that. Thank you for your help.
09:10NUMG has left IRC (NUMG!29bc26c7@gateway/web/freenode/ip.41.188.38.199, )
09:15kjackal has joined IRC (kjackal!~quassel@165.225.80.246)
09:26kjackal has left IRC (kjackal!~quassel@165.225.80.246, Ping timeout: 260 seconds)
09:58adminaula has joined IRC (adminaula!9effeffe@gateway/web/freenode/ip.158.255.239.254)
10:01Statler has left IRC (Statler!~Georg@p5B30EA68.dip0.t-ipconnect.de, Remote host closed the connection)
10:02adminaula has left IRC (adminaula!9effeffe@gateway/web/freenode/ip.158.255.239.254, Ping timeout: 260 seconds)
10:04GodFather has left IRC (GodFather!~rcc@wsip-24-249-172-216.ph.ph.cox.net, Read error: Connection reset by peer)
10:04GodFather has joined IRC (GodFather!~rcc@wsip-24-249-172-216.ph.ph.cox.net)
10:26kjackal has joined IRC (kjackal!~quassel@165.225.80.248)
10:31Statler has joined IRC (Statler!~Georg@gwrz3.lohn24.de)
10:36kjackal has left IRC (kjackal!~quassel@165.225.80.248, Quit: No Ping reply in 180 seconds.)
10:37kjackal has joined IRC (kjackal!~quassel@165.225.80.252)
11:11kjackal has left IRC (kjackal!~quassel@165.225.80.252, Ping timeout: 264 seconds)
11:15kjackal has joined IRC (kjackal!~quassel@165.225.80.119)
11:29kjackal has left IRC (kjackal!~quassel@165.225.80.119, Ping timeout: 276 seconds)
12:38lucascastro has joined IRC (lucascastro!~lucas@201.182.221.154)
15:38jgee has joined IRC (jgee!~jgee@181.56.72.152)
16:05Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
16:16Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
17:18Till_ has joined IRC (Till_!25c9d717@gateway/web/freenode/ip.37.201.215.23)
17:21Till_ has left IRC (Till_!25c9d717@gateway/web/freenode/ip.37.201.215.23, Client Quit)
17:57vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
18:12lucascastro has left IRC (lucascastro!~lucas@201.182.221.154, Remote host closed the connection)
18:32Statler has left IRC (Statler!~Georg@gwrz3.lohn24.de, Remote host closed the connection)
18:50lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
18:54ABIX_Adamj has joined IRC (ABIX_Adamj!~quassel@abix-vps.abix.info.pl)
18:57ABIX_Adamj_ has left IRC (ABIX_Adamj_!~quassel@abix-vps.abix.info.pl, Ping timeout: 268 seconds)
19:03Statler has joined IRC (Statler!~Georg@p5B30EA68.dip0.t-ipconnect.de)
19:07Ray_ has joined IRC (Ray_!ccf97f0e@gateway/web/freenode/ip.204.249.127.14)
19:07
<Ray_>
trying to boot client but errors out (PXE E51)
19:08
any ideas
19:08
<vagrantc>
dhcp server not configured?
19:08
or multiple dhcp servers on the same network?
19:10
<Ray_>
i configured dhcp on the /etc/ltsp.dhcpd.conf fi
19:10
sorry /etc/ltsp/dhcpd.conf
19:11
<vagrantc>
what distro? software version?
19:11
<Ray_>
ubuntu 17.10
19:11
and ran the root@server #apt install ltsp-manager
19:12
<vagrantc>
i'm not sure if ltsp-manage supports isc-dhcp-server ... typically it uses dnsmasq
19:12
ltsp-manager
19:13
!ltsp-manager
19:13
<ltsp>
ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager
19:13
<vagrantc>
Ray_: those are the install instructions for using ltsp-manager
19:13
<Ray_>
so should i isc-dhcp-server or configure dnsmasq
19:14
install
19:14
ahh okay i see
19:16
<vagrantc>
ltsp-manager is made to minimize the number of manual steps
19:17
<Ray_>
okay so i can use ltsp-manager to set up my thin client enviroment
19:22lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Ping timeout: 268 seconds)
19:23lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
19:25ray__ has joined IRC (ray__!ccf97f0e@gateway/web/freenode/ip.204.249.127.14)
19:28Ray_ has left IRC (Ray_!ccf97f0e@gateway/web/freenode/ip.204.249.127.14, Ping timeout: 260 seconds)
20:25lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Remote host closed the connection)
21:00adrianor1 has joined IRC (adrianor1!~adrianorg@177.18.174.216)
21:02ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
21:03adrianorg has left IRC (adrianorg!~adrianorg@186.215.16.144, Ping timeout: 268 seconds)
21:27adrianor1 has left IRC (adrianor1!~adrianorg@177.18.174.216, Ping timeout: 240 seconds)
21:30adrianorg has joined IRC (adrianorg!~adrianorg@177.18.174.216)
22:20vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
22:56Statler has left IRC (Statler!~Georg@p5B30EA68.dip0.t-ipconnect.de, Remote host closed the connection)