FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Edubuntu User

 
 
LinkBack Thread Tools
 
Old 02-15-2012, 07:40 PM
Valerio Pachera
 
Default Fat client fails to authenticate

Hi, I just run ltsp-buil-client and I'm testing a fat client.
The fat client boots without problem but I can't log in.
This is what I get from syslog:

Feb 15 16:53:33 extensys-ProLiant-ML310-G2 dhcpd: DHCPOFFER on
192.168.0.27 to e8:0b:af:8f:13:00 via eth0
Feb 15 16:53:33 extensys-ProLiant-ML310-G2 dhcpd: DHCPREQUEST for
192.168.0.27 (192.168.0.254) from e8:0b:af:8f:13:00 via eth0
Feb 15 16:53:33 extensys-ProLiant-ML310-G2 dhcpd: DHCPACK on
192.168.0.27 to e8:0b:af:8f:13:00 via eth0
Feb 15 16:53:33 extensys-ProLiant-ML310-G2 nbd_server[1189]: connect
from 192.168.0.27, assigned file is /opt/ltsp/images/i386.img
Feb 15 16:53:33 extensys-ProLiant-ML310-G2 nbd_server[1189]: Can't
open authorization file (null) (Bad address).
Feb 15 16:53:33 extensys-ProLiant-ML310-G2 nbd_server[1189]: Authorized client
Feb 15 16:53:33 extensys-ProLiant-ML310-G2 nbd_server[2028]: Starting to serve
Feb 15 16:53:33 extensys-ProLiant-ML310-G2 nbd_server[2028]: Size of
exported file/device is 1200467968
Feb 15 16:53:41 extensys-ProLiant-ML310-G2 ldminfod[2030]: connect
from 192.168.0.27 (192.168.0.27)
Feb 15 16:53:45 extensys-ProLiant-ML310-G2 nbd_server[1189]: connect
from 192.168.0.27, assigned file is /opt/ltsp/images/i386.img
Feb 15 16:53:45 extensys-ProLiant-ML310-G2 nbd_server[1189]: Can't
open authorization file (null) (Bad address).
Feb 15 16:53:45 extensys-ProLiant-ML310-G2 nbd_server[1189]: Authorized client
Feb 15 16:53:45 extensys-ProLiant-ML310-G2 nbd_server[2033]: Starting to serve
Feb 15 16:53:45 extensys-ProLiant-ML310-G2 nbd_server[2033]: Size of
exported file/device is 1200467968
Feb 15 16:53:45 extensys-ProLiant-ML310-G2 nbd_server[2033]:
Disconnect request received.
Feb 15 16:53:45 extensys-ProLiant-ML310-G2 nbd_server[1189]: Child exited with 0
Feb 15 16:54:33 extensys-ProLiant-ML310-G2 ldminfod[2036]: connect
from 192.168.0.27 (192.168.0.27)
Feb 15 16:54:34 extensys-ProLiant-ML310-G2 nbd_server[1189]: connect
from 192.168.0.27, assigned file is /opt/ltsp/images/i386.img
Feb 15 16:54:34 extensys-ProLiant-ML310-G2 nbd_server[1189]: Can't
open authorization file (null) (Bad address).
Feb 15 16:54:34 extensys-ProLiant-ML310-G2 nbd_server[1189]: Authorized client
Feb 15 16:54:34 extensys-ProLiant-ML310-G2 nbd_server[2039]: Starting to serve
Feb 15 16:54:34 extensys-ProLiant-ML310-G2 nbd_server[2039]: Size of
exported file/device is 1200467968
Feb 15 16:54:34 extensys-ProLiant-ML310-G2 nbd_server[2039]:
Disconnect request received.
Feb 15 16:54:34 extensys-ProLiant-ML310-G2 nbd_server[1189]: Child exited with 0
Feb 15 16:55:33 extensys-ProLiant-ML310-G2 ldminfod[2051]: connect
from 192.168.0.27 (192.168.0.27)
Feb 15 16:55:33 extensys-ProLiant-ML310-G2 nbd_server[1189]: connect
from 192.168.0.27, assigned file is /opt/ltsp/images/i386.img
Feb 15 16:55:33 extensys-ProLiant-ML310-G2 nbd_server[1189]: Can't
open authorization file (null) (Bad address).
Feb 15 16:55:33 extensys-ProLiant-ML310-G2 nbd_server[1189]: Authorized client
Feb 15 16:55:33 extensys-ProLiant-ML310-G2 nbd_server[2054]: Starting to serve
Feb 15 16:55:33 extensys-ProLiant-ML310-G2 nbd_server[2054]: Size of
exported file/device is 1200467968
Feb 15 16:55:34 extensys-ProLiant-ML310-G2 nbd_server[2054]:
Disconnect request received.
Feb 15 16:55:34 extensys-ProLiant-ML310-G2 nbd_server[1189]: Child exited with 0

As suggested in the guide I enabled ndb compression removing
NO_COMP="-noF -noD -noI -no-exports"
before running ltsp-build-client.

What is wrong?
Which other information may I report?

Thank you.

--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
 
Old 02-21-2012, 01:40 PM
Valerio Pachera
 
Default Fat client fails to authenticate

2012/2/15 Valerio Pachera <sirio81@gmail.com>:
> Hi, I just run ltsp-buil-client and I'm testing a fat client.
> The fat client boots without problem but I can't log in.

I run
ltsp-update-sshkey
ltsp-update-image

I also wanted to use nfs instead of sshfs so, before creating the
image, I made sure nfs-common was installed in the chroot.
Then I followd the instruction on the wiki (fat client) to setup the
nfs-kernel-server (on the server).
And I was able to log in.

--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
 

Thread Tools




All times are GMT. The time now is 08:05 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org