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