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


Channel log from 19 February 2015   (all times are UTC)

00:01
<ternarybit>
Interesting
00:13telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
00:14telex has joined IRC (telex!teletype@freeshell.de)
00:28ternarybit has left IRC (ternarybit!~ternarybi@205.155.216.7, Quit: HydraIRC -> http://www.hydrairc.com <- Would you like to know more?)
01:41dedwards has joined IRC (dedwards!6c0cbf6a@gateway/web/freenode/ip.108.12.191.106)
01:41
<dedwards>
hello
01:42dedwards has left IRC (dedwards!6c0cbf6a@gateway/web/freenode/ip.108.12.191.106, Client Quit)
01:43dedwards has joined IRC (dedwards!6c0cbf6a@gateway/web/freenode/ip.108.12.191.106)
01:43
<dedwards>
is this where I get help for ltsp?
01:47
I guess I'll get right to it. I'm having a problem with getting a black screen on the thinclient everytime I set LDM_AUTOLOGIN = True in the lts.conf file
01:54
<vagrantc>
try with LDM_GUESTLOGIN instead
01:54
dedwards: chances are there's some misconfiguration with the username/password defaults
01:55
dedwards: also, what distro/version/ltsp version you using? "ltsp-info" pasted to a pastebin might help
01:58
<dedwards>
http://pastebin.com/a0g16fCe
01:59
I'm not sure what you mean by misconfiguration with the username/password defaults. here's lts.conf if it may help:
02:00
http://pastebin.com/tHSVGSkJ
02:04
<vagrantc>
autologin/guestlogin both default to the username and password of the client "hostname"... typically something like "ltsp123"
02:06
dedwards: does "ssh tsuser@server" work with that password?
02:06
dedwards: basically, try logging in with that username/password without autologin ... does that work?
02:09
<dedwards>
so I need to enable LDM_GUESTLOGIN first?
02:09
<vagrantc>
well, disable LDM_AUTOLOGIN
02:09
and just manually enter the username/password at login
02:10
<dedwards>
but I don't know the thinclient hostname.
02:10
<vagrantc>
well, you've specified LDM_USERNAME and LDM_PASSWORD in your lts.conf
02:10
so you're not using the default
02:10
does that username and password combination work?
02:11
<dedwards>
I haven't tried yet. I will now though
02:11
<vagrantc>
much easier to debug non-autologin
02:14
<dedwards>
hold on updating image
02:15
<vagrantc>
no need to update image when changing lts.conf ...
02:15
if you edit it in the tftp dir, anyways...
02:22
<dedwards>
the username and password are not working. I did add it in the chroot environment though. The Admin password I added in the chroot works though
02:32
<vagrantc>
you add the users to the server
02:32
typically, anyways
02:33
effectively, LDM is just a GUI frontend for "ssh -X user@server"
02:46
<dedwards>
this is what I did:
02:47
sudo chroot /opt/ltsp/i386
02:47gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Remote host closed the connection)
02:48
<dedwards>
mount -t proc proc /proc
02:48
useradd -m tsuser -G sudo
02:48
useradd -m adminusername -G sudo
02:49
then I updated the image. My understanding was that by doing that I would be actually adding the accounts to the thinclient image. Is that not the case?
02:49
ignore the line from 21:49
02:50
that says useradd -m adminusername -G sudo
02:52
<vagrantc>
accounts do not need to be added to the thinclient image
02:52
you add accounts on the server.
02:53
at least with a typical configuration. you can of course do whatever you want. :)
02:53
but maybe start with the default behavior before running off into the weeds. :)
02:58gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
03:03
<dedwards>
I stand corrected. Okay so i put the admin account on autologin and it worked. Now, I just want to launch rdesktop on login and when I add the following:
03:04
http://pastebin.com/EWmVpuFn
03:04
I get the black screen again lol
03:04
<vagrantc>
eeyk. i wouldn't put the admin password info in a file fetched over tftp...
03:04
<dedwards>
that wasn't the actual pass
03:05
<vagrantc>
LDM_AUTOLOGIN doesn't do RDP ...
03:05
<dedwards>
so how do I do that then?
03:08
<vagrantc>
oh wait, you want to lauch rdesktop from a logged in session? why not just use the "xfreerdp" screen script instead?
03:08
or do you want to RDP session to automatically log in too?
03:09
i think that would default to logging into your LTSP server with RDP ... is RDP running on your LTSP server, or do you want to connect to some other machine?
03:11
<dedwards>
I would like to thinclient to start and automatically launch rdesktop to our terminal server but prompt the user for a domain username/password
03:11
our windows terminal server
03:12
<vagrantc>
so you have to tell it which server to connect to
03:13
<dedwards>
correct which I thought I did that with the RDP_SERVER = line
03:13
<vagrantc>
ah, you've called it ts01
03:14
try with the ip address of ts01
03:14
the clients are on the same network as your server?
03:14
<dedwards>
well that's the name of the terminal server
03:14
yes they are
03:14
<vagrantc>
try with the ip address, it may have name resolution issues
03:14
<dedwards>
let me try that
03:15
<vagrantc>
no need to rebuild the image...
03:18
<dedwards>
yep. That's so nice. Every guide I read it said to rebuild the image and it took so long. Anyways, using the IP address seems to work fine. However I really need to use the hostname
03:30
<vagrantc>
do you have multiple servers you'll be using?
03:32
dedwards: you can put in lts.conf: HOSTS_00=1.2.3.4 ts01
03:33
that should allow you to specify RDP_SERVER=ts01
03:33
(where 1.2.3.4 is the ip address of ts01)
03:41
<dedwards>
okay I was just looking at the ip config of the client and I saw a DNS server of 127.0.0.1
03:42
I would rather have DNS working since this is a load balanced terminal server farm and DNS plays a large role in the load balancing
03:42
<vagrantc>
oh yeah, you could also specify DNS_SERVER=1.2.3.4
03:43
there were some bugs in the DNS_SERVER code; not sure if the version of ubuntu you're running has them fixed or not
03:43
<dedwards>
could the problem be on the DHCP server? I'm using DHCP proxy on the ltsp server which I'm not really clear how that part works. I guess it looks for an available dhcp server on the network and forwards the requests to it? if that's the case then it should be giving ot the correct DNS servers
03:45
can I add multiple DNS_SERVER entries i guess?
03:46
<vagrantc>
i think it supports multiple dns servers
03:47
dedwards: ideally we'd get those values from DHCP, but because of how it boots, it doesn't get that information
03:47
<dedwards>
got ya
03:48
<vagrantc>
the client makes a DHCP request before the root filesystem is mounted, and we don't cache the values from the initramfs into the rootfs.
03:48
although it actually wouldn't be terribly difficult, we do do that for some values, i think...
03:48
definitely worth filing a bug report about it
03:50
<dedwards>
I just put one DNS_SERVER entry and I changed to the hostname and now the black screen again
03:58alkisg_android has joined IRC (alkisg_android!~yaaic@46-242-88.adsl.cyta.gr)
03:59gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
04:00
<alkisg_android>
gbaman, have you tried rpi2?
04:05
<vagrantc>
dedwards: hrm. need to do more troubleshooting ... set SCREEN_02=shell and SCREEN_07=xfreerdp (or rdesktop
04:05
a little lost on all of it
04:06gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Ping timeout: 240 seconds)
04:06
<vagrantc>
alkisg_android: the big plus is it's armv7, so could support debian/ubuntu... but still routes all the hardware through a single USB connection
04:07
dedwards: i've only ever used RDP to help troubleshoot...
04:07
<alkisg_android>
Do you think it would make a decent fat client?
04:08* alkisg_android is thinking of deploying an rpi2 pc lab in a school...
04:08
<vagrantc>
alkisg_android: it might ... should get my hands on one to test...
04:08
<alkisg_android>
errr computer lab not pc
04:08
<vagrantc>
can't beat the price
04:13
<dedwards>
still not working. I soon as I put that hostname in there it's not working. Let me paste my lts.conf file again, maybe I mistyped something?
04:15
<vagrantc>
switch to tty2 to view the debug shell
04:15
ctrl-alt-f2
04:15
<dedwards>
http://pastebin.com/fK6bTj2b
04:17
<vagrantc>
well, .local addresses are usually resolved by libnss-mdns, not by a dns server
04:18
well, usual is an unusual phrase
04:18
<dedwards>
not familiar with libnss-mdns. do i need to install that package?
04:19
thanks for sticking with this. Its kicking my ass
04:19
<vagrantc>
sudo ltsp-chroot apt-get intall libnss-mdns ; sudo ltsp-update-image
04:19
before doing that
04:20
<alkisg_android>
isn't Dnsserver comma-based?
04:20
<vagrantc>
i'd check that your server resolves your .local addresses
04:20
host ts01.xxx.local 1.2.3.4
04:20
<alkisg_android>
not that it matters for .local, ok
04:22
<vagrantc>
well, they may have configured their DNS servers to resolve .local
04:23
<alkisg_android>
yup thought so but unlikely and cant type much :)
04:23* alkisg_android waves
04:23alkisg_android has left IRC (alkisg_android!~yaaic@46-242-88.adsl.cyta.gr)
04:26
<dedwards>
the dns server can definitely resolve .local addresses. The actual AD domain is .local.
04:26
updating the image
04:27
<vagrantc>
then installing libnss-mdns won't do anything
04:28
libnss-mdns resolves hosts using avahi/zeroconf
04:28
not typical dns servers
04:28
which is why i asked to run the host command to see if it resolves
04:29
as i know that doesn't check libnss-mdns
04:30
<dedwards>
okay did you happen to see a type or anything? maybe i need to enclose the tsfarm.xxx.local in quotes?
04:30
I mean a typo
04:31
<vagrantc>
nothing obvious, though i suspect it's not actually got xxx in the name
04:31
<dedwards>
no it doesn't. That's just me trying not to reveal too much info
04:33
nothing of interest as far as I can tell in /var/log/syslog
04:33
<vagrantc>
i can only check for some many obvious mistakes when i have to guess what's actually there
04:33
dedwards: cat /etc/resolv.conf
04:33
does it show your dns servers?
04:34* vagrantc notes that obscuring dns ip addresses from a local namespace that are advertised over DHCP only makes troubleshooting harder and doesn't provide any real protection
04:35
<vagrantc>
from a local ip address range
04:36
<dedwards>
it is showing the DNS servers and from a console prompt I can resolve the tsfarm.xxx.local successfully
04:38
<vagrantc>
from which console prompt?
04:39
<dedwards>
here's the real file:
04:39
http://pastebin.com/nc0SVDHR
04:39
TTY2
04:40
the client's
04:41
<vagrantc>
so, the ip address works, the client can resolve the hostname, but using the hostname doesn't work?
04:51
<dedwards>
that's correct. I wonder if this is related to the terminal services session broker for the terminal server farm
04:51
maybe rdesktop doesn't support it?
05:03gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
05:07gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Ping timeout: 250 seconds)
05:19
<dedwards>
well thanks anyways. I appreciate the help. I will work on it some more tomorrow. I appreciate the help
05:23dedwards has left IRC (dedwards!6c0cbf6a@gateway/web/freenode/ip.108.12.191.106, Ping timeout: 246 seconds)
06:13work_alkisg is now known as alkisg
06:30eemeli has joined IRC (eemeli!3e94cd0c@gateway/web/freenode/ip.62.148.205.12)
06:58alkisg is now known as work_alkisg
07:05gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
07:10gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Ping timeout: 245 seconds)
08:07gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
08:12gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Ping timeout: 265 seconds)
08:51adrianorg has left IRC (adrianorg!~adrianorg@186.213.152.128, Ping timeout: 252 seconds)
08:53adrianorg has joined IRC (adrianorg!~adrianorg@186.213.152.128)
08:56work_alkisg is now known as alkisg
09:04telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
09:04telex has joined IRC (telex!teletype@freeshell.de)
09:05camaraadmin has joined IRC (camaraadmin!298bd0f6@gateway/web/freenode/ip.41.139.208.246)
09:09gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
09:15gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Ping timeout: 246 seconds)
09:25vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
09:32Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
10:33alkisg is now known as work_alkisg
10:34Fenuks has joined IRC (Fenuks!~Fenuks@gate.ifmieo.nspu.ru)
10:37eemeli has left IRC (eemeli!3e94cd0c@gateway/web/freenode/ip.62.148.205.12, Quit: Page closed)
10:42gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
10:50gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Remote host closed the connection)
10:52gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
10:52gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Remote host closed the connection)
11:06ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)
11:30eemeli has joined IRC (eemeli!3e94cd0b@gateway/web/freenode/ip.62.148.205.11)
11:37Fenuks has left IRC (Fenuks!~Fenuks@gate.ifmieo.nspu.ru, Ping timeout: 246 seconds)
12:35Faith has joined IRC (Faith!~paty@unaffiliated/faith)
12:43adrianorg has left IRC (adrianorg!~adrianorg@186.213.152.128, Ping timeout: 246 seconds)
12:44adrianorg has joined IRC (adrianorg!~adrianorg@186.213.152.128)
12:47eemeli has left IRC (eemeli!3e94cd0b@gateway/web/freenode/ip.62.148.205.11, Ping timeout: 246 seconds)
12:59gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
13:05gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
13:31gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Remote host closed the connection)
14:14Fenuks has joined IRC (Fenuks!~Fenuks@212.164.143.65)
14:15Fenuks has joined IRC (Fenuks!~Fenuks@212.164.143.65)
15:07work_alkisg is now known as alkisg
15:59telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
16:00telex has joined IRC (telex!teletype@freeshell.de)
16:01gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
16:05adrianorg has left IRC (adrianorg!~adrianorg@186.213.152.128, Ping timeout: 264 seconds)
16:06adrianorg has joined IRC (adrianorg!~adrianorg@186.213.152.128)
16:07alkisg is now known as work_alkisg
16:29Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Quit: I Leave)
16:59imox has joined IRC (imox!~imox@p4FC5C6F2.dip0.t-ipconnect.de)
17:18imox has left IRC (imox!~imox@p4FC5C6F2.dip0.t-ipconnect.de, Quit: imox)
17:32khildin has joined IRC (khildin!~khildin@ip-83-134-135-105.dsl.scarlet.be)
17:42vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
18:01Fenuks has left IRC (Fenuks!~Fenuks@212.164.143.65, Ping timeout: 245 seconds)
18:53gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
19:09khildin has left IRC (khildin!~khildin@ip-83-134-135-105.dsl.scarlet.be, Ping timeout: 245 seconds)
19:35shogunx has left IRC (shogunx!~shogunx@rrcs-67-79-182-229.se.biz.rr.com, Ping timeout: 252 seconds)
19:36shogunx has joined IRC (shogunx!~shogunx@rrcs-67-79-182-229.se.biz.rr.com)
19:56khildin has joined IRC (khildin!~khildin@ip-83-134-135-105.dsl.scarlet.be)
20:00shogunx has left IRC (shogunx!~shogunx@rrcs-67-79-182-229.se.biz.rr.com, Ping timeout: 250 seconds)
20:00shogunx has joined IRC (shogunx!~shogunx@rrcs-67-79-182-229.se.biz.rr.com)
20:38vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
21:18gbaman has left IRC (gbaman!~gbaman@31.205.104.150, Remote host closed the connection)
21:27ricotz has left IRC (ricotz!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)
21:29telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
21:30telex has joined IRC (telex!teletype@freeshell.de)
21:48gbaman has joined IRC (gbaman!~gbaman@31.205.104.150)
23:27Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)