Re: beacon still dies at 1.0
On Wed, 25 Aug 2004 14:11:33 -0500
debbie fligor <fligor@uiuc.edu> wrote:
> well, I updated my mac beacons to 1.0-0 and it's still exiting, but
> since no one else is reporting problems, I thought it was only a Mac
> thing.
Debbie,
I believe this is the same issue I was seeing as well. You could
put your startup script in a loop or work in the patch I used on
the previous RC release:
<http://archive.ncsa.uiuc.edu/lists/beacon/jul04/msg00044.html>
I've just installed and started the latest beacon and I haven't seen
the problem yet (though I expect to). What I'll probably do is tie
a tcpdump capture to the central server on the TCP connections and see
if I can spot anything that way. If you can catch one before I do I
can help you analyze the capture file if need be.
> 350 faranth> Use of uninitialized value in scalar chop at ./beacon line 1876.
> Use of uninitialized value in concatenation (.) or string at ./beacon
> line 1897.
> HOST_LOOKUP delete failed 0x2910cce4, UNKN,
I was seeing those previously as well.
John