LTSP 5 is in minimal maintenance mode
The new LTSP is hosted at https://ltsp.github.io

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


Channel log from 12 April 2019   (all times are UTC)

00:58mmarconm has left IRC (mmarconm!~mmarconm@unaffiliated/mmarconm, Quit: Leaving)
04:12vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
04:48vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
05:22os_a has joined IRC (os_a!~Thunderbi@141.101.206.111.leadertelecom.ru)
05:23os_a has left IRC (os_a!~Thunderbi@141.101.206.111.leadertelecom.ru, Client Quit)
05:32pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, Ping timeout: 240 seconds)
05:32os_a has joined IRC (os_a!~Thunderbi@141.101.206.111.leadertelecom.ru)
05:36os_a has left IRC (os_a!~Thunderbi@141.101.206.111.leadertelecom.ru, Client Quit)
05:45pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme)
05:45ricotz has joined IRC (ricotz!~ricotz@p5B2A8DE5.dip0.t-ipconnect.de)
05:46ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:07woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de)
06:13vsuojanen has left IRC (vsuojanen!~vsuojanen@cable-hml-585686-205.dhcp.inet.fi, Ping timeout: 250 seconds)
06:35map7 has left IRC (map7!~user@103.232.216.31, Remote host closed the connection)
07:08Basnap has joined IRC (Basnap!511476ce@gateway/web/freenode/ip.81.20.118.206)
07:08
<Basnap>
Hi there!
07:08
I am tryying for roughly 5 workdays to get VNC working on LTSP-clients
07:09
if you got any advice or can help I am grateful for that.
07:09
it looks like the VNC server needs to be started by the same person with gui/x-server. But who is the username of the user getting the ldm login screen of LTSP?
07:14
<alkisg>
!epoptes
07: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
07:14
<alkisg>
Basnap: why would you use vnc instead of epoptes, which natively supports ltsp?
07:14
<Basnap>
Oh sorry!
07:14
<alkisg>
Then you can just click and get vnc access to any client, logged in or not, with much less resources etc
07:15
<Basnap>
We have an edubuntu server on a customer of us
07:15
and would like to look at the clients directly from our company via VNC, anydesktop or the like
07:15
<alkisg>
Are they using epoptes? If not, you can just setup epoptes so that it connects to you
07:16
<Basnap>
(it doesn't help that the customer is supposed to have crappy internet, so going with vnc to the LTSP server itself (whcih works!) and then starting epoptes...well, will prob be very very slow)
07:16
They = the customer?
07:16
<alkisg>
Yes
07:16
I mean, the server AND all the clients would be configured so that they'd be epoptes-clients of you
07:16
So you'd just click on any of them that you want
07:16
<Basnap>
Just to get you right, you are suggesting the server and clients connect to a server within our company?
07:17
<alkisg>
Yes
07:17
<Basnap>
that's an idea at last - can epoptes be controlled from windows systems?
07:17
<alkisg>
It's also easier, it doesn't require port forwarding on the client
07:17
The epoptes server needs to be a linux pc
07:17
<Basnap>
We don't need to do port forwarding because we will get into their network via VPN
07:17
<alkisg>
But you can access that linux pc from windows if you want
07:18
<Basnap>
http://www.epoptes.org/documentation/windows-client
07:18
"No Windows port of epoptes-client currently exists and the developers have no plans to implement one in the near future. However, in case anyone's up to the task, here are some key parts that are needed. "
07:18
<alkisg>
Nah, this didn't work out
07:18
Noone was interested :)
07:18
Another way would be to login to their server, run epoptes from there, and then if you want to control a client you'd run the vnc command to the client via epoptes
07:19
This allows you to only use windows in your office
07:19
<Basnap>
Yes, but that's not optimal and they got slow internet.
07:20
<alkisg>
The vnc connection would be direct
07:20
<Basnap>
Anyways, also because I am interested whether it works then, what's the LTSP username of the user running LDM/x-server?
07:20
<alkisg>
The only downside is that you need to login to the server first, in order to run the command to the client
07:20
It's "root"
07:20
<Basnap>
meh
07:20
<alkisg>
Well, xorg has been running as root for decades
07:20
<Basnap>
Tried root before but didnt work with vnc, either X-org is not running completely or the authentification fails
07:21
<alkisg>
It's only recently that some distros started running it as non-root
07:21
<Basnap>
edubuntu 14.04.
07:21
<alkisg>
You probably didn't manage to set up vnc server properly
07:21
<Basnap>
it works on the LTSP server at least.
07:22
Are you familiar with VNC servers?
07:22
<alkisg>
Sure, how else would I program epoptes? :)
07:22
<Basnap>
I didnt know you did!
07:22
App looks solid bro!
07:22
<alkisg>
LTSP too :)
07:22
<Basnap>
great job methinks!
07:23
one issue with LTSP I had was figuring out how to change keyboard layout and enable numlock
07:23
like not looking where to look or where that login screen came from, but I solved it after 1 or 2 workdays
07:24
"x11vnc was unable to open the X DISPLAY; ":0" it cannot continue. There may be Xlib error messages above with details about the failure"
07:24
An X server (the one you with to view) must be running before x11vnc is starter, x11vnc does not start the x server). try -create to start it blabla
07:25
<alkisg>
Yes, you didn't manage to properly access the x server
07:25
It's tricky; epoptes automates all that
07:25
<Basnap>
You mjust use -display OR set and export $display to refer to the display of the desired X server. Usually display is :0, x11vnc use this by defailt
07:26
You need sufficient permissions (Xauthority) to connect to the X display
07:26
<alkisg>
Btw I sent you a personal message about profressional support if you're interested
07:26
<Basnap>
You often need to run x11vnc as the user logged into the X sesssion. So make sure to be that user when you type x11vnc
07:28
"Being root is usually not enough because the incorrect MIT-MAGIC-COOKIE file may be accessed" The cookie file contains the secret key that allows x11vnc to connect to the desired x display.
07:29
<alkisg>
Those are just standard messages that mean your DISPLAY/XAUTHORITY are wrong
07:29
No need to paste more of them...
07:29
<Basnap>
you can specific the MIT MAGIC COOKIE file with -auth blabla. I figured it seems to be /var/run/ldm-x-something
07:29
ah k
07:29
just wanted to provide some info.
07:30
So you are very sure root is the user executing the login screen as well as active the whole time during the login?
07:30
<alkisg>
Yup
07:31
The proper way to use a vnc server on the clients would be to run it when ldm runs,on the same context, and provide a way to enable/disable it via lts.conf
07:31
This work could go upstream in ltsp, and it would take an hour for scripting and one for testing
07:32
But this would need more resources than epoptes-client needs, as epoptes-client is a shell than can run vnc on demand
07:32
While in your solution the vnc server would always be running, wasting resources
07:34
<Basnap>
I might try to run epoptes under windows by cygwin
07:34
Or VM? Maybe. I am not sure yet how to configure epoptes to send data to another server, though.
07:34
<alkisg>
You can run it on the ltsp server, VNC to the ltsp server, and then do a direct VNC connection from windows to the ltsp clients, without the traffic passing from the ltsp server
07:35
<Basnap>
How?
07:35
<alkisg>
That's what I was suggesting half an hour ago ;)
07:36
This is a custom solution though, I don't have enough time to give free support for custom solutions. This doesn't require any coding.
07:36
Ping me if you're interested in professional support; or wait in case someone else can help more
07:36
<Basnap>
Ah ok, I thought you were referring only to VNC regarding a custom solution
07:37
<alkisg>
VNC will run on windows, yes
07:37
<Basnap>
And that the thing with epoptes would work already
07:37
<alkisg>
Epoptes would work fine; it's the "access the clients via windows" part that's non standard and needs documentation
07:42
<Basnap>
OK, I'll try to get epoptes running on Cygwin at the same time while trying to get VNC working properly. I'll try to let you know if I can use it with Cygwin, so you might could add it to the "windows client" page I linked before if it does!
07:43
<alkisg>
np
07:49kjackal has joined IRC (kjackal!~quassel@88.197.12.12)
07:53
<Basnap>
There seems to be only an .Xauthority file for the user "test" as I was able to find (literally!) out.
07:56kjackal has left IRC (kjackal!~quassel@88.197.12.12, Ping timeout: 250 seconds)
07:56kjackal has joined IRC (kjackal!~quassel@88.197.36.111)
08:20Basnap has left IRC (Basnap!511476ce@gateway/web/freenode/ip.81.20.118.206, Ping timeout: 256 seconds)
08:34yanu has joined IRC (yanu!~yanu@178-116-60-189.access.telenet.be)
09:00Basinator2 has joined IRC (Basinator2!511476ce@gateway/web/freenode/ip.81.20.118.206)
09:00
<Basinator2>
Hi, me again! Got a dc and now on anothewr machine.
09:00
I wondered and setting it up now.
09:00
What if I install a VM with a *Ubuntu and try to run epoptes on it, wouldn'
09:01
't i be able to connect to epoptes clients of the LTSP server directly?
09:01
That's at least my current idea. Also: Can an epoptes client have 2 epoptes servers?
09:05
<alkisg>
Ubuntu VM inside windows => sure, as long as you have bridged networking,
09:05
2 epoptes servers => nope, not without a bit of hacking
09:11statler has joined IRC (statler!~Georg@gwrz.lohn24.de)
10:10kjackal has left IRC (kjackal!~quassel@88.197.36.111, Ping timeout: 250 seconds)
10:43kjackal has joined IRC (kjackal!~quassel@2a02:587:3119:ef00:6876:85e2:1a8:5382)
11:05os_a has joined IRC (os_a!~Thunderbi@141.101.206.111.leadertelecom.ru)
11:41os_a has left IRC (os_a!~Thunderbi@141.101.206.111.leadertelecom.ru, Remote host closed the connection)
11:41os_a has joined IRC (os_a!~Thunderbi@195.112.116.22)
12:56woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Remote host closed the connection)
13:04Basinator2 has left IRC (Basinator2!511476ce@gateway/web/freenode/ip.81.20.118.206, Ping timeout: 256 seconds)
13:15os_a has left IRC (os_a!~Thunderbi@195.112.116.22, Remote host closed the connection)
15:21woernie has joined IRC (woernie!~werner@pD9E8BADB.dip0.t-ipconnect.de)
16:33vsuojanen has joined IRC (vsuojanen!~vsuojanen@cable-hml-585686-205.dhcp.inet.fi)
16:53Leandro_ has joined IRC (Leandro_!c891b51d@gateway/web/freenode/ip.200.145.181.29)
16:55
<Leandro_>
Hello guys. I'm having trouble to boot some thinclients. The client says: "Loading initrd.img-4.15.0-47-generic...ok." and nothing happens after that.
16:56
The server boots fine on some HP All-in-one, but not booting on HP Thinclient
16:58
<alkisg>
!quiet-splash
16:58
<ltsp>
quiet-splash: to disable the splash screen in Ubuntu, in order to see any boot error messages, run sudo gedit /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default and remove quiet splash plymouth:force-splash vt.handoff=7
16:58
<alkisg>
First, try to remove that; then, try with an older kernel; finally, try with -47 with a local installation (e.g. usb stick, local or external disk...)
17:01fnurl has left IRC (fnurl!url@host81-154-10-70.range81-154.btcentralplus.com, Read error: No route to host)
17:10
<Leandro_>
ok I'll try that
17:16fnurl has joined IRC (fnurl!url@host81-154-10-70.range81-154.btcentralplus.com)
17:21
<Leandro_>
Pardon my ignorance, but in the default file, should I add plymouth:force-splash vt.handoff=7 at the end of the file? Cause there is no "quiet splash" on it
17:24
<alkisg>
Leandro_: ok then you don't need to try the quiet splash step. Btw, how much ram do those problematic clients have?
17:26vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
17:26
<alkisg>
And, where they booting before, with the previous kernel?
17:29Leandro_ has left IRC (Leandro_!c891b51d@gateway/web/freenode/ip.200.145.181.29, Quit: Page closed)
17:29Leandro_ has joined IRC (Leandro_!c891b51d@gateway/web/freenode/ip.200.145.181.29)
17:29
<Leandro_>
Sorry, dropped connection.
17:29
They have 1GB of RAM.
17:29
<alkisg>
(08:26:35 PM) alkisg: And, where they booting before, with the previous kernel?
17:29
<Leandro_>
And yes, there were booting. There were already working on an old ubuntu 10.10 LTSP installation
17:30
<alkisg>
No, I mean with 4.15.0-46 or so
17:30
Is this the first time you try to boot them with ubuntu 18.04?
17:31
<Leandro_>
Yeah, this is the first time
17:31
<alkisg>
Try to boot them with a live usb stick, it may be a kernel issue, not an ltsp issue
17:31
<Leandro_>
alright. Good Idea
17:32
I'll do that and get back to you
17:32
thanks for now
17:32
<alkisg>
np
17:32book`_ has left IRC (book`_!~book`@68.ip-149-56-14.net, Quit: Leaving)
17:35book` has joined IRC (book`!~book`@68.ip-149-56-14.net)
17:46woernie has left IRC (woernie!~werner@pD9E8BADB.dip0.t-ipconnect.de, Remote host closed the connection)
18:21
<quinox>
Talking about that...
18:21
who renders those "Loading vmlinuz..." and "Loading initrd" messages?
18:23
I'm a bit triggered by the fact that the vmlinuz message has "-generic...[SPACE]ok" whereas the initrd message has "-generic...[NOSPACE]ok"
18:24
pxelinux I suppose
18:29statler has left IRC (statler!~Georg@gwrz.lohn24.de, Ping timeout: 246 seconds)
18:43kjackal has left IRC (kjackal!~quassel@2a02:587:3119:ef00:6876:85e2:1a8:5382, Remote host closed the connection)
18:43kjackal has joined IRC (kjackal!~quassel@2a02:587:3119:ef00:6876:85e2:1a8:5382)
18:56
<quinox>
I made a checkout of syslinux, distinctively marked all the loading message and built a new pxelinux.0 -- let's test it out tomorrow
19:05statler has joined IRC (statler!~Georg@gwrz.lohn24.de)
19:16statler has left IRC (statler!~Georg@gwrz.lohn24.de, Ping timeout: 255 seconds)
19:31statler has joined IRC (statler!~Georg@gwrz.lohn24.de)
19:32kjackal has left IRC (kjackal!~quassel@2a02:587:3119:ef00:6876:85e2:1a8:5382, Remote host closed the connection)
19:32kjackal has joined IRC (kjackal!~quassel@2a02:587:3119:ef00:6876:85e2:1a8:5382)
19:33
<alkisg>
quinox: the next ltsp that I'm preparing no longer uses syslinux, only ipxe and grub. Those loading messages come from the boot loader, which is probably syslinux in your case
19:33statler has left IRC (statler!~Georg@gwrz.lohn24.de, Remote host closed the connection)
21:24ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)