From owner-freebsd-questions  Thu Jul 31 19:51:16 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA19899
          for questions-outgoing; Thu, 31 Jul 1997 19:51:16 -0700 (PDT)
Received: from gdi.uoregon.edu (cisco-ts7-line1.uoregon.edu [128.223.150.48])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA19888
          for <freebsd-questions@FreeBSD.ORG>; Thu, 31 Jul 1997 19:51:10 -0700 (PDT)
Received: from localhost (dwhite@localhost)
          by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id TAA11189;
          Thu, 31 Jul 1997 19:50:55 -0700 (PDT)
Date: Thu, 31 Jul 1997 19:50:54 -0700 (PDT)
From: Doug White <dwhite@gdi.uoregon.edu>
X-Sender: dwhite@localhost
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Costa Morris <costa@cortx.com>
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: core dumps
In-Reply-To: <3.0.2.32.19970729193510.00967510@cortx.com>
Message-ID: <Pine.BSF.3.96.970731194947.11158E-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 29 Jul 1997, Costa Morris wrote:

> I am having probs with the following:
> >
> pid 2755 (radiusd), uid 0: exited on signal 11 (core dumped)
> pid 2771 (radiusd), uid 0: exited on signal 11 (core dumped)
> pid 2774 (radiusd), uid 0: exited on signal 11 (core dumped)
> arplookup 205.197.61.1 failed: host is not on local network  
> arplookup 205.197.61.1 failed: host is not on local network  
> arplookup 205.197.61.1 failed: host is not on local network  
> arplookup 205.197.61.1 failed: host is not on local network 
> pid 7536 (pine), uid 1013: exited on signal 4 (core dumped)  
> arplookup 205.197.61.1 failed: host is not on local network  
> arplookup 205.197.61.1 failed: host is not on local network  

For the arp lookups, your routing is wrong.  Take a look at 'netstat -rn'
and try to sort it out.  It helps if you disable routed in /etc/sysconfig
(or /etc/rc.conf on 2.2.2).  

For your sig11's and sig4's, these are probably caused by some bad memory
or processor cache.  If you can't compile a kernel with out cc1 sig11ing,
you need to replace your RAM chips.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major
Spam routed to /dev/null by Procmail    | Death to Cyberpromo