[gentoo-user] broken ping reply after 30secs

[gentoo-user] broken ping reply after 30secs

[Enrico Weigelt]

Hi folks,


I've got an very strange situation w/ one of my gento servers:
Ping reply (within lan) takes very long (about 30secs) and is 
broken, services are not responding.

I never got such slow ping replies, even of heavily busy 
machines. 

Does anyone know such an situation and maybe how to solve it ?


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] broken ping reply after 30secs

[Mick]

[-- Attachment #1: Type: text/plain, Size: 470 bytes --]

On Friday 29 December 2006 16:22, Enrico Weigelt wrote:
> Hi folks,
>
>
> I've got an very strange situation w/ one of my gento servers:
> Ping reply (within lan) takes very long (about 30secs) and is
> broken, services are not responding.
>
> I never got such slow ping replies, even of heavily busy
> machines.
>
> Does anyone know such an situation and maybe how to solve it ?

Have you ruled out faulty cables & RJ45 connectors?

-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] broken ping reply after 30secs

[Леонид Моргун]

Maybe problems with hardware? I mean routers, switches, etc...

В сообщении от Пятница 29 декабря 2006 19:22 Enrico Weigelt написал(a):
> Hi folks,
>
>
> I've got an very strange situation w/ one of my gento servers:
> Ping reply (within lan) takes very long (about 30secs) and is
> broken, services are not responding.
>
> I never got such slow ping replies, even of heavily busy
> machines.
>
> Does anyone know such an situation and maybe how to solve it ?
>
>
> cu
> --
> ---------------------------------------------------------------------
>  Enrico Weigelt    ==   metux IT service - http://www.metux.de/
> ---------------------------------------------------------------------
>  Please visit the OpenSource QM Taskforce:
>  	http://wiki.metux.de/public/OpenSource_QM_Taskforce
>  Patches / Fixes for a lot dozens of packages in dozens of versions:
> 	http://patches.metux.de/
> ---------------------------------------------------------------------

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] broken ping reply after 30secs

[Enrico Weigelt]

* Mick <michaelkintzios@gmail.com> wrote:

> Have you ruled out faulty cables & RJ45 connectors?

Yes. This was my first suspect.

It suddenly disappeared after putting down and reconfiguring
the eth interface (diretly w/ ifconfig). Then I remembered 
I've put an "ifconfig eth0 up" into crontab, since it
sometimes disappeared. Now I've replaced it with a little
script which puts the interface down and reconfigures/
brings it up again.

Smells like a bug ...

cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] broken ping reply after 30secs

[Hans-Werner Hilse]

Hi,

On Sun, 31 Dec 2006 03:52:30 +0100
Enrico Weigelt <weigelt@metux.de> wrote:

> It suddenly disappeared after putting down and reconfiguring
> the eth interface (diretly w/ ifconfig). Then I remembered 
> I've put an "ifconfig eth0 up" into crontab, since it
> sometimes disappeared. Now I've replaced it with a little
> script which puts the interface down and reconfigures/
> brings it up again.
> 
> Smells like a bug ...

Smells like a driver/interrupt routing problem. Did you try
conservative kernel configuration, i.e. disabling MSI and/or APIC
(kernel command line "nomsi", "noapic", "nolapic")?

-hwh

-- 
gentoo-user@gentoo.org mailing list