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


Channel log from 22 May 2016   (all times are UTC)

00:15vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
01:37gdi2k has left IRC (gdi2k!~gdi2k@49.151.17.102, Quit: Ex-Chat)
02:37XoMeLLyoX has joined IRC (XoMeLLyoX!605507d9@gateway/web/freenode/ip.96.85.7.217)
02:38
<XoMeLLyoX>
I just installed ltsp-server on Debian 8 according to the instructions on the wiki. I have double checked everything but my client still doesn't boot. Can someone help me with this?
02:52
This does pop up on the client's screen and I would suspect this may be part of the issue: module overlayfs not found in modules.dep
02:56
<vagrantc>
the overlayfs warning shouldn't be an issue
02:57
XoMeLLyoX: which exact instructions did you follow?
02:57
<XoMeLLyoX>
https://wiki.debian.org/LTSP/Howto
02:58
Are there different ones I should follow? I've installed on CentOS in the past without issue. I've heard Debian isn't as straight forward though.
02:58
<vagrantc>
Debian actually has an active maintainer for LTSP, at least
02:59
but, i'm a little biased :)
02:59
XoMeLLyoX: so, what happens when you boot a client? any logs in the server's /var/log/syslog?
03:00
<XoMeLLyoX>
It obtains an IP and that's the last I see it in the logs.. And on the client it just goes to a black screen
03:01
<vagrantc>
so you turn on the computer and it just goes to a black screen, nothing scrolling by as it boots?
03:02
<XoMeLLyoX>
No, I see the warning about overlayfs then black screen. And my monitor goes to sleep
03:02
<vagrantc>
does the black screen have any readable text on it?
03:03
<XoMeLLyoX>
Nothing at all
03:03
<vagrantc>
is the computer still running?
03:03
<XoMeLLyoX>
I can ping the client just fine
03:03
Yes
03:03
<vagrantc>
if you press ctrl-alt-f1 on the client, do you see a login screen?
03:04
<XoMeLLyoX>
Nope
03:04
<vagrantc>
!shell
03:04
<ltsp`>
I do not know about 'shell', but I do know about these similar topics: 'shell-screen', 'gnome-shell'
03:04
<vagrantc>
!shell-screen | echo XoMeLLyoX
03:04
<ltsp`>
XoMeLLyoX shell-screen: One way to get local root access to troubleshoot a thin client is to use a shell SCREEN: https://help.ubuntu.com/community/UbuntuLTSP/ClientTroubleshooting#Using%20a%20shell%20SCREEN
03:05
<XoMeLLyoX>
Okay so this could be a x11 issue?
03:05
<vagrantc>
that's what I'm thinking
03:05
don't have much to go on
03:06
XoMeLLyoX: in fact, if you edit lts.conf to just have two lines "[default]" and "SCREEN_02=shell" and then reboot, does it give you a shell prompt?
03:07
<XoMeLLyoX>
Yeah Debian is a tad different than what I'm used to. We've been running CentOS for years which I'm more familiar with. But it's obviously not supported so we've moved to Debian.
03:07
No, I just tried it and nothing
03:08
Should I have a default xorg.conf under /opt/ltsp/i386/etc/X11?
03:10
<vagrantc>
shouldn't need an xorg.conf ... with that in lts.conf, it shouldn't even try to load X
03:11
what's your client hardware?
03:12
<XoMeLLyoX>
It's a 10zig. I know the hardware works b/c we have a similar set up working in the office. It PXE boots the image just fine
03:13
<vagrantc>
works running a debian live cd?
03:13
or, you mean, this same hardware boots a debian ltsp-pnp setup somewhere else?
03:14
<XoMeLLyoX>
ltsp-pnp? Is that needed? I did not install that on this machine.
03:14
<vagrantc>
if you're seeing the overlayfs message, it means the console video is working at some point ... but something is later breaking it.
03:14
<XoMeLLyoX>
Yes the same hardware runs ltsp somewhere else
03:14
<vagrantc>
XoMeLLyoX: using the same setup, or some other verison of LTSP, other OS, etc?
03:14
<XoMeLLyoX>
I'm setting up a test system at my house to work through some issues for our set up at the office
03:14
Same setup
03:15
But I do believe my sysadmin switched the image to an older image to tftpboot because he couldn't get the newer one to work for some reason
03:15
<vagrantc>
honestly out of ideas at this point
03:16
XoMeLLyoX: so when you say same setup, you mean different setup? :P
03:16
<XoMeLLyoX>
I can ssh into the client
03:16
haha Sorry I should be more elaborate
03:17
<vagrantc>
ok, if you can ssh in you can at least look at some logs from the client itself
03:17
dmesg
03:17
check /var/log/syslog
03:17
and /var/log/Xorg.*.log
03:18
ctrl-alt-f1 should really show a console login prompt, or SCREEN_02=shell should pop up a shell ... but somehow your video is crashing part-way through bootup ... haven't seen that before.
03:19
if it were a KMS (kernel mode setting) issue, i'd expect it to not display video at all
03:19
or distorted, or something like that
03:20
any idea what video hardware is in it?
03:21
10zig reveals lots of different hardware
03:21
<XoMeLLyoX>
I'm really not sure. I'd have to look it up at the office
03:22
Well I just thought I could ssh into the client. Root password isn't working
03:31
<vagrantc>
passwords are usually disabled on the client images
03:31
<gehidore>
is the root password not working or is root login disabled via ssh by default...
03:31
s/via/in/
03:32
<vagrantc>
password root logins are also usually disabled by default in debian's ssh
03:33
i *think*
03:33
been so long since i used any system that actually had a root password set
03:33
<XoMeLLyoX>
Yes you are correct.. I enabled it though
03:35
<vagrantc>
XoMeLLyoX: you could specify ltsp.break= on e of the scripts from /usr/share/ltsp/init-ltsp.d
03:35
that should kick in before the video gets mangled ...
03:36
<XoMeLLyoX>
Oh wait a sec. I'm an idiot. I forgot to restart the ssh daemon after making the change
03:36
Okay I just ssh'd into the client. Now let me try looking at the logs
03:36
<vagrantc>
restart the ssh daemon where?
03:36
and how?
03:36
<XoMeLLyoX>
In the chroot environment
03:36
<vagrantc>
if you can't log in?
03:36
i thought you were doing ltsp-pnp?
03:36
there is no chroot there
03:36
<XoMeLLyoX>
No I am not. I didn't even know about ltsp-pnp
03:37
Is there documentation out there on that?
03:37
<vagrantc>
oh, i don't know where i got that idea
03:37
XoMeLLyoX: the wiki howto you linked mentions it a little later
03:41
<XoMeLLyoX>
Weirdest thing.. I don't see anything weird in the logs on the client either.
03:43
<vagrantc>
try a different monitor?
03:44
it's amazing, after 10+ years of developing LTSP, people still manage to find weird issues i've never heard of before
03:45
<XoMeLLyoX>
I am going to try it.. But I swear if that's the fix I'm going to kick myself.
03:46
I do have it hooked through a KVM switch. But I've set it up this way before without an issue.
03:46
So I'm going to plug it directly in and if that doesn't work then change monitors
03:46
<vagrantc>
oh, KVMs sometimes mess with detection of the correct settings
03:46
i have seen that before!
03:53
<XoMeLLyoX>
Well that seem to have worked..
03:53
Although the login screen is off the monitor at least it's a log in screen!
03:53
<vagrantc>
even after a reboot?
03:54
<XoMeLLyoX>
Yes. I had to reboot it to get it to come up at all after hooking the monitor in directly
03:55
I believe this is part of the issue my sysadmin had and that's why he used a different image than the newest one.
03:55
He never could get the resolution correct on the monitor
03:56
<vagrantc>
you could try XRANDR_DISABLE=True and then X_MODE_0=XxY (e.g. 1024x768)
03:56
if you know what the valid resolution should be
03:57
XoMeLLyoX: well, sorry it took so long, but at least figured something out! :)
03:57* vagrantc waves
03:57vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
04:10
<XoMeLLyoX>
Thank you for your help!
05:54ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:53kjackal has joined IRC (kjackal!~quassel@2a02:587:3117:9e00:e113:dadf:2c9a:ae4)
11:43Phantomas has joined IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
12:05
<highvoltage>
vsuojanen, alkisg: LTSP live on Edubuntu works well
12:12GodFather has left IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com, Remote host closed the connection)
12:15GodFather has joined IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com)
12:25GodFather has left IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com, Ping timeout: 246 seconds)
12:42GodFather has joined IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com)
12:50GodFather has left IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com, Ping timeout: 246 seconds)
13:00GodFather has joined IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com)
13:16Phantomas has left IRC (Phantomas!~ftsamis@ubuntu/member/phantomas, Ping timeout: 250 seconds)
13:16Phantomas has joined IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
13:27GodFather has left IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com, Ping timeout: 260 seconds)
13:37GodFather has joined IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com)
13:47GodFather has left IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com, Ping timeout: 252 seconds)
13:52GodFather has joined IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com)
15:59vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
16:19Phantomas has left IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
16:27kjackal has left IRC (kjackal!~quassel@2a02:587:3117:9e00:e113:dadf:2c9a:ae4, Ping timeout: 260 seconds)
16:56robb_nl has joined IRC (robb_nl!~robb_nl@62.235.97.203)
17:03robb_nl has left IRC (robb_nl!~robb_nl@62.235.97.203, Ping timeout: 244 seconds)
17:26ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Remote host closed the connection)
17:26ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
18:04kjackal has joined IRC (kjackal!~quassel@2a02:587:3117:9e00:e113:dadf:2c9a:ae4)
18:12kjackal has left IRC (kjackal!~quassel@2a02:587:3117:9e00:e113:dadf:2c9a:ae4, Ping timeout: 260 seconds)
18:52robb_nl has joined IRC (robb_nl!~robb_nl@62.235.97.203)
20:04kjackal has joined IRC (kjackal!~quassel@2a02:587:3117:9e00:e113:dadf:2c9a:ae4)
20:15robb_nl has left IRC (robb_nl!~robb_nl@62.235.97.203, Quit: I'm gone, bye bye)
20:28GodFather has left IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com, Remote host closed the connection)
20:29GodFather has joined IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com)
20:34Freejack has left IRC (Freejack!~Freejack@unaffiliated/freejack, Ping timeout: 246 seconds)
20:44Freejack has joined IRC (Freejack!~Freejack@unaffiliated/freejack)
21:00
<sbalneav>
vagrantc: http://pastebin.com/RCnWySZ9
21:00
pam_external + that script = 80% of what pam_sshauth currently does.
21:06GodFather has left IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com, Remote host closed the connection)
21:08
<vagrantc>
sbalneav: nice!
21:09
<sbalneav>
So, this leads me to ask the question:
21:10
What I'd like, is someone from the debian security team who knows about pam to have a look at the pam_external module, and the nss_external module, and make suggestions.
21:11
If the idea is completely daft, then we can just drop it.
21:11
But if someone else thinks the idea is sound, and we're on to something here, it's *clearly* easier doing this via the scripting language than it is via C.
21:12
<vagrantc>
right
21:12
<sbalneav>
And therefore, I'd suggest we use pam_external + <some script>, and we could just mark pam_sshauth as depricated.
21:12
<vagrantc>
i'll see if i can dig up some folks willing to do a review of the concept and code.
21:12
<sbalneav>
That would be awesome.
21:12
I'll work in the next couple of days on documentation.
21:13
I think the code is "reasonably
21:13
" complete
21:14
<vagrantc>
sbalneav: would you be able to email me a brief email about it so i don't loose track?
21:14
<sbalneav>
Will do, I'll do it on tues when I get the doco done
21:15
<vagrantc>
sbalneav: i'm really excited to see you busy working on this! :)
21:15* vagrantc hasn't been able to do much more than maintenance for ltsp5
21:16
<sbalneav>
Well, it's been a long, slow process getting all the bits I wanted in place
21:16
Mate desktop, webkit-greeter, pam modules....
21:17
And much of the work was outside the direct LTSP sphere.
21:17
But mow... I think we're within striking distance.
21:17
*now
21:18
And when you and Alkis are in SA, I can make myself available nights to help with remote work.
21:18
I can E-Attend :D
21:21
<vagrantc>
sbalneav: let's hope that works out, and maybe plan for something in the coming year for us to all attend? :)
21:30ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)
22:41GodFather has joined IRC (GodFather!~rcc@96-35-101-212.dhcp.bycy.mi.charter.com)