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


Channel log from 29 September 2017   (all times are UTC)

01:51adrianor1 has joined IRC (adrianor1!~adrianorg@177.204.156.23.dynamic.adsl.gvt.net.br)
01:53kjackal_ has joined IRC (kjackal_!~quassel@207.110.29.138.ptr.us.xo.net)
01:54adrianorg has left IRC (adrianorg!~adrianorg@187.113.218.186, Ping timeout: 240 seconds)
02:09vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
04:03kjackal_ has left IRC (kjackal_!~quassel@207.110.29.138.ptr.us.xo.net, Ping timeout: 240 seconds)
05:23Statler has joined IRC (Statler!~Georg@p579FE8E2.dip0.t-ipconnect.de)
05:24
<alkisg>
markit, no, I haven't heard that issue
05:52ricotz has joined IRC (ricotz!~ricotz@p5B2A9CFC.dip0.t-ipconnect.de)
05:52ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:30mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
06:32Eric4 has joined IRC (Eric4!~eric@sdi.iut-valence.fr)
06:41wim1 has joined IRC (wim1!~Thunderbi@WEGC203033.UNI-GRAZ.AT)
07:21
<bcg>
alkisg: I have to reboot clients to see new NBD image, right? But what happens if I don't reboot? Will they see old image / corrupted image / crash?
07:22
I mean, if I have logged in users when I update nbd
07:22
<alkisg>
old image with no corruption
07:22
<bcg>
Great.
07:22
So there is no downtime for clients.
07:22
<alkisg>
Right
07:23
You can even delete the old image, linux will free it when the clients get rebooted
07:24
<bcg>
Yes, I know. I just wanted to be sure as I have 24/7 users.
08:35Statler_ has joined IRC (Statler_!~Georg@p579FFB65.dip0.t-ipconnect.de)
08:36Statler has left IRC (Statler!~Georg@p579FE8E2.dip0.t-ipconnect.de, Remote host closed the connection)
08:36Statler_ has left IRC (Statler_!~Georg@p579FFB65.dip0.t-ipconnect.de, Client Quit)
08:37Statler has joined IRC (Statler!~Georg@p579FFB65.dip0.t-ipconnect.de)
08:48lkamona has joined IRC (lkamona!c23feff3@gateway/web/freenode/ip.194.63.239.243)
09:45fnurl_y has joined IRC (fnurl_y!~fnurl@36-225-222-145.dynamic-ip.hinet.net)
09:47fnurl has left IRC (fnurl!~fnurl@36-225-222-145.dynamic-ip.hinet.net, Ping timeout: 248 seconds)
11:11gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
11:41sebd has joined IRC (sebd!~seb@aditu.ldd.fr)
11:46
<sebd>
Hello, I am upgrading a debian LTSP server from jessie to stretch. Everything went fine until I regenerate the chroot and NDB image - the new image does not work : client screen remains blank
11:48* sebd looking through past days' irc logs
11:56
<sebd>
using jessie's kernel fixes the issue
12:00
and using jessie's ndb clientimage works better too
12:00
of course
12:02
<alkisg>
sebd: did you run ltsp-build-client to create a new chroot?
12:04kjackal_ has joined IRC (kjackal_!quassel@conference/ubuntu-rally/x-ihxcdccmeafdbwux)
12:07
<sebd>
yes I did
12:08
alkisg: yes I did, and it went fine
12:08
now trying kernel 4.12.0-0.bpo.1-amd64
12:09
<alkisg>
sebd: the client boots fine and it just has a blank screen?
12:11
<sebd>
yes
12:11
with the default kernel
12:12
<alkisg>
sebd: can you see the client screen with epoptes?
12:12
I've seen some issues with blank screen on ubuntu, on skylake clients...
12:12
Running just "xrandr" in lts.conf fixed the issue
12:14
<sebd>
same with latest bpo kernel
12:14
Xorg started by ldm, but display staying blank
12:14
<alkisg>
(03:12:14 μμ) alkisg: sebd: can you see the client screen with epoptes?
12:15* sebd looks what is epoptes
12:16
<sebd>
not using epoptes
12:17
<alkisg>
!epoptes
12:17
<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
12:17
<alkisg>
It's extremely handy for accessing ltsp clients
12:17
E.g. you'd click on "monitor client" and you might see that it displays a xorg screen, just not on the real monitor
12:17
<sebd>
I can login on 1st console (Ctrl+Alt+F1). text mode works. Trying xrandr now.
12:18
<alkisg>
You can't run xrandr from vt1 just like that
12:18
You need the proper DISPLAY and XAUTHORITY
12:20
<sebd>
I know, I am adding XRANDR_COMMAND_0 in lts.conf server-side
12:26
not helping
12:26
well, now we see something, but screen is split in two and colors are all wrong
12:26
trying with another terminal
12:30
mmm I/O errors with ndb0
12:30
mm I'll start with regenerating the image
12:33
<alkisg>
I/O errors might be normal, bug in nbd
12:33
sebd: is this a thin client or a fat client?
12:33
You might need X_SMART_COLOR_DEPTH=False
12:34
<sebd>
ok
12:34
both fat and thin (same single image, kernel parameters select fat or thin)
12:35
<alkisg>
And with fat you have split screen?
12:35
<sebd>
video mode not well initialized, screen is using only one quarter of the screen and is duplicated on both sides
12:36
<alkisg>
What's the output of `xrandr` at that point?
12:36
It sounds like a thin client with 16 bpp
12:36
<sebd>
yes
12:36
possible
12:36
<alkisg>
That's why I asked if it's fat
12:37
<sebd>
but I cannot get past ldm. Currently regenerating ltsp chroot
12:37
there are other issues
12:46* alkisg thinks sebd is multitasking too much to properly troubleshoot the issues in a step-by-step basis
12:51
<sebd>
I agree
12:57
X_SMART_COLOR_DEPTH=False fixed the initial issue (screen mode)
12:57
the second issue is caused by sshd
12:58markit has joined IRC (markit!~marco@88-149-177-66.v4.ngi.it)
12:59mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Remote host closed the connection)
13:01mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy)
13:06
<sebd>
sshd issue fixed
13:12
thin clients work fine
13:12
but logging out from xfce4, ldm does not reappear (screen remains blank)
13:16
actually it works, but is very slow
13:16
(respawning ldm is very slow and cpu intensive) (on a w$ vista era laptop)
13:17
ok LTSP on debian 9 works
13:21ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
13:23adrianor1 is now known as adrianorg
13:41
<sebd>
now everything seems to work fine, even logging out and getting ldm back, and rebooting.
13:53
"/etc/rc.local : no such file or directory" at boot on thin clients
13:55wim1 has left IRC (wim1!~Thunderbi@WEGC203033.UNI-GRAZ.AT, Quit: wim1)
14:46mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
15:14Statler has left IRC (Statler!~Georg@p579FFB65.dip0.t-ipconnect.de, Remote host closed the connection)
15:40
<gvy>
install -pm755 /dev/null /etc/rc.local
15:57fzimper has joined IRC (fzimper!4e2b136d@gateway/web/freenode/ip.78.43.19.109)
16:11
<sebd>
thank you gvy
16:15
<gvy>
yw
16:23markit has left IRC (markit!~marco@88-149-177-66.v4.ngi.it, )
16:35silvia_ has joined IRC (silvia_!4e0d86ac@gateway/web/freenode/ip.78.13.134.172)
16:39
<silvia_>
Hi, need some advice for ltsp setup in my school.
16:39lucascastro has joined IRC (lucascastro!~lucas@170.78.53.20)
16:39
<silvia_>
I need to reuse old netbooks asus 1001 px as thin client
16:40
Everything works but it's extremely slow on videos
16:40
(youtube, I mean)
16:41
I discover today they're 64bit, they have 1M RAM
16:42
When used with XP, videos are ok
16:42
Do you think it's a good idea to make them fat clients?
16:43
<alkisg>
!ltsp-pnp
16:43
<ltsp>
ltsp-pnp: ltsp-pnp is the recommented method to install and maintain LTSP for "usual" setups. Since it doesn't involve chroots, it requires little to no command line to maintain it. It automatically supports both thin and fat ltsp clients. https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
16:43
<alkisg>
!ltsp-manager
16:43
<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
16:44
<alkisg>
silvia_: yes, follow one of those guides
16:44
what's their cpubenchmark score?
16:45
<silvia_>
How can I get it?
16:46
But no need for ltsp-pnp, because everything work now and, at the beginning, I thought they were 32-bit
16:49
<gvy>
well 64-bit chroot might help multimedia (for more registers and faster baseline command set)
16:50
<silvia_>
ok, I'll rebuild chroot tomorrow
16:53
Is the benchmark for Atom N450 possibly 297?
16:55
<alkisg>
Yes, it's a very old and lame processor
16:55
Similar to pentium 4, but with lower power consumption
16:56
<silvia_>
yes, that's the main need for thin client
16:56
<alkisg>
They should be able to barely play youtube full screen with no lost frames
16:56
How many clients?
16:56
<silvia_>
26
16:56
<alkisg>
And what's the server cpu benchmark?
16:56
And how much ram on the server?
16:57
And how many gigabit nics on the server?
16:57
<silvia_>
8Gbyte RAM, 1 NIC
16:57
<alkisg>
And cpu?
16:58
(those are not enough for 26 users already... without looking at the cpu)
16:58
<silvia_>
No clue about CPU
16:58
<alkisg>
(so I'd use fat clients even with just that info)
16:58
Is it a monster server,or some plain i3/i5 thing?
16:59
<silvia_>
Don't know, is a big server outside, and that's all I know, right now
17:00
<alkisg>
With that info, I'd use fat clients
17:00
And with 8gb ram on the server and 1 gb on the clients, I'd use 32bit ltsp-pnp
17:00
<silvia_>
But it's a real server, not a pc used as a server
17:00
<alkisg>
It saves ram
17:00
8 gb doesn't sound like a recent server
17:00
If you had 32gb and 10000+ cpubenchmark score and 2-3 bonded nics, I might advice thin clients then...
17:01
<silvia_>
Ok, maybe I'm wrong, I'll check tomorrow but was bought last year
17:01
<alkisg>
Your thin clients now have 297 score
17:01
297*26 = 7722
17:01
So your server must have higher score than that to perform better
17:02
<silvia_>
ok, I've an idea I thank you veeeeery much
17:02
<alkisg>
np
17:02
<silvia_>
I now know what to check and consider
17:02
I really thank you
17:05lucas__ has joined IRC (lucas__!~lucas@200.141.207.18)
17:07silvia_ has left IRC (silvia_!4e0d86ac@gateway/web/freenode/ip.78.13.134.172, Quit: Page closed)
17:08lucascastro has left IRC (lucascastro!~lucas@170.78.53.20, Ping timeout: 255 seconds)
17:23gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
17:33zibis has joined IRC (zibis!~zibi@mail.linseco.pl)
17:34zibis has joined IRC (zibis!~zibi@mail.linseco.pl)
17:35fzimper has left IRC (fzimper!4e2b136d@gateway/web/freenode/ip.78.43.19.109, Ping timeout: 260 seconds)
17:39pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, Quit: Leaving)
17:41sbalneav1 has left IRC (sbalneav1!~sbalneav@wnpgmb0311w-ds01-165-236.dynamic.bellmts.net, Ping timeout: 264 seconds)
17:55sbalneav1 has joined IRC (sbalneav1!~sbalneav@wnpgmb0311w-ds01-165-236.dynamic.bellmts.net)
17:58lucascastro has joined IRC (lucascastro!~lucas@200.141.207.18)
17:58lucas__ has left IRC (lucas__!~lucas@200.141.207.18, Read error: Connection reset by peer)
18:01pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme)
18:43fzimper has joined IRC (fzimper!4e2b136d@gateway/web/freenode/ip.78.43.19.109)
18:43
<fzimper>
Hi alkisg, regarding our chat yesterday. Have you seen the bug I raised and the suggested fix? Is that ok?
18:44
<alkisg>
fzimper: eeeh sorry I didn't see it, link?
18:55vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
18:57
<alkisg>
Whoops just saw this one: https://github.com/NetworkBlockDevice/nbd/issues/51
18:58
systemd kills nbd roots?! :/
18:58* alkisg wonders if nohup would work...
19:00Stephen has joined IRC (Stephen!5ad76ee5@gateway/web/freenode/ip.90.215.110.229)
19:01
<Stephen>
message to Alkisg. Just reinstalled 32 bit Ubuntu Mate 16.04. Installed the PNP LTSP GUI with the new patch I saw you posted on the installation page. It worked perfectly out of the box!
19:02
Outstanding work. I cannot express my gratitude enough. This really is the easiest implementation of LTSP I have ever used.
19:02
My sincere thanks to you Alkisg....:)
19:04
and also any of other ltsp devs if they are online
19:10
<alkisg>
Stephen: you're welcome! :)
19:11* vagrantc can't take much credit for ltsp-manager
19:13
<Stephen>
I can't believe a numpty like me can now install and get LTSP up and running in less than 15 minutes (including the building of the image). Incredible work. I am a teacher and this is now suffiiently easy to implement I can use it to showcase LTSP and Linux to schools I work in. Thank you again!
19:14
<alkisg>
Stephen: you might want to start putting pins on the map:
19:14
http://www.ltsp.org/stories/widget-map/?location=Greece
19:14
<Stephen>
hahaha will do
19:14
<alkisg>
May your map be as crowded as ours :D
19:20
<fzimper>
Sorry, been away. Here's the link: https://bugs.launchpad.net/ltsp-manager/+bug/1720209
19:22
<vagrantc>
fzimper: ooh, a patch!
19:22
fzimper: great work!
19:23
<alkisg>
Heh, weird, didn't get a notification for this one
19:23
<fzimper>
Not a very big one, but it survived a bunch of 9th-graders today :-D
19:23
<alkisg>
fzimper: cool, thanks for the patch
19:24
<fzimper>
np
19:25* alkisg put himself as the bug supervisor, I think that would be enough to get notifications...
19:25
<alkisg>
(supervisor for all ltsp-manager bugs)
19:25
<fzimper>
There's some other issue I noticed with epoptes.. It often closes when a user signs off or shuts down her PC. Is that a known issue?
19:26
<alkisg>
I'm not sure which epoptes process you mean there
19:27
epoptes-daemon running on the server, epoptes gui running by the teacher, root epoptes-client running on the client, session epoptes-client running on the client
19:27
<fzimper>
epoptes gui
19:27
Might be this one: https://github.com/Epoptes/epoptes/issues/21
19:27
Though it's not when I log them out
19:28
<alkisg>
I've never seen the GUI close when clients do anything
19:28
Any error messages?
19:29
<fzimper>
No, nothing
19:29
Will check the logs. Sorry, just wanted to know if that's a known issue.
19:29
<alkisg>
There's a /var/log/epoptes.log file
19:29
<fzimper>
ok
19:29
<alkisg>
No, it's not, never heard of it
19:30
<fzimper>
So I'll try to get more detail and then add to the open bug or open a new one. Github is the right place for epoptes bugs, right?
19:31
<alkisg>
Eh, I suppose so... I preferred launchpad but Fotis moved it to github...
19:31
and we haven't decided yet to move it back to launchpad... :D
19:31
So wherever you want :)
19:32
<fzimper>
I'm more familiar with Github, but use whatever is more appropriate.
19:32
<alkisg>
It's fine, use that
19:51Stephen has left IRC (Stephen!5ad76ee5@gateway/web/freenode/ip.90.215.110.229, Quit: Page closed)
20:11
<fzimper>
Regarding that epoptes issue: I run epoptes from a fat client unsing ltsp-remoteapps - so it actually runs on the server. When a client logs off the epoptes GUI closes. Here's the epoptes.log: http://termbin.com/n2f03
20:17kjackal_ has left IRC (kjackal_!quassel@conference/ubuntu-rally/x-ihxcdccmeafdbwux, Ping timeout: 258 seconds)
21:00lucascastro has left IRC (lucascastro!~lucas@200.141.207.18, Remote host closed the connection)
21:09zibis has left IRC (zibis!~zibi@mail.linseco.pl, Quit: zibis)
21:10vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 260 seconds)
21:22vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
21:42fzimper has left IRC (fzimper!4e2b136d@gateway/web/freenode/ip.78.43.19.109, Ping timeout: 260 seconds)
21:52ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
23:10vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
23:12ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection)