You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Randy Terbush <ra...@zyzzyva.com> on 1997/07/15 03:53:59 UTC

Re: spammage (fwd)

I've seen some similar problems coming from free() on FreeBSD when 
doing a graceful restart. Complains of attempt to free() bad 
address.


> Damnit.  I always thought this was a user configuration problem... we've
> had this reported a few times in the past against linux, solaris, and
> something else I think.  But today it happened on my machine ... running
> 1.3 as of a week ago. 
> 
> Dean
> 
> ---------- Forwarded message ----------
> Date: Mon, 14 Jul 1997 14:08:12 -0700
> To: dgaudet@arctic.org
> Subject: spammage
> 
> the httpd freaked out today and filled the disk with:
> 
> [Mon Jul 14 13:56:42 1997] select: (listen): Bad address
> [Mon Jul 14 13:56:42 1997] select: (listen): Bad address
> [Mon Jul 14 13:56:42 1997] select: (listen): Bad address
> 
> hundreds of megs of it.
> 
> i shut down the httpd, grepped this out, replaced the log with the results, 
> and restarted the httpd. hope that was all to your liking.



Re: spammage (fwd)

Posted by Dean Gaudet <dg...@arctic.org>.
Hmm, not sure.  twinlark's webserver isn't ever automatically restarted,
so it was sort of a spontaneous event for me. 

Dean

On Tue, 15 Jul 1997, Ben Laurie wrote:

> Randy Terbush wrote:
> 
> > I've seen some similar problems coming from free() on FreeBSD when
> > doing a graceful restart. Complains of attempt to free() bad
> > address.
> 
> The two symptoms together would suggest that the listener copies are
> being prematurely freed. I'd look into it myself if I weren't busy with
> NT stuff.
> 
> Cheers,
> 
> Ben.
> 
> --
> Ben Laurie [Normal service will be resumed as soon as possible]
> 
> 
> 


Re: spammage (fwd)

Posted by Ben Laurie <be...@algroup.co.uk>.
Randy Terbush wrote:

> I've seen some similar problems coming from free() on FreeBSD when
> doing a graceful restart. Complains of attempt to free() bad
> address.

The two symptoms together would suggest that the listener copies are
being prematurely freed. I'd look into it myself if I weren't busy with
NT stuff.

Cheers,

Ben.

--
Ben Laurie [Normal service will be resumed as soon as possible]