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


Channel log from 27 May 2015   (all times are UTC)

00:43andygraybeal has left IRC (andygraybeal!~andy@h98.39.30.71.dynamic.ip.windstream.net, Quit: Ex-Chat)
00:51gbaman has joined IRC (gbaman!~gbaman@host81-139-225-149.in-addr.btopenworld.com)
01:56gdi2k has left IRC (gdi2k!~gdi2k@49.151.8.95, Ping timeout: 250 seconds)
02:28vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
02:36
<gbaman>
alkisg: you about?
02:37
vagrantc: got an interesting one for you. Got a user testing PiNet in his home. He has a normal household router. He tries to boot the Pi, the Pi sits waiting for DHCP response to get IP address. Works perfectly fine on normal Raspbian and every other computer he owns. Ever seen anything like that before?
02:38
We eventually just installed isc-dhcp-server onto his PiNet server and it worked fine
02:50gbaman has left IRC (gbaman!~gbaman@host81-139-225-149.in-addr.btopenworld.com, Remote host closed the connection)
02:56work_alkisg has joined IRC (work_alkisg!~alkisg@r-dide.ioa.sch.gr)
02:57alkisg has left IRC (alkisg!~alkisg@srv1-dide.ioa.sch.gr, Ping timeout: 265 seconds)
02:57work_alkisg has left IRC (work_alkisg!~alkisg@r-dide.ioa.sch.gr, Read error: Connection reset by peer)
02:58work_alkisg has joined IRC (work_alkisg!~alkisg@srv1-dide.ioa.sch.gr)
03:54gbaman has joined IRC (gbaman!~gbaman@host81-139-225-149.in-addr.btopenworld.com)
03:59gbaman has left IRC (gbaman!~gbaman@host81-139-225-149.in-addr.btopenworld.com, Ping timeout: 272 seconds)
04:26vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 276 seconds)
05:04work_alkisg has left IRC (work_alkisg!~alkisg@srv1-dide.ioa.sch.gr, Ping timeout: 265 seconds)
05:27vervelak has left IRC (vervelak!~vervelak@139.91.68.65, Ping timeout: 276 seconds)
05:27vmlintu has joined IRC (vmlintu!~vmlintu@a91-154-149-253.elisa-laajakaista.fi)
05:31ricotz has joined IRC (ricotz!~rico@p5B2AAC8E.dip0.t-ipconnect.de)
05:31ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)
05:33vervelak has joined IRC (vervelak!~vervelak@139.91.68.65)
05:37vmlintu has left IRC (vmlintu!~vmlintu@a91-154-149-253.elisa-laajakaista.fi, Ping timeout: 272 seconds)
05:41AlexPortable has joined IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-pyhsdjripvdrwkvd)
05:50vmlintu has joined IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi)
06:28epoptes_user0 has joined IRC (epoptes_user0!c2b1d778@gateway/web/freenode/ip.194.177.215.120)
06:44gbaman has joined IRC (gbaman!~gbaman@host81-139-225-149.in-addr.btopenworld.com)
06:49gbaman has left IRC (gbaman!~gbaman@host81-139-225-149.in-addr.btopenworld.com, Ping timeout: 255 seconds)
07:01work_alkisg has joined IRC (work_alkisg!~alkisg@srv1-dide.ioa.sch.gr)
07:05work_alkisg is now known as alkisg
07:17mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
07:31gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
07:47AlexPortable has left IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-pyhsdjripvdrwkvd, Quit: Connection closed for inactivity)
07:48telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
07:48telex has joined IRC (telex!teletype@freeshell.de)
07:50epoptes_user0 has left IRC (epoptes_user0!c2b1d778@gateway/web/freenode/ip.194.177.215.120, Quit: Page closed)
08:15mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
08:46gbaman has joined IRC (gbaman!~gbaman@host81-139-225-149.in-addr.btopenworld.com)
08:49AlexPortable has joined IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-gvkcpjtfncqrhxoc)
08:52gbaman has left IRC (gbaman!~gbaman@host81-139-225-149.in-addr.btopenworld.com, Ping timeout: 276 seconds)
08:56mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
10:00gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
10:03alkisg is now known as work_alkisg
10:11markit has joined IRC (markit!~marco@host179-38-static.243-95-b.business.telecomitalia.it)
11:03gbaman has joined IRC (gbaman!~gbaman@host81-139-225-149.in-addr.btopenworld.com)
11:08gbaman has left IRC (gbaman!~gbaman@host81-139-225-149.in-addr.btopenworld.com, Ping timeout: 276 seconds)
11:17AlexPortable has left IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-gvkcpjtfncqrhxoc, Quit: Connection closed for inactivity)
11:27staffencasa_ has joined IRC (staffencasa_!~staffenca@8-220.ptpg.oregonstate.edu)
11:30sutula_ has joined IRC (sutula_!~sutula@207-118-178-64.dyn.centurytel.net)
11:34jbermudes_ has joined IRC (jbermudes_!~quassel@76.74.178.212)
11:36mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Ping timeout: 250 seconds)
11:36sutula has left IRC (sutula!~sutula@207-118-178-64.dyn.centurytel.net, Ping timeout: 250 seconds)
11:36jbermudes has left IRC (jbermudes!~quassel@76.74.178.212, Ping timeout: 250 seconds)
11:36staffencasa has left IRC (staffencasa!~staffenca@8-220.ptpg.oregonstate.edu, Ping timeout: 250 seconds)
11:36sutula_ is now known as sutula
11:43mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
11:54miup has joined IRC (miup!~rcerny@78.47.161.200)
11:55
<miup>
Hi @all
12:05
we have here a LTSP environment with Debian Jessie, we are mostly using PIII (mostly all at 1GHz) pc's as thin clients, but we have some annoying issues. Mostly because of the high cpu load on the clients. Videos are horrible (2/3 cpu load is X, 1/3 pulseaudio), but that is not the Problem because we don't make any multimedia thingies. The real annoying problem is at scrolling in a urxvt terminal causes 1/2 cpu
12:05
load on X and 1/2 on xatomwait. I was searching about xatomwait, but I cannot find any documentation about it... I mean any documentation about how it works, why it is necessary etc. (reading the source is not really an option). So, has anyone an idea about it?
12:23
Hm... we have to chroot's for compatibility (Jessie & Wheezy) on Wheezy was the above described symptomes, on Jessie, it it is only X that takes ~99% of the CPU time
12:36vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi, Ping timeout: 272 seconds)
13:08khildin has joined IRC (khildin!~khildin@ip-213-49-87-242.dsl.scarlet.be)
13:53gbaman has joined IRC (gbaman!~gbaman@host81-139-225-149.in-addr.btopenworld.com)
13:58gbaman has left IRC (gbaman!~gbaman@host81-139-225-149.in-addr.btopenworld.com, Ping timeout: 245 seconds)
14:07mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
14:08alkisg_android has joined IRC (alkisg_android!~yaaic@178-171-170.dynamic.cyta.gr)
14:09gbaman has joined IRC (gbaman!~gbaman@host81-139-225-149.in-addr.btopenworld.com)
14:13alkisg_android has left IRC (alkisg_android!~yaaic@178-171-170.dynamic.cyta.gr, Quit: Yaaic - Yet another Android IRC client - http://www.yaaic.org)
14:16work_alkisg is now known as alkisg
14:16
<alkisg>
miup: xatomwait was inefficient so I rewrote it using xprop
14:16
So now it needs 0% cpu
14:16
The rest of the xorg cpu is normal, old clients need 100% cpu to scroll a window
14:17
(and some dual core clients need 50%, i.e. a full core, for that)
14:49khildin has left IRC (khildin!~khildin@ip-213-49-87-242.dsl.scarlet.be, Ping timeout: 272 seconds)
14:52
<alkisg>
It _would_ be nice if xorg synced to vblank and discarded any graphics operations that will never reach the screen, keeping the cpu much less, (like games with fixed FPS do), but it doesn't do that
15:00
<gbaman>
alkisg: You about?
15:17F-GT has left IRC (F-GT!~phantom@ppp121-44-225-201.lns20.syd7.internode.on.net, Ping timeout: 245 seconds)
15:26
<Nickname123>
When installing ltsp I get a warning about ndb-client. Even though it warns and defaults not to, I want to disconnect all NBD devices on "stop" don't I?
15:29F-GT has joined IRC (F-GT!~phantom@ppp121-44-192-63.lns20.syd7.internode.on.net)
15:37
<alkisg>
Nickname123: it doesn't make any difference what you choose there, for ltsp
15:37
LTSP doesn't touch the nbd-client configuration file
15:38
<Nickname123>
Oh. I thought it had something to do with the ltsp client using NBD. Thanks
15:40Nickname123 is now known as gp
15:45
<alkisg>
No it launches it directly using a command line instead of a service+configuration file
15:49markit has left IRC (markit!~marco@host179-38-static.243-95-b.business.telecomitalia.it, Quit: Konversation terminated!)
15:53
<gp>
Is there an easy way to go about restarting clients after a server restart?
16:06
<alkisg>
check the mailing list logs, some methods were mentioned there... cron jobs, sysrq, xnbd-client...
16:08tohtoris has left IRC (tohtoris!~antti@91-158-8-222.elisa-laajakaista.fi, Ping timeout: 265 seconds)
16:09tohtoris has joined IRC (tohtoris!~antti@91-158-8-222.elisa-laajakaista.fi)
16:21telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
16:22telex has joined IRC (telex!teletype@freeshell.de)
16:22gbaman has left IRC (gbaman!~gbaman@host81-139-225-149.in-addr.btopenworld.com, Remote host closed the connection)
16:31Faith has joined IRC (Faith!~paty@unaffiliated/faith)
16:35
<gp>
Ill check it out. Thanks
16:57vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
17:02alkisg is now known as work_alkisg
17:03staffencasa_ is now known as staffencasa
17:19gbaman has joined IRC (gbaman!~gbaman@host81-139-225-149.in-addr.btopenworld.com)
17:52AlexPortable has joined IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-wvkqlfwjcwwyzkkb)
18:21andygraybeal has joined IRC (andygraybeal!~andy@71.30.39.118)
18:35khildin has joined IRC (khildin!~khildin@ip-213-49-87-242.dsl.scarlet.be)
18:42work_alkisg is now known as alkisg
19:12khildin has left IRC (khildin!~khildin@ip-213-49-87-242.dsl.scarlet.be, Remote host closed the connection)
19:26
<gp>
I just did a fresh install from your ppa alkisg. I am using LDM_PASSWORD_HASH to allow fat client screen locking. The problem is it is taking like 5 minutes to unlock the screen. It just says "checking" for 5 minutes and then logs in. Here is my lts.conf http://dpaste.com/1P9R7YB
19:27
Logging into LDM the first time is very fast. From the screen lock it just took 5 minutes
19:28
I am using mate-desktop. Should I be using a different screen locker than the default?
19:28vmlintu has joined IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi)
19:29
<vagrantc>
just using the standard authentication methods?
19:29
no custom pam or nss modules?
19:33
<gp>
I use centrify active directory authentication on the server. I use ltsp-pnp image for the clients. But I thought the ltsp client authenticated with the ltsp server? The client does not join the domain
19:33
So I don't think it is using active directory authentication directly
19:33
If it was, wouldn't the LDM login screen delay for 5 minutes too?
19:34
<alkisg>
gp, try to login in vt1
19:35
<gp>
Okay. One sec. Test client is at a desk away from my laptop
19:35
<alkisg>
after logging in with ldm, press alt+ctrl+f1 and try to login again
19:35
without logging off from the session
19:36
<gp>
While logged into LDM, I swapped to VT1. I was able to log in as the same user quickly. No delay
19:36
<alkisg>
do you see anything weird in the syslog after unlock?
19:37
<gp>
I will check again. I haven't had much luck with the client syslog. Still learning to troubleshoot ltsp effectively
19:37
<alkisg>
gp, for the fat clients it's like usual, tail /var/log/syslog locally
19:37
vagrantc, btw the commits that tried to fix the ldm messages "no response from server" etc, also added a big delay on invalid password
19:38
<vagrantc>
alkisg: yeah, i noticed...
19:38
in fact, even a delay on successful login
19:38
<alkisg>
But only on the first try though, I don't know why
19:38
<vagrantc>
at least, i've been noticing
19:38
<alkisg>
On the second failed try, it's faster, maybe ssh caches something...
19:38
<gp>
trying again
19:39
oh it was really fast the second time
19:39
<vagrantc>
"ltsp-update-image --cleanup /" wouldn't clean out pam/nss stuff, would it?
19:39
<gp>
I haven't tried it multiple times. I always just log out
19:40
<alkisg>
vagrantc/gp, no, pam would need a cleanup script in usr/share/ltsp/cleanup.d
19:40
(btw #2, we should support etc overrides for scripts)
19:40
<gp>
3rd time was very fast also
19:41* vagrantc is always a fan of /etc/ overrides.
19:41
<alkisg>
gp, do you see anything in `tail /var/log/syslog`?
19:41
Or in /var/log/auth.log ?
19:41
I've tried mate 14.04 with the ppa and fat clients, I didn't experience the issue you're mentioning
19:42
If one uses e.g. ldap, and then ldm creates a local user with the same name, shouldn't screen unlocking work without ldap then?
19:42
I.e. isn't it "first check local users, then check ldap" usually?
19:43
<gp>
Alkisg: I didn't. I am letting the client reboot so I can check syslog during the delay
19:44
<vagrantc>
alkisg: it can be configured poorly...
19:55vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi, Ping timeout: 272 seconds)
20:02
<gp>
It seems I had some of the issue symptoms incorrect. Doing a little more digging before reporting back
20:09vmlintu has joined IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi)
20:11alkisg is now known as work_alkisg
20:14ricotz has left IRC (ricotz!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)
20:19
<gp>
So it seems that I overlooked I was swapping users when I was observing the issue back to back. It seems to happen for the first screen lock but it is fast afterwards. I just logged in with 2 different users. The first screen lock for each user took a long time to unlock. Afterwards both unlocked quickly. I checked both users on another fat client after completing the first lock screen on the other machine and the screen
20:19
unlock was quick
20:20
I didn't notice anything odd in syslog but it was gigantic so sort of difficult to know what is important
20:21
Auth log didn't seem too odd. It logged about pam. And that it was trying to use a lock file in the user home. But I didn't see any errors
20:21
<vagrantc>
lock file in the user home *might* be an issue
20:22
you're using the default with sshfs home dirs? sshfs is fuse-based, and doesn't allow even root read access by default ...
20:22
though i thought we changed the default mount options to allow root
20:24
<gp>
I did not change any of the ltsp options
20:24
What should I check to confirm?
20:24vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-70.elisa-laajakaista.fi, Ping timeout: 272 seconds)
20:24
<vagrantc>
log in as the user and run "mount | grep /home"
20:26
<gp>
"server:/home/foo on /home/foo type fuse.sshfs (rw,nosuid,nodev,allow_other)
20:29
<vagrantc>
allow_other should allow it to read, ok
20:30
so that's probably not it
20:31
<gp>
Does it tell anything that it is only the first time the screen is locked? I rebooted the original client and the lock screen resumes quickly. I also tried a different client.
20:31
I haven't rebooted the server yet
20:31
Let me try that
20:31
to see if it comes back
20:32
<vagrantc>
also check the user's ~/.xsession-errors
20:35
<gp>
It was fast again after server and client reboot
20:37* vagrantc shrugs
20:38
<gp>
Yeah. There are errors in xsession-errors but I don't know that they are related. Seems to be panel widgets that are disabled
20:38
I think since it just appears to be on initial lock screen I can live with it. If i can find something helpful I will bring it up again
20:39
What file did you mention that determines the order of which password backend is checked? remote -> shadow or shadow -> remote?
20:40
I didn't manually set any of the authentication info except which ad groups are sudoers. So it may have been altered without me knowing
20:43
<vagrantc>
i think /etc/nsswitch.conf
20:43
but there may be other places as well
20:58cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 264 seconds)
20:58cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
21:05Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)
21:27
<gp>
vagrantc: Okay so it looks like this: http://dpaste.com/3M6RKN0 Since the client isn't actually joined to the domain and can't use centrifydc, how would I go about removing it for the client?
21:27
I guess it may be looking like ltsp-pnp isn't good for my setup since it copies all of the server files
21:30
But it sure is convenient and I think this is the last issue.
21:35pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, Ping timeout: 265 seconds)
21:38pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme)
21:42
<vagrantc>
alkisg mentioned dropping some files in cleanup.d ... you could make tweaks to the image that way
21:43
should be in /usr/share/ltsp/cleanup.d ... could write a hook to work around that
21:43
gp: also curious if you switched the order on your server
21:44
gp: putting compat before centrifydc
21:44
not sure if it would break other things
22:14
<gp>
vagrantc: I think it might. I want active directory to be the authority. I was thinking about changing it to "centrifydc [NOTFOUND=return]" on the server
22:21
<vagrantc>
gp: the other option, of course, is to configure all the fat clients to be allowed to use centrify...
22:22
gp: but you can write a simple hook to clean out the centrifydc config in the cleanup.d directory
22:22
in theory, it'd be better to not use LDM_PASSWORD_HASH at all and just use centrifydc all over
22:23
LDM_PASSWORD_HASH is an ugly hack to work around lack of LDAP or other centralized authentication
22:51vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
23:02telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
23:04telex has joined IRC (telex!teletype@freeshell.de)
23:20stgraber has left IRC (stgraber!~stgraber@ubuntu/member/stgraber, Read error: Connection reset by peer)
23:25stgraber has joined IRC (stgraber!~stgraber@shell.stgraber.org)
23:26stgraber has left IRC (stgraber!~stgraber@shell.stgraber.org, Changing host)
23:26stgraber has joined IRC (stgraber!~stgraber@ubuntu/member/stgraber)
23:56cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 245 seconds)
23:57cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)