On Thu, 8 Mar 2012 14:35:35 +0000 (UTC), Camaleón wrote in message <jjag3n$ek5$4...@dough.gmane.org>:
> On Thu, 08 Mar 2012 00:07:23 +0100, benoit lair wrote: > > > 2012/3/7 benoit lair <kurushi7...@gmail.com>: > >> 2012/3/7 Camaleón <noela...@gmail.com>: > >>> On Tue, 06 Mar 2012 23:33:00 +0100, benoit lair wrote: > >>> > >>>> I didn't specify it, but i've tried: > >>>> > >>>> ping onto an external host > >>>> ping onto the gateway of this server > >>> > >>> And what was the output/results? > > >> No response in all cases. > > Mmm, okay. Neither for the loopback interface? > > ping -c 3 127.0.0.1 ..try ping -nc 3 <ip adress> if the above "hangs" on dns, see man ping for details. > > >>>> The messages into mail.info says there's a problem with MX > >>>> resolution because of the network loss. > >>> > >>> So you can't resolve domain names. > > >> I wasn't behind my server when it loss connection. No way to > >> contact him from my office, so went fast to my datacenter to > >> regain access (ok no remote control pdu on this machine and not > >> virtualised (1 of 3 old school survivors on my network), so hard > >> access to this hardware when problem) So when arrived in my box, > >> face to my server, wired my kvm screen and so no way to get any > >> network from my server. > > Understood. > > >>>> Also, when i tried to ping an IP, i got no response, so it > >>>> doesn't seem there's a problem around dns system. > >>> > >>> Which pings fails, remote or local (or both)? > > >> So both > > That sounds serious. > > (...) > > >>>> It's quite surprising, seen nothing on the logs. > >>> > >>> Nothing? Is the module loaded? "lsmod | grep bnx2" > > >> Now i looked onto my incidents tickets, already got this problem 10 > >> months ago. But it was unsolved by my collegues. grrh, now it's too > >> late to get response less than waiting horribly for a potential > >> new bug > > What was the incident about? > > >> Keeping the logs away from log rotate, will have to read and > >> prepare cups of cofee for this week end > > :-) > > > Yep! An idea! > > > > I didn't take a look onto my ossec logs, perhaps will i find > > something. > > > > Thanks for the tip of modprobe Camaleon. > > > > I'll be back, when i got news. > > Okay, we'll wait for your findings. > > Having the networking service up, running and configured but no > response to pings (neither from local nor remote hosts) it sounds to > me like some sort of problem with either the hardware facilities > (cables, switches, ethernet card) or at the software side, the kernel > module for the adapter. > > Greetings, > -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120401190938.27d63...@nb6.lan
