|00:15||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|01:37||gdi2k has left IRC (firstname.lastname@example.org, Quit: Ex-Chat)|
|02:37||XoMeLLyoX has joined IRC (XoMeLLyoX!605507d9@gateway/web/freenode/ip.184.108.40.206)|
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?
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
the overlayfs warning shouldn't be an issue
XoMeLLyoX: which exact instructions did you follow?
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.
Debian actually has an active maintainer for LTSP, at least
but, i'm a little biased :)
XoMeLLyoX: so, what happens when you boot a client? any logs in the server's /var/log/syslog?
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
so you turn on the computer and it just goes to a black screen, nothing scrolling by as it boots?
No, I see the warning about overlayfs then black screen. And my monitor goes to sleep
does the black screen have any readable text on it?
Nothing at all
is the computer still running?
I can ping the client just fine
if you press ctrl-alt-f1 on the client, do you see a login screen?
I do not know about 'shell', but I do know about these similar topics: 'shell-screen', 'gnome-shell'
!shell-screen | echo XoMeLLyoX
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
Okay so this could be a x11 issue?
that's what I'm thinking
don't have much to go on
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?
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.
No, I just tried it and nothing
Should I have a default xorg.conf under /opt/ltsp/i386/etc/X11?
shouldn't need an xorg.conf ... with that in lts.conf, it shouldn't even try to load X
what's your client hardware?
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
works running a debian live cd?
or, you mean, this same hardware boots a debian ltsp-pnp setup somewhere else?
ltsp-pnp? Is that needed? I did not install that on this machine.
if you're seeing the overlayfs message, it means the console video is working at some point ... but something is later breaking it.
Yes the same hardware runs ltsp somewhere else
XoMeLLyoX: using the same setup, or some other verison of LTSP, other OS, etc?
I'm setting up a test system at my house to work through some issues for our set up at the office
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
honestly out of ideas at this point
XoMeLLyoX: so when you say same setup, you mean different setup? :P
I can ssh into the client
haha Sorry I should be more elaborate
ok, if you can ssh in you can at least look at some logs from the client itself
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.
if it were a KMS (kernel mode setting) issue, i'd expect it to not display video at all
or distorted, or something like that
any idea what video hardware is in it?
10zig reveals lots of different hardware
I'm really not sure. I'd have to look it up at the office
Well I just thought I could ssh into the client. Root password isn't working
passwords are usually disabled on the client images
is the root password not working or is root login disabled via ssh by default...
password root logins are also usually disabled by default in debian's ssh
been so long since i used any system that actually had a root password set
Yes you are correct.. I enabled it though
XoMeLLyoX: you could specify ltsp.break= on e of the scripts from /usr/share/ltsp/init-ltsp.d
that should kick in before the video gets mangled ...
Oh wait a sec. I'm an idiot. I forgot to restart the ssh daemon after making the change
Okay I just ssh'd into the client. Now let me try looking at the logs
restart the ssh daemon where?
In the chroot environment
if you can't log in?
i thought you were doing ltsp-pnp?
there is no chroot there
No I am not. I didn't even know about ltsp-pnp
Is there documentation out there on that?
oh, i don't know where i got that idea
XoMeLLyoX: the wiki howto you linked mentions it a little later
Weirdest thing.. I don't see anything weird in the logs on the client either.
try a different monitor?
it's amazing, after 10+ years of developing LTSP, people still manage to find weird issues i've never heard of before
I am going to try it.. But I swear if that's the fix I'm going to kick myself.
I do have it hooked through a KVM switch. But I've set it up this way before without an issue.
So I'm going to plug it directly in and if that doesn't work then change monitors
oh, KVMs sometimes mess with detection of the correct settings
i have seen that before!
Well that seem to have worked..
Although the login screen is off the monitor at least it's a log in screen!
even after a reboot?
Yes. I had to reboot it to get it to come up at all after hooking the monitor in directly
I believe this is part of the issue my sysadmin had and that's why he used a different image than the newest one.
He never could get the resolution correct on the monitor
you could try XRANDR_DISABLE=True and then X_MODE_0=XxY (e.g. 1024x768)
if you know what the valid resolution should be
XoMeLLyoX: well, sorry it took so long, but at least figured something out! :)
|03:57||* vagrantc waves|
|03:57||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)|
Thank you for your help!
|05:54||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|07:53||kjackal has joined IRC (kjackal!~quassel@2a02:587:3117:9e00:e113:dadf:2c9a:ae4)|
|11:43||Phantomas has joined IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)|
vsuojanen, alkisg: LTSP live on Edubuntu works well
|12:12||GodFather has left IRC (GodFatheremail@example.com, Remote host closed the connection)|
|12:15||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|12:25||GodFather has left IRC (GodFatheremail@example.com, Ping timeout: 246 seconds)|
|12:42||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|12:50||GodFather has left IRC (GodFatheremail@example.com, Ping timeout: 246 seconds)|
|13:00||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|13:16||Phantomas has left IRC (Phantomas!~ftsamis@ubuntu/member/phantomas, Ping timeout: 250 seconds)|
|13:16||Phantomas has joined IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)|
|13:27||GodFather has left IRC (GodFatheremail@example.com, Ping timeout: 260 seconds)|
|13:37||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|13:47||GodFather has left IRC (GodFatheremail@example.com, Ping timeout: 252 seconds)|
|13:52||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|15:59||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|16:19||Phantomas has left IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)|
|16:27||kjackal has left IRC (kjackal!~quassel@2a02:587:3117:9e00:e113:dadf:2c9a:ae4, Ping timeout: 260 seconds)|
|16:56||robb_nl has joined IRC (email@example.com)|
|17:03||robb_nl has left IRC (firstname.lastname@example.org, Ping timeout: 244 seconds)|
|17:26||ogra_ has left IRC (email@example.com, Remote host closed the connection)|
|17:26||ogra_ has joined IRC (firstname.lastname@example.org)|
|18:04||kjackal has joined IRC (kjackal!~quassel@2a02:587:3117:9e00:e113:dadf:2c9a:ae4)|
|18:12||kjackal has left IRC (kjackal!~quassel@2a02:587:3117:9e00:e113:dadf:2c9a:ae4, Ping timeout: 260 seconds)|
|18:52||robb_nl has joined IRC (email@example.com)|
|20:04||kjackal has joined IRC (kjackal!~quassel@2a02:587:3117:9e00:e113:dadf:2c9a:ae4)|
|20:15||robb_nl has left IRC (firstname.lastname@example.org, Quit: I'm gone, bye bye)|
|20:28||GodFather has left IRC (GodFatheremail@example.com, Remote host closed the connection)|
|20:29||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|20:34||Freejack has left IRC (Freejack!~Freejack@unaffiliated/freejack, Ping timeout: 246 seconds)|
|20:44||Freejack has joined IRC (Freejack!~Freejack@unaffiliated/freejack)|
pam_external + that script = 80% of what pam_sshauth currently does.
|21:06||GodFather has left IRC (GodFatheremail@example.com, Remote host closed the connection)|
So, this leads me to ask the question:
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.
If the idea is completely daft, then we can just drop it.
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.
And therefore, I'd suggest we use pam_external + <some script>, and we could just mark pam_sshauth as depricated.
i'll see if i can dig up some folks willing to do a review of the concept and code.
That would be awesome.
I'll work in the next couple of days on documentation.
I think the code is "reasonably
sbalneav: would you be able to email me a brief email about it so i don't loose track?
Will do, I'll do it on tues when I get the doco done
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|
Well, it's been a long, slow process getting all the bits I wanted in place
Mate desktop, webkit-greeter, pam modules....
And much of the work was outside the direct LTSP sphere.
But mow... I think we're within striking distance.
And when you and Alkis are in SA, I can make myself available nights to help with remote work.
I can E-Attend :D
sbalneav: let's hope that works out, and maybe plan for something in the coming year for us to all attend? :)
|21:30||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)|
|22:41||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|