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

Robert-Andre Croteau wrote:
> Scott Mohnkern wrote:
>> Thanks for your help,
>>
>
> what platform is this on? if Solaris 8 (not sure) you may need to=20
> install a patch for the tail command.
>

Rhel 5

> otherwise, check the free inodes:
>
> df -ki

[root@hsp ~]# df -ki
Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/mapper/VolGroup00-LogVol00
                     2555904  732809 1823095   29% /
/dev/sda1              26104      38   26066    1% /boot
tmpfs                  64440       1   64439    1% /dev/shm
/dev/mapper/VolGroup00-LogVol03
                     1302528     890 1301638    1% /var/lib/mysql
/dev/mapper/VolGroup00-LogVol01
                     3809280   66219 3743061    2% /var/www
/dev/mapper/VolGroup00-LogVol02
                     2371040      37 2371003    1% /var/www/html/logs
140.90.20.81:/B2     30215296   18445 30196851    1% /fs/hdsb5
140.90.20.80:/A4     92500992  245224 92255768    1% /fs/hdsb6
140.90.20.80:/A5     18013968   10911 18003057    1% /fs/hdsb4

no problem here either.

Scott

>
> 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
>>
>> Looks okay to me:
>>
>> -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
>>
>> -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 ..
>>
>> However I am troubled by the file with a date of March 17 2008.
>>
>>
>>
>> And just to make sure that everything is running under user bb:
>>
>> -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=20
>> /usr/local/bb16e1/bin/bbd
>> 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
>>
>>
>> Scott
>>
>> Timmers, Frank wrote:
>>
>>>> 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 it=
s
>>>> 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=20
>>>> monitored.
>>>
>>> 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 proble=
m.
>>>
>>> =20
>>>
>>> /Frank.
>>>
>>
>> ----------------------------------------------------------------------=
--
>>
>> No virus found in this incoming message.
>> Checked by AVG. Version: 7.5.518 / Virus Database: 269.21.7/1324 -=20
>> Release Date: 3/10/2008 7:27 PM
>
>
--
=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.