|02:08||metal-machine has left IRC (email@example.com, Quit: Leaving)|
|03:33||fiesh has left IRC (fiesh!~fiesh@p508AE68B.dip0.t-ipconnect.de, Ping timeout: 246 seconds)|
|03:35||fiesh has joined IRC (fiesh!~fiesh@p508AE6DD.dip0.t-ipconnect.de)|
|04:13||metal-machine has joined IRC (firstname.lastname@example.org)|
alkisq: I am not able to login thin clients. I am using NFS. here is the output for "grep -r ^Exec /usr/share/xsessions"
Is it problem with NFS configuration?
|05:56||metal-machine has left IRC (email@example.com, Ping timeout: 244 seconds)|
|05:57||adrianorg has left IRC (firstname.lastname@example.org, Ping timeout: 255 seconds)|
|05:59||adrianorg has joined IRC (email@example.com)|
|06:35||metal-machine has joined IRC (firstname.lastname@example.org)|
hello still not able to login from thin-client
any one there?
metal-machine: run this on the server: tail -f /var/log/auth.log
|06:52||work_alkisg is now known as alkisg|
Then try to login on the thin client, and check the server again to see if you got a successful login message
no i am not getting successful login, the error is something like
pam_unix(su:auth): auth could not identify password for [root]
FAILED su for root by test1
- /dev/pts/2 test1:root
[now again tried to boot thin client and new message appears ]
root-server sshd Connection closed by 192.168.0.201 [preauth]
Ok that means the problem is with openssh?
|07:11||metal-machine has left IRC (email@example.com, Quit: Leaving)|
|07:11||metal-machine has joined IRC (firstname.lastname@example.org)|
metal-machine: are you trying to login as root?
metal-machine: it might be an issue with your ssh keys
ltsp-update-sshkeys: If you changed your server IP, you need to run ltsp-update-sshkeys, and if you're using NBD (Ubuntu) you also need ltsp-update-image afterwards
you can also try this:
screen_08: To get a root shell on a Debian thin client, put SCREEN_07=ldm, SCREEN_08=shell and SCREEN_DEFAULT=07 to lts.conf.
I am using Debian wheezy with NFS
So try those 2 sentences, but don't try the ubuntu part
first I run this on root server: ltsp-update-sshkeys 192.168.0.106 debian-app-01
the both of above run without errors
|07:22||ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)|
Then you need LDM_SERVER=ip
The default name for the LTSP server is "server", so the client ssh doesn't know and doesn't trust server when you've only put its ip and dns in the keys
Either name .106 as "server" in your /etc/hosts, and run ltsp-update-sshkeys with "server", or change LDM_SERVER
ok I am trying with first
ok trying to boot thin client
One more thing I want to confirm . I am creating users in .106.
is that fine or I have to make only in root server(.105)?
The root server is only serving NFS, right?
If so, you don't need users there, unless you're using nfs4 with authentication etc
Root server is serving boot image. I am sending you the setup
No need, try the ssh keys, it's probably that
I used that. Please have a look. I did the same as in setup
I feel I am missing some nfs setup part
Did you get a shell at screen08?
When you get a local root shell on a client, try those:
1) alt+ctrl+f8 to switch to the console
2) getltscfg -a, check the value of SERVER there, or LDM_SERVER
3) ssh user@<exact ip or name of server>
4) It will probably prompt you to trust the ssh keys, which is what is going wrong with your setup
Accept the keys
5) Switch again to vt7, alt+ctrl+f7. Now you should be able to log in
aah ok Now i got you. :)
I.e. I think that the problem is that the client doesn't trust the server because you're mixing IPs, DNS names, the LTSP special "server" name, your MY_SERVER_LIST, etc
If the above 5 steps allow you to log in, you'll be certain that I was "right"...
|07:55||gbaman has joined IRC (email@example.com)|
|08:02||metal-machine has left IRC (firstname.lastname@example.org, Ping timeout: 256 seconds)|
|08:11||gbaman has left IRC (email@example.com, Remote host closed the connection)|
|08:12||gbaman has joined IRC (firstname.lastname@example.org)|
|08:28||fiesh has left IRC (fiesh!~fiesh@p508AE6DD.dip0.t-ipconnect.de, Ping timeout: 245 seconds)|
|08:35||gbaman has left IRC (email@example.com, Remote host closed the connection)|
|08:39||vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)|
|08:52||freedomrun has joined IRC (freedomrun!~quassel@BSN-182-152-186.dynamic.siol.net)|
|08:52||freedomrun has joined IRC (freedomrun!~quassel@unaffiliated/freedomrun)|
|08:55||freedomrun has left IRC (freedomrun!~quassel@unaffiliated/freedomrun, Remote host closed the connection)|
|09:17||telex has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|09:18||telex has joined IRC (email@example.com)|
|09:33||alkisg is now known as work_alkisg|
|09:56||Heinz2k has joined IRC (Heinz2k!54bd75f8@gateway/web/freenode/ip.188.8.131.52)|
Hi for testing purpose im running LTSP on 14.04 Ubuntu LTSP serving a fat client chroot via NBD. That works without problem. However for some reasons i want to switch back to NFS, i have installed all necessary packages and NFS Server works, however my client cant boot the chroot if the export is ro ( permission issues) exporting chroot as rw works well, but thats not what i want. Is there something special i have to change to make n
Yes, it is possibly by mounting an overlayfs on top of NFS, that's what LTSP does for NBD as well. Heinz2k, explain your reason for wanting to switch to NFS.
LTSP is just running on a tiny vm , due to IO Perfomance i want the thin clients to load the chroot from a NFS Share of our local SAN (much better IO Perfomance) ...
Sounds like a plan.
NFS should be mounted read-only. If it's mounted read-write, clients will get in eachother's way.
But the OS needs a read-write root to start from. Solution is the same with NBD (as that is also read-only): LTSP mounts an overlay FS (basically, a ramdisk) on top of the root, where all changes are stored.
If the client reboots, all those changes are gone again.
so it seems my setup lack overlayfs support
Heinz2k, you can check this by typing "mount"
Typically, you should see the root nbd/nfs mount
And then another root, with overlayfs (or aufs, not sure which LTSP uses)
Let me boot a thin client to show you
I just sent you a PM here on IRC, with a screenshot of 'mount' output on a virtual thin client
Note /dev/nbd0 mounted ro and overlayfs mounted rw
LTSP should do this automatically though, for NBD -and- NFS.
with NBD : overlayfs on / type overlayfs (rw)
seems to work
client boots fine
NFS Fails on bootup : /sbin/init-ltsp/ ........ Permission denied
Permission denied doesn't necessarily mean something is read-only.
In this case, I bet it means your NFS permissions aren't set up correctly.
You said you were using a NAS... does this NAS preserve Linux file permissions?
Just testing with local VMs right now (1 Server VM 1 Client VM)
h1@ubuntu:/etc$ sudo exportfs /home <world> /opt/ltsp/amd64 <world>
tcp 0 0 *:nfs *:* LISTEN root 11876 -
Yes, now mount the directory from the SAN.
Cant .. not at work ;)
So you're not actually trying to mount NFS from the SAN?
But from the local server?
NFS Server is on the local machine
sorry i meant on the LTSP VM
quiet-splash: to disable the splash screen in Ubuntu, in order to see any boot error messages, run sudo gedit /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default and remove quiet splash plymouth:force-splash vt.handoff=7
Forgot all about that, it's been a while since I debugged LTSP. :P
You might see some useful error messages when you do that.
|11:57||khildin has joined IRC (firstname.lastname@example.org)|
send you the corresponding error messages
thank you for ur help so far
gotta take care of my child now :) ... but will be online later
I've only once or twice used LTSP with NFS backend, to me, it looks like something is going wrong with overlayfs still...
But the problem could be in your lts.conf as well... I'm not sure.
|13:16||AlexPortable has joined IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-nugmlyzrmsjuhjjm)|
|13:45||Heinz2k has left IRC (Heinz2k!54bd75f8@gateway/web/freenode/ip.184.108.40.206, Quit: Page closed)|
|14:57||Heinz2k has joined IRC (Heinz2k!54bd75f8@gateway/web/freenode/ip.220.127.116.11)|
|16:21||AlexPortable has left IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-nugmlyzrmsjuhjjm, Quit: Connection closed for inactivity)|
|16:33||vmlintu has joined IRC (email@example.com)|
|17:20||vmlintu has left IRC (firstname.lastname@example.org, Ping timeout: 256 seconds)|
|17:24||telex has left IRC (email@example.com, Remote host closed the connection)|
|17:26||telex has joined IRC (firstname.lastname@example.org)|
|17:34||vmlintu has joined IRC (email@example.com)|
|17:41||alkisg_web has joined IRC (alkisg_web!d510e116@gateway/web/freenode/ip.18.104.22.168)|
|17:48||alkisg_web has left IRC (alkisg_web!d510e116@gateway/web/freenode/ip.22.214.171.124, Quit: Page closed)|
|18:13||Heinz2k has left IRC (Heinz2k!54bd75f8@gateway/web/freenode/ip.126.96.36.199, Quit: Page closed)|
|19:21||alkisg_web has joined IRC (alkisg_web!d510e116@gateway/web/freenode/ip.188.8.131.52)|
|20:12||syrius has left IRC (firstname.lastname@example.org, Ping timeout: 255 seconds)|
|20:24||syrius has joined IRC (email@example.com)|
|20:31||syrius has left IRC (firstname.lastname@example.org, Ping timeout: 250 seconds)|
|20:37||syrius has joined IRC (email@example.com)|
|20:52||AlexPortable has joined IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-ynrklyvgjwrxmrsg)|
4k: Imagine a 4k display updated at 60 fps. It needs 3840×2160×32×60 bits per second, i.e. 16 gbps. Normal HD displays need 4 gbps. Thin clients will have much trouble getting all that through the local network...
|21:43||vmlintu has left IRC (firstname.lastname@example.org, Ping timeout: 245 seconds)|
|21:45||fiesh has joined IRC (email@example.com)|
|21:54||alkisg_web has left IRC (alkisg_web!d510e116@gateway/web/freenode/ip.184.108.40.206, Quit: Page closed)|
|22:07||ricotz has left IRC (ricotz!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)|
|22:53||khildin has left IRC (firstname.lastname@example.org, Quit: I'm gone, bye bye)|