{bb} Re: BBOUT filles the filesystem - Thanks

[Dietmar Felmer <Dietmar.Felmer@ivmed.med.uni-erlangen.de>]

Thank You Brothers,

Henrik Olsen wrote:
> 
> <snip>
> > For your other question...  The 'conn', 'ftp', 'telnet' and other
> > connectivity-type tests are run from the BBDISPLAY machine, not the 
> > client.
> Quick correction here, it's of course BBNET that does the network tests.
> 

Yes, I knew that. What I tried to say was, that BBDISPLAY and BBNET (on
the same mashine, SUN U-1/Solaris 2.5, with BB 1.3) were running, but
the accordant dots for the stopped (on 13.01.2000) BB-client ('disk',
'msgs', 'procs') never turned to purple after 30 min, not even after
restarting the BB-server (BBDISPLAY,BBNET). 
To find out the reason of this behavior I din't restart the BB-client
(v. 1.2b) on that mashine until yesterday (31.01.2000), only the
BB-server, but with no success. The BB-server didn't realise that the
logs from that client were out of date. 
Yesterday before I started the BB-client on that mashine (SUN
U-250/Solaris 2.6) I made a 'ps -ef | grep bb' and didn't found any BB
process, but when I started the BB-client I got the answer that "bb is
already running". 
Maybe this all happens, because the BB-client wasn't stopped, but
killed.
     
> > maybe one of You can help me to stop BBOUT increasing to fast an
> > filling the / filesystem (BBHOME=/opt/bb). The problem is that the
> > BBOUT file is always open when bbd runs (= all the time) and therefore
> > it can't be reduced.
> echo "" >BBOUT
> should work for truncating it even when held open by bbd.

I tried this: 

tail -1000 $BBHOME/BBOUT > $BBTMP/BBOUT; mv $BBTMP/BBOUT $BBHOME/BBOUT

but this was the reason that the BBOUT file increased so rapidly. The
file never grows over 1000 lines but the initial storage was never
deallocated.
It's my fault, my new BBOUT file has another inode and the old one is
also in use with it also the storage area. 

- echo "" > BBOUT - seems to be the best tip.

> 
> > Another strange behavior I had some days ago when one bb client
> > mashine was rebooted within 4 min so the 'conn' dot never goes red. As
> > BB wasn't started after reboot I expected that all the dots except
> > 'conn' and the network dots (ftp, telnet,..) must turn to purple after
> > 30 min but they didn't. Everything else is working fine, so I donno
> > whats the cause.
> Do you mean that BB didn't restart on the client, so you didn't get
> purple cpu, disk, mesg and procs as you expected?
>
Yes. We still use to start BB by hand, yet. 
 
> When looking at the dots, could you see by the time reported that they
> where more than 30 minutes old, but they still where not purple as
> expected?
>
Yeah, for this reason I din't realised that the BB-client wasn't
running; all the dots were green. Only a week later I looked around in
the BB-server www directory and find out that the files from that client
were out of date. 

> If so, what exact version of BB are you running, there was a bug in
> calculating the purple delay in the early 1.3 versions.
> 
On the BB-server (BBDISPLY, BBNET) we use v. 1.3 and on the BB-client v.
1.2b.

> > Any help would be great,

The help was verry great - merci.
 
> > Dietmar
>
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
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.