Server Suddenly Started Hunging up
Nicolas Roussi
nroussi at gmail.com
Thu Mar 5 01:28:48 GMT 2009
I have thought about that, so I connected the cable that was going to eth1
of the server that was not working to eth1 of one of my other servers. All
thin clients booted up therefore I can conclude that something blew up in
the motherboard.
Thanks to everyone that tried to help
On Wed, Mar 4, 2009 at 6:18 PM, David Groos <djgroos at gmail.com> wrote:
> I offer this story, quite uncertain of its utility, nonetheless... My thin
> clients were working well last summer, then I replaced the switch with a new
> switch... and could get only 1 or often none of the thin clients to
> boot--couldn't connect to a DHCP server. Several people tried to find the
> problem with the new switch, and it wasn't until a systems engineer looked
> at it that he was able to properly configure it so that during the PXE
> booting, the thin client could get it's IP address. I seem to recall him
> saying it was something about the spanning tree protocol though don't
> remember if that was just one of the things he checked or if that were the
> issue... Good luck :-)
>
> David
>
> On Wed, Mar 4, 2009 at 5:03 PM, Nicolas Roussi <nroussi at gmail.com> wrote:
>
>> I have formatted yet again the server and this time I installed 8.04 i386
>> thinking that this will resolve the issue since I have another on the LAN
>> that works perfectly. After the 3rd client boots up I get the same thing No
>> DHCP or no proxyDHCP offers received. Could it be that the network card or
>> the motherboard blew something?
>>
>> On Tue, Mar 3, 2009 at 9:31 PM, Nicolas Roussi <nroussi at gmail.com> wrote:
>>
>>> I am guessing that it is. I recently configured a bind9 server on the
>>> network which is also the LDAP server but I disabled bind9. These are the
>>> files on the server that is not working. I have included hosts, hostname,
>>> interfaces, dhcpd.conf, ifconfig -a and resolv.conf. I am really puzzled
>>> about this. The help is greatly appreciated.
>>>
>>> nicolas at edubuntuS2:~$ cat /etc/hosts
>>> 127.0.0.1 edubuntuS2 localhost
>>> 127.0.1.1 edubuntuS2.home edubuntuS2
>>>
>>> # The following lines are desirable for IPv6 capable hosts
>>> ::1 ip6-localhost ip6-loopback
>>> fe00::0 ip6-localnet
>>> ff00::0 ip6-mcastprefix
>>> ff02::1 ip6-allnodes
>>> ff02::2 ip6-allrouters
>>> ff02::3 ip6-allhosts
>>>
>>> nicolas at edubuntuS2:~$ cat /etc/hostname
>>> edubuntuS2
>>>
>>> nicolas at edubuntuS2:~$ cat /etc/network/interfaces
>>> # This file describes the network interfaces available on your system
>>> # and how to activate them. For more information, see interfaces(5).
>>>
>>> # The loopback network interface
>>> auto lo
>>> iface lo inet loopback
>>>
>>> # The primary network interface
>>> auto eth0
>>> iface eth0 inet dhcp
>>>
>>> auto eth1
>>> iface eth1 inet static
>>> address 192.168.0.254
>>> netmask 255.255.255.0
>>> network 192.168.0.0
>>> broadcast 192.168.0.255
>>>
>>> nicolas at edubuntuS2:~$ cat /etc/ltsp/dhcpd.conf
>>> #
>>> # Default LTSP dhcpd.conf config file.
>>> #
>>>
>>> authoritative;
>>>
>>> subnet 192.168.0.0 netmask 255.255.255.0 {
>>> range 192.168.0.20 192.168.0.250;
>>> option domain-name "example.com";
>>> option domain-name-servers 192.168.0.1;
>>> option broadcast-address 192.168.0.255;
>>> option routers 192.168.0.1;
>>> # next-server 192.168.0.1;
>>> # get-lease-hostnames true;
>>> option subnet-mask 255.255.255.0;
>>> #option root-path "/opt/ltsp/i386";
>>> option root-path "/opt/ltsp/amd64";
>>> if substring( option vendor-class-identifier, 0, 9 ) =
>>> "PXEClient" {
>>> # filename "/ltsp/i386/pxelinux.0";
>>> filename "/ltsp/amd64/pxelinux.0";
>>> } else {
>>> filename "/ltsp/amd64/nbi.img";
>>> # filename "/ltsp/i386/nbi.img";
>>> }
>>> }
>>>
>>> nicolas at edubuntuS2:~$ ifconfig -a
>>> eth0 Link encap:Ethernet HWaddr 00:1f:c6:1b:4d:f8
>>> inet addr:192.168.2.85 Bcast:192.168.2.255 Mask:255.255.255.0
>>> inet6 addr: fe80::21f:c6ff:fe1b:4df8/64 Scope:Link
>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>> RX packets:343737 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:221723 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:1000
>>> RX bytes:281611267 (268.5 MB) TX bytes:67461581 (64.3 MB)
>>> Base address:0x2000 Memory:d4300000-d4320000
>>>
>>> eth1 Link encap:Ethernet HWaddr 00:1f:c6:1b:4d:f9
>>> inet addr:192.168.0.254 Bcast:192.168.0.255
>>> Mask:255.255.255.0
>>> inet6 addr: fe80::21f:c6ff:fe1b:4df9/64 Scope:Link
>>> UP BROADCAST MULTICAST MTU:1500 Metric:1
>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:1000
>>> RX bytes:0 (0.0 B) TX bytes:4271 (4.1 KB)
>>> Base address:0x2020 Memory:d4320000-d4340000
>>>
>>> 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:29670 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:29670 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:0
>>> RX bytes:1507758 (1.4 MB) TX bytes:1507758 (1.4 MB)
>>> nicolas at edubuntuS2:~$ cat /etc/resolv.conf
>>> nameserver 66.255.85.8
>>> nameserver 66.255.85.9
>>>
>>> Thanks
>>>
>>>
>>> On Tue, Mar 3, 2009 at 6:52 PM, Gavin McCullagh <gmccullagh at gmail.com>wrote:
>>>
>>>> On Tue, 03 Mar 2009, Nicolas Roussi wrote:
>>>>
>>>> > No I am not. Also, on every sudo command it takes forever.
>>>>
>>>> Is your DNS working okay?
>>>>
>>>> Gavin
>>>>
>>>>
>>>
>>>
>>> --
>>> Nicolas Roussi
>>>
>>
>>
>>
>> --
>> Nicolas Roussi
>>
>> --
>> edubuntu-users mailing list
>> edubuntu-users at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
>>
>>
>
--
Nicolas Roussi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/edubuntu-users/attachments/20090304/f844cc51/attachment.htm
More information about the edubuntu-users
mailing list