Re: {bb} big brother monitoring a df that it shouldn't be

Scott Mohnkern wrote:
> Thanks for your help,
>=20

what platform is this on? if Solaris 8 (not sure) you may need to=20
install a patch for the tail command.

otherwise, check the free inodes:

df -ki

if you have a BB server on the box, sometimes that'll chew a lot of=20
inodes.  Purge older historical logs if that's the case.

bye

> Directory "warned" about is /usr/local/bb16e1/tmp
>=20
> Looks okay to me:
>=20
> -bash-3.1$ cd /usr/local/bb16e1
> -bash-3.1$ ls -alt | grep tmp
> drwxr-xr-x  2 bb   users   4096 Mar 11 10:05 tmp
>=20
> -bash-3.1$ cd tmp
> -bash-3.1$ ls -alt
> total 28
> -rw-r--r--  1 bb users   63 Mar 17  2008 [email protected]
> drwxr-xr-x  2 bb users 4096 Mar 11 10:05 .
> -rw-r--r--  1 bb users  366 Mar 11 10:05 BB
> -rw-r--r--  1 bb users    0 Mar 11 10:03 .expire
> -rw-r--r--  1 bb users    4 Mar 11 08:01 _var_log_messages
> -rw-r--r--  1 bb users   18 Mar 10 13:14 BBPID
> drwxr-xr-x 10 bb users 4096 Feb 21 14:55 ..
>=20
> However I am troubled by the file with a date of March 17 2008.
>=20
>=20
>=20
> And just to make sure that everything is running under user bb:
>=20
> -bash-3.1$ ps -ef | grep bb
> bb        4540 24679  0 10:06 ?        00:00:00 sleep 149
> bb        5523 24990  0 10:07 ?        00:00:00 sleep 144
> mohnkern  5548  4085  0 10:08 pts/2    00:00:00 grep bb
> bb       24672     1  0 Mar10 ?        00:01:12 /usr/local/bb16e1/bin/b=
bd
> bb       24676     1  0 Mar10 ?        00:00:00 /bin/sh=20
> /usr/local/bb/runbb.sh start
> bb       24677     1  0 Mar10 ?        00:00:00 /bin/sh=20
> /usr/local/bb/runbb.sh start
> bb       24679 24676  0 Mar10 ?        00:00:02 /bin/sh=20
> /usr/local/bb16e1/bin/bbrun /usr/local/bb16e1/bin/bb-local.sh
> bb       24990 24677  0 Mar10 ?        00:00:02 /bin/sh=20
> /usr/local/bb16e1/bin/bbrun /usr/local/bb16e1/bin/bb-display.sh
>=20
>=20
> Scott
>=20
> Timmers, Frank wrote:
>=20
>>>I'm having a problem with bb a 1.6e1 client reporting on a partition
>>>that it shouldn't be.
>>>It's acting like the tmp directory for the client (in this case
>>>/usr/local/bb16e1/tmp) is a partition, and reporting it full (and its
>>>not a partition at all, just a directory).
>>>adding the following to bb-dftab doesn't seem to help:
>>>localhost:/usr/local/bb16e1/tmp:101:101
>>>For the life of me, I can't figure out where it's deciding that
>>>/usr/local/bb16e1/tmp is a partition, and that it needs to be monitore=
d.
>>
>> Check the write permissions for BB on that directory and the files=20
>> beneath. Often when BB complains tmp is full, it=92s an rights problem.
>>
>> =20
>>
>> /Frank.
>>
>=20
> -----------------------------------------------------------------------=
-
>=20
> No virus found in this incoming message.
> Checked by AVG.=20
> Version: 7.5.518 / Virus Database: 269.21.7/1324 - Release Date: 3/10/2=
008 7:27 PM


--=20
Robert-Andre Croteau    BSD,MOTU
Quest Software, Inc.            Big Brother, Product Architect
http://www.quest.com/                          http://bb4.com/
+1 (514) 238-9374
         Si le bonheur ne s'achete pas alors louez le.
--
=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:[email protected] with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.