Re: {bb} unable to contact BBD

[Ben Pitzer <bpitzer@gmail.com>]

Okay, this is getting a tad ridiculous.  I can cd into $BBHOME/bin and
run the following:

./bb <BBDISP IP> "status testhost,domain,com.TEST green Bogus Info"

...and have it show up.  Why is bbtest-net unable to contact the bb
host?  Why does this show up in the bbtest entry in BB:

TIME SPENT
Event                                            Starttime          Duration
bbtest-net startup                       1110393573.635693                 -
Service definitions loaded               1110393573.638984          0.003291 
Tests loaded                             1110393573.667710          0.028726 
DNS lookups completed                    1110393573.719624          0.051914 
Test engine setup completed              1110393573.723017          0.003393 
TCP tests completed                      1110393594.007738         20.284721 
Test result collection completed         1110393594.007872          0.000134 
LDAP test engine setup completed         1110393594.007875          0.000003 
LDAP tests executed                      1110393594.007877          0.000002 
LDAP tests result collection completed   1110393594.007879          0.000002 
NSLOOKUP tests executed                  1110393595.143939          1.136060 
Test results transmitted                 1110394225.267397        630.123458 
bbtest-net completed                     1110394226.327167          1.059770 
TIME TOTAL                                                        652.691474

Cany anybody explain why the test results transmission is taking so
long?  Port 1984 is listening, but is not terribly active.  I'm lost
here, folks.  Any pointers would be appreciated.

Solaris 8
BB 1.9e
bbgen 3.5
gcc 3.4.1
GNU make 3.8.0

Regards,
Ben Pitzer


On Wed, 9 Mar 2005 12:38:38 -0500, Ben Pitzer <bpitzer@gmail.com> wrote:
> Okay, well, I've got the fping.sh problem resolved, but the overall
> problem remains:
> 
> Wed Mar  9 12:33:06 2005 bbd CONNECTION TO my-bb-server.domain.com TIMED OUT...
> Wed Mar  9 12:33:06 2005 bbd CAN'T CONNECT TO bbd SERVER @
> my-bb-server.domain.com
> 
> The tcp_time_wait_interval is at 30000, so that's not causing it,
> either.  I'm not sure about the tmpfs directories, but given the
> scripts that I have to run, I can't really spare the memory for that
> particular solution.  I can look into the bbproxy piece, but I'm not
> sure if that's something I can implement or not.
> 
> Any more ideas would be greatly appreciated.
> 
> Regards,
> Ben Pitzer
> 
> 
> On Tue, 8 Mar 2005 22:58:23 +0000 (UTC), Henrik Storner
> <henrik-bb@hswn.dk> wrote:
> > In <7eeb9e7f050308144627ee5879@mail.gmail.com> Ben Pitzer <bpitzer@gmail.com> writes:
> >
> > >I have gotten everything taken care of that I know how to do, and now
> > >I'm getting this problem in BBOUT:
> >
> > >Tue Mar  8 17:39:40 2005 fping.sh Tue Mar  8 17:39:40 2005
> > >bb CONNECTION TO my-bb-host.domain.tld TIMED OUT...
> > >Tue Mar  8 17:39:40 2005 fping.sh Tue Mar  8 17:39:40 2005 bb CAN'T
> > >CONNECT TO bbd SERVER @ my-bb-host.domain.tld
> >
> > >It appears that fping.sh is my culprit here, but I have no idea what
> > >the deal is.  I'm trying to build a BB 1.9e server on Solaris 8.
> > >bbtest reports 610 seconds taken up in the reporting phase
> >
> > First, why are you running both bbtest-net (from bbgen, I suppose) and
> > fping.sh ? bbtest-net has built-in fping support so you'll end up with
> > two sets of ping-tests.
> >
> > As for the error you are seeing - how many hosts do you have ? I used
> > to see this a lot with a Solaris 8 box that just couldn't handle the
> > sudden reporting of network-test statuses from 2000 hosts. Some things
> > to check:
> >
> > * Solaris' default TIME_WAIT period is ridiculous, and causes it to
> >   keep bbd-processes hanging around forever. A workaround is to run
> >     /usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 30000
> >
> > * Consider using a tmpfs filesystem for the bbvar/logs/ and
> >   bb/www/html/ directories. This does speed things up, since you
> >   avoid the disk-I/O that is done with every status message.
> >
> > * Consider using the bbgen "bbproxy" tool as an front-end to your bbd
> >   daemon. bbproxy has a built-in queuing mechanism so it can absorb
> >   bursts of messages and pass them on to bbd at a smoother pace. It
> >   also merges lots of small messages into large combo-messages, which
> >   means fewer connections to your bbd and fewer spawned processes to
> >   handle them.
> >
> > Regards,
> > Henrik
> > --
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
> > 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.
> >
>
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
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.