On Fri, 2006-02-17 at 15:02, Ryan Novosielski wrote:
Contrary to what I told a gentleman on the list earlier this week,
apparently, I still seem to be getting paged even while the system in
question is disabled and shows up blue in the BBDISPLAY. I suppose my
question is, how does one properly disable everything? I assume that I
need -DENABLE_DISABLE on every bbd host, right? I previously assumed
that it was necessary only on the display, but then I went and enabled
it on BBPAGER also. The only thing left is one of the BBNET machines
(though, I /have/ done the one that is testing the disabled machine).
Any hints here?
I guess this worked properly when all three were on the same host -- now
it does not seem to.
Time for a caveat. It's been some time since I had a close look at
the disable feature and things appear to have changed quite a lot
since then. As a result, this might not be too accurate.
It looks like the only machines that need to have ENABLE_DISABLE
applied are the display and pager hosts. It also looks like enable
and disable messages are distributed to the pager host(s) by "bbd" on
the display host that receives the message. As a result, it is
essential that bb-hosts on the display host identifies the appropriate
pager(s).
If things are working correctly, you should see relevant files appear
in BBVAR/disabled on each server. The BBOUT file on the display server
might also contain entries if it has encountered a problem in forwarding
a disable request to a pager host.
To get the complete picture, you would probably need to enable debugging
and examine the output. If you are going to do that, it probably makes
sense to start with the pager first. There should be much less traffic
on that machine and it will let you know if the message is arriving
there.
Cheers, Phil.