Re: beacon 0.9.58 dies after a while - broken pipe?

To: beacon@dast.nlanr.net
Subject: Re: beacon 0.9.58 dies after a while - broken pipe?
From: "Charles R. Anderson" <cra@WPI.EDU>
Date: Sun, 25 Jul 2004 15:59:47 -0400
Content-disposition: inline
Content-type: text/plain; charset=us-ascii
In-reply-to: <3.0.5.32.20040724173456.015b8270@pop.ncsa.uiuc.edu>
Mail-followup-to: beacon@dast.nlanr.net
References: <Pine.GSO.4.58.0407221342490.5094@icarus.cc.uic.edu> <3.0.5.32.20040724173456.015b8270@pop.ncsa.uiuc.edu>
Reply-to: beacon@dast.nlanr.net
Sender: owner-beacon@dast.nlanr.net
User-agent: Mutt/1.4.1i

On Sat, Jul 24, 2004 at 05:34:56PM -0500, Mitch Kutzko wrote:
> At 02:51 PM 7/22/2004 -0500, you wrote:
> > I'm running a fresh install of beacon version 0.9.58 and after running it
> > for a while (not sure exactly how long) it seems to give up. This has
>
> Hi -- Has anybody else seen this behavior?  Is it reproducible?  Any details?

I'm seeing it on 2 of my 4 beacon server systems.  Each server is
running 3 copies of the beacon on three different group/port sets. 
The local 239.x.x.x beacon on one server died at some time, and I
restarted it last night.  It has died again since then.  I have also
just noticed that the global beacon.ncsa.uiuc.edu beacon on another
server ag-venueserv.WPI.EDU died, but the other two are still running
(local and regional).

References:
- beacon 0.9.58 dies after a while - broken pipe?
  - From: Gideon Goldman
- Re: beacon 0.9.58 dies after a while - broken pipe?
  - From: Mitch Kutzko

Prev by Date: Re: multiple packets from client with decreasing TTL
Next by Date: Re: beacon 0.9.58 dies after a while - broken pipe?
Previous by thread: Re: beacon 0.9.58 dies after a while - broken pipe?
Next by thread: Re: beacon 0.9.58 dies after a while - broken pipe?

Other Mailing lists | Author Index | Date Index | Subject Index | Thread Index