A funny thing happened on the way to the RC...............
So, I updated my server to the RC version today. Saved all of my configuration files, and (based on info from this list!), decided to add fping to my system this time. Fping installed, no problem.
Fired up BB. Then, everyone's pager went NUTS. 100 pages, times 4 pagers. WHOOOOPS. The entire world had uh..... "lost connectivity."
What had really happened of course is, that the hobbit userid couldn't run fping, since I had forgotten to suid the executable. And yes, I did eventually find it in a log file, but... But, this had the very nasty side effect of turning each and every connectivity icon RED. And then the alerts kicked in..... And four Duracell batteries died.
I don't know how easy it is to implement, but I have a suggestion worth looking into?
If fping "doesn't work" (as opposed to, "cannot ping a host"), the result status should be CLEAR, not RED. "test not functional" or "test disabled" or something.
Just a thought!!!!
:-)
Kent C. Brodie - brodie at phys.mcw.edu
Department of Physiology
Medical College of Wisconsin
(414) 456-8590
On Thu, Jul 13, 2006 at 04:48:08PM -0500, Brodie, Kent wrote:
Fired up BB. Then, everyone's pager went NUTS. 100 pages, times 4 pagers. WHOOOOPS. The entire world had uh..... "lost connectivity."
What had really happened of course is, that the hobbit userid couldn't run fping, since I had forgotten to suid the executable. And yes, I did eventually find it in a log file, but... But, this had the very nasty side effect of turning each and every connectivity icon RED. And then the alerts kicked in..... And four Duracell batteries died.
Well, at least Hobbit managed to get your attention that there was some configuration problem :-)
Seriously - you're right, it shouldn't do that. Such a problem should end up with a red status in the "bbtest" column and nothing else. I'll make sure it does that.
Sorry about the trouble!
Regards, Henrik
participants (2)
-
brodie@mcw.edu
-
henrik@hswn.dk