From owner-freebsd-questions  Wed Feb  4 22:36:17 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA16462
          for questions-outgoing; Wed, 4 Feb 1998 22:36:17 -0800 (PST)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA16420
          for <freebsd-questions@FreeBSD.ORG>; Wed, 4 Feb 1998 22:36:09 -0800 (PST)
          (envelope-from dwhite@gdi.uoregon.edu)
Received: from localhost (dwhite@localhost)
          by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id WAA17103;
          Wed, 4 Feb 1998 22:36:03 -0800 (PST)
          (envelope-from dwhite@gdi.uoregon.edu)
Date: Wed, 4 Feb 1998 22:36:03 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: "Daniel R.  Brownstone" <drbrowns@ls.wustl.edu>
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: pointer problems, 2.2.5
In-Reply-To: <Pine.BSF.3.96.980204202406.5498B-100000@ls.wustl.edu>
Message-ID: <Pine.BSF.3.96.980204223430.16875T-100000@gdi.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe questions"

On Wed, 4 Feb 1998, Daniel R.  Brownstone wrote:

> 
> I apologize if I should have caught this either in a FAQ or in the
> handbook.  We recently upgraded our system from 2.2 to 2.2.5-STABLE, and
> shortly thereafter we seem to be getting this error.  Rebooting seems to
> solve the problem for a few days, then it myseteriously comes back.  We
> get this message when we telnet in, or when we try to ftp.  (The ftp will
> not work, as a result.  The telnet will.)  Any suggestions:
> 
> The error is:
> 
> inetd in realloc(): warning: junk pointer, too low to make sense. 

This happens to a fraction of the users and unfortunately I don't know a
solution offhand.  

The last suggestion was to check `netstat -m' and see how many mbuf
clusters are in use and the max value.  If the max is within 3/4 of the
total maxiumum (default 255?) then you need to increase the number by
compiling your kernel with `options NMBCLUSTERS=XXXX'. 

Something is running out of memory or is leaking memory.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major