beacon still dies at 1.0
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.
FWIW, here's the error I had on my Mac this morning:
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,
so i installed the 1.0-0 version on 10 solaris boxes (our monitoring
buoys) yesterday and this morning, and I can't keep them up. some of
them seem to have more problems than others, I've had to restart some
of them more than once, and some not yet at all.
if anyone has any ideas
<http://dclmr-buoy.gw.uiuc.edu/beacon/central_loss.html> for my
server and other info (this is our on-campus/eventually-multi-campus
monitoring, hence our own page & group). there should be 5 "good"
and 5 "blind" beacons. they're all pretty much the same:
100 hab-buoy> uname -a
SunOS hab-buoy 5.8 Generic_108528-15 sun4u sparc SUNW,UltraAX-i2
I can't find anything in anything that's syslogging.
--
-debbie
Debbie Fligor, n9dn Network Engineer, CITES, Univ. of Il
email: fligor@uiuc.edu <http://www.uiuc.edu/ph/www/fligor>
"Every keystroke can be monitored. And the computers never forget."