Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 24 Jan 2010 08:36:06 +0530
From:      Sherin George <list@sheringeorge.co.cc>
To:        freebsd-hackers@freebsd.org
Subject:   Re: Strange network issue in freebsd 8
Message-ID:  <7f14551c1001231906w17e2372av75e3d8e1e84c6ae4@mail.gmail.com>
In-Reply-To: <alpine.BSF.2.00.1001240045550.79980@fledge.watson.org>
References:  <7f14551c1001230119r65464667t6d6b604118101419@mail.gmail.com> <alpine.BSF.2.00.1001240045550.79980@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hello Robert,

Thanks for the advice.

I have upgrade OS to FreeBSD 8.0-RELEASE-p2.

I have also requested the help of freebsd-net.

--
Regards,
Sherin

On Sun, Jan 24, 2010 at 6:18 AM, Robert Watson <rwatson@freebsd.org> wrote:

>
> On Sat, 23 Jan 2010, Sherin George wrote:
>
>  i am facing some sort of strange network issue in a freebsd server
>> occasionally.
>>
>> OS: FreeBSD 8.0-RELEASE - amd64
>>
>> The servers loses network connection once in a few days. I logged into
>> console and verified that network is up. I even restarted network service
>> using following command.
>>
>
> I'd suggest sending this e-mail to freebsd-net; there have been significant
> link layer changes in 8.0, and it's possible this is a side effect (and bug)
> from that.  The appropriate people will pick it up on that list.
>
> Also, I notice you're running 8.0-RELEASE, rather than the latest patch
> level (which included some important security impovements and stability
> improvements); you may want to slide forward using freebsd-update or a
> manual rebuild.  You will need to reboot to pick up some of the
> improvements.
>
> Robert N M Watson
> Computer Laboratory
> University of Cambridge
>
>
>> /etc/rc.d/netif restart
>>
>> Still, it didn't fix.
>>
>> I checked /var/log/messages, but I am not getting any clue.
>>
>> ==============
>> Jan 19 12:10:20 myserver kernel: GEOM_MIRROR: Device gm0: rebuilding
>> provider ad0 finished.
>> Jan 19 20:20:23 myserver nfsd[732]: select failed: Interrupted system call
>> Jan 19 20:21:07 myserver nfsd[732]: select failed: Interrupted system call
>> Jan 23 02:14:33 myserver login: ROOT LOGIN (root) ON ttyv0
>> Jan 23 02:19:51 myserver kernel: ifa_del_loopback_route: deletion failed
>> Jan 23 02:19:57 myserver kernel: em0: link state changed to DOWN
>> Jan 23 02:20:02 myserver kernel: em0: link state changed to UP
>> Jan 23 02:29:58 myserver reboot: rebooted by root
>> Jan 23 02:29:58 myserver syslogd: exiting on signal 15
>> Jan 23 02:31:31 myserver syslogd: kernel boot file is /boot/kernel/kernel
>> Jan 23 02:31:31 myserver kernel: Copyright (c) 1992-2009 The FreeBSD
>> Project.
>> Jan 23 02:31:31 myserver kernel: Copyright (c) 1979, 1980, 1983, 1986,
>> 1988,
>> 1989, 1991, 1992, 1993, 1994
>> Jan 23 02:31:31 myserver kernel: The Regents of the University of
>> California. All rights reserved.
>> Jan 23 02:31:31 myserver kernel: FreeBSD is a registered trademark of The
>> FreeBSD Foundation.
>> Jan 23 02:31:31 myserver kernel: FreeBSD 8.0-RELEASE #0: Sat Nov 21
>> 15:02:08
>> UTC 2009
>> Jan 23 02:31:31 myserver kernel: root@mason.cse.buffalo.edu:
>> /usr/obj/usr/src/sys/GENERIC
>> Jan 23 02:31:31 myserver kernel: Timecounter "i8254" frequency 1193182 Hz
>> quality 0
>> ==============
>>
>> Network, TCP stack all were up. It was pinging gateway even. But,
>> traceroute
>> was not going beyond gateway.
>>
>> I believe the issue is not related to anything outside server since a
>> reboot
>> always fixes the issue.
>>
>> I will be grateful for any advise that can help me in troubleshooting this
>> problem.
>>
>> --
>> Best Regards,
>> Sherin
>> _______________________________________________
>> freebsd-hackers@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org
>> "
>>
>>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7f14551c1001231906w17e2372av75e3d8e1e84c6ae4>