Date: Mon, 8 Jun 1998 08:40:02 -0700 (PDT) From: jher <jher@io.com> To: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense. Message-ID: <199806081540.IAA11039@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR kern/6858; it has been noted by GNATS.
From: jher <jher@io.com>
To: Greg Lehey <grog@lemis.com>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense.
Date: Mon, 8 Jun 1998 10:31:44 -0500
Sure, that fixes inetd, but that doesn't make my cronjobs work. Thats the
main problem.
On Fri, Jun 05, 1998 at 09:46:57AM +0930, Greg Lehey wrote:
> This symptom seems much more common than this message would suggest.
> I've seen it in cases where the system has run out of swap, but that
> doesn't seem to be a requirement. The "fix" is rather heavy-handed.
> I've always been able to restart inetd and keep it quiet for some
> time.
>
> Greg
>
> On Thu, 4 June 1998 at 10:18:42 -0700, jher@io.com wrote:
> >
> >> Number: 6858
> >> Category: kern
> >> Synopsis: inetd in realloc(): warning: junk pointer, too low to make sense.
> >> Confidential: no
> >> Severity: serious
> >> Priority: high
> >> Responsible: freebsd-bugs
> >> State: open
> >> Quarter:
> >> Keywords:
> >> Date-Required:
> >> Class: sw-bug
> >> Submitter-Id: current-users
> >> Arrival-Date: Thu Jun 4 10:20:01 PDT 1998
> >> Last-Modified:
> >> Originator: jher
> >> Organization:
> > Illuminati Online
> >> Release: 3.0-980518-SNAP
> >> Environment:
> > FreeBSD solomon.io.com 3.0-980518-SNAP FreeBSD 3.0-980518-SNAP #0: Tue Jun 2 19:22:49 CDT 1998 jher@solomon.io.com:/usr/src/sys/compile/SOLOMON i386
> >
> >> Description:
> > I boot the machine, run my innd server o it and after its 12am expire
> > run, the machine starts screwing up. The expire run is very memory
> > intensive and usually eats about 200megs of ram. As soon as it starts,
> > sshd can no longer malloc correctly and tries to malloc 1+gig of memory
> > whenever I ssh into the machine. I therefore resort to telnetting in and
> > get the message:
> > inetd in realloc(): warning: junk pointer, too low to make sense.
> > but it lets me login. From that point forward, the cronjobs cease to
> > run correctly. Basically they startup and exit immediately. If I send
> > a HUP to sshd's pid, it returns to normal and I can ssh in. Of course,
> > since cron no longer functions correctly, news is failing to get expired
> > etc. If I reboot, it usually corrects the problem until the cronjob
> > for news runs at midnight.
> > I'm on a P-II 266Mhz, with 256M SDram, 2940UW scsi (2 controllers), SMC
> > 10/100 Etherpower, and an LX-6 Motherboard.
> >
> > I'm running an SMP version of the same release on a Dual PPro 200Mhz
> > machine with DPT and 2904UW, and SMC 10/100 without having the same
> > problem. The kernel has esentially the same compile options. This
> > machine is also running innd and its nightly news.daily (expire) run
> > has a larger amount of data to work with and so far its been flawless.
> > Oh and the Mainboard is an ASUS board.
> >> How-To-Repeat:
> > wait for the news.daily run to happen from the 12am crontab
> >> Fix:
> > reboot
> >> Audit-Trail:
> >> Unformatted:
>
> --
> See complete headers for address and phone numbers
> finger grog@lemis.com for PGP public key
>
--
jher@io.com Senior Systems Engineer jher@fnord.org Pope
http://www.fnord.org
Today is Prickle-Prickle, day 13 in the season of Confusion, 3164.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806081540.IAA11039>