En/na SZABO Zsolt ha escrit:
> On Wed, 31 Oct 2007, Alexandre Magaz Graça wrote:
> 
>> Oct 31 12:56:27 ltsp-prova sshd[5029]: Server listening on :: port 22.
>> Oct 31 12:56:27 ltsp-prova sshd[5029]: error: Bind to port 22 on 0.0.0.0
>> failed: Address already in use.
> 
> How does your dhcpd.conf look?

The DHCP server is in another machine (192.168.0.1). This is its dhcpd.conf

ddns-update-style interim;
ignore client-updates;
authoritative;

default-lease-time 10800;
max-lease-time 21600;

subnet 192.168.0.0 netmask 255.255.255.0 {
...
}

host ltsp1 {
        hardware ethernet               00:16:e6:52:a8:d0;
        fixed-address                   192.168.0.40;
        option subnet-mask              255.255.255.0;
        option broadcast-address        192.168.0.255;
        option routers                  192.168.0.4;
        option domain-name-servers      192.168.0.4;
        option domain-name              "udl.net";
        get-lease-hostnames             true;
        next-server                     192.168.0.4;
        option root-path                "/opt/ltsp/i386";
        option tftp-server-name         "192.168.0.4";
        filename                        "ltsp/i386/pxelinux.0";
}


> What does hostname say? And ifconfig?

On the server:
hostname -> ltsp-prova
[EMAIL PROTECTED]: ~> ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:36:8E:0F:9E
           inet addr:192.168.0.4  Bcast:192.168.0.255  Mask:255.255.255.0
           inet6 addr: fe80::216:36ff:fe8e:f9e/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:255313 errors:0 dropped:0 overruns:0 frame:0
           TX packets:233319 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:26439634 (25.2 MB)  TX bytes:551951025 (526.3 MB)
           Interrupt:16 Base address:0xe000

eth1      Link encap:Ethernet  HWaddr 00:16:36:8E:0F:9C
           inet addr:10.100.14.92  Bcast:10.255.255.255  Mask:255.0.0.0
           inet6 addr: fe80::216:36ff:fe8e:f9c/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:224185 errors:0 dropped:0 overruns:0 frame:0
           TX packets:54920 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:23458722 (22.3 MB)  TX bytes:23111233 (22.0 MB)
           Interrupt:20

lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           inet6 addr: ::1/128 Scope:Host
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:126353 errors:0 dropped:0 overruns:0 frame:0
           TX packets:126353 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:304567820 (290.4 MB)  TX bytes:304567820 (290.4 MB)

On the client:
hostname -> ltsp (it should be ltsp1, I don't know where this ltsp is 
from ¿?)

[EMAIL PROTECTED]:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:E6:52:A8:D0
           inet addr:192.168.0.40  Bcast:192.168.0.255  Mask:255.255.255.0
           inet6 addr: fe80::216:e6ff:fe52:a8d0/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:17831 errors:0 dropped:0 overruns:0 frame:0
           TX packets:10923 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:25674342 (24.4 MB)  TX bytes:792251 (773.6 KB)
           Interrupt:17

lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           inet6 addr: ::1/128 Scope:Host
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


>> I rebuild the thin client chroot with ltsp-build-client and added a new
>> user to ensure all was clean, but keeps failing. I've modified the thin
>> client initrd to include the sky2 module (BTW, why are so few network
>> modules included in initrd?), but I suppose this shouldn't affect ssh
>> authentication (˙˙?)
>>
>> Someone knows what is happening with this?
> 
> Or probably it is about ltsp-update-sshkeys, etc. ?

I already run it, but nothing changes.

I will check all one more time hoping to find something...

Cheers,
Àlex

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to