{bb} unknown host or planned down

["SIGSEGV ." <device.not.found@gmail.com>]

Greetings! This is my first post to the list. I believe I've exhausted
the archives attempting to find a solution to a few issues I've been
having recently. We've been using Big Brother here at work for at
least 3 years now and have been very happy with it. I decided to
finally upgrade to 1.9e, and also added bbgen-3.5. I have also set up
a tiered structure, as we have multiple isolated subnets, so the setup
looks like:

                 BB Prime
               /                \
           Site1           Site2

With each site having its own BBDISPLAY server, and a BBRELAY pointing
to BB Prime display server. All servers are running Solaris 8 with the
latest cluster patch. The relaying is working fine. However, I'm now
seeing the following problems:

1> The BBOUT file on Prime is filling up with messages for every blued
out server that we have, and there are a lot:

Mon Apr 11 15:27:39 2005 bbd: page from someservername.conn ignored -
unknown host or planned down

I know the server is down, that's why I blued it out. How can I shut
off these messages? The hostnames are all FQDN and resolve just fine.
Also I made sure to format the bb-hosts entries for the sub-sites on
Prime as: 0.0.0.0  somesite #noconn
to avoid duplicate checking.

2> Seeing the same odd bb_rename errors whenever I try to blue out a
service. About 3/4 of the time, the disable still works. However, when
I first turned on relaying, and was seeing a lot of errors from
services that were already blued out at the lower level, I had a lot
of things to blue out at once. What was happening, was the Prime
bb2.html page showed some things blue, and some purple, even though if
you click the dot to drill down, the status page was blue. I managed
to track down the problem to the bbvar/logs. I noticed that the
services showing purple dots did not have log files with timestamps in
the future, but the present. If I touched the file with some date in
the future, the next refresh of bb2.html showed the dot as blue now.
So some part of the disable is not setting that timestamp properly,
but I haven't had time to see what might be failing.

3> I used to see this error in 1.8d3 before upgrading, and had been
ignoring it as I had read it wasn't anything to be concerned about,
but it's cropping up again and I wonder if it's related to my other
issues in any

/var/adm/messages (scanned at Tue Apr 12 11:44:16 EDT 2005)
Apr 12 11:42:13 servername genunix: [ID 533030 kern.notice] NOTICE:
bbd[7251] attempt to execute code on stack by uid 112
Apr 12 11:42:13 servername genunix: [ID 603404 kern.notice] NOTICE:
core_log: bbd[7251] core dumped: /var/crash/servername/servername.bbd

Thanks for any help! :)
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.