BB Unix Network Monitor - Message

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: {bb} The bb_rename error problem



Title: Message
Brent,
 
Have you considered using RAM disks to increase performance? [bb]/www/html amd [bbvar]/logs are easily configured as tmpfs in /etc/vfstab. If you use a start/stop script in /etc/*.d you can add lines to preserve and restore these directories after stopping and before starting the BB server process using tar.
 
Hints (my bb server uses /opt/bb and /opt/bbvar):
swap    -       /opt/bb/www/html    tmpfs   -       yes     size=10M
swap    -       /opt/bbvar/logs        tmpfs   -       yes     size=10M
(You will probably want to increase the 10M)
#!/sbin/sh
BBDIR=/opt/bb
BBVAR=/opt/bbvar
BBUSER=bb
if [ -x $BBDIR/runbb.sh ]
then
        if [ "start" = "$1" ]
        then
                if [ -f $BBDIR/bbtmp.tar ]
                then
                        /usr/bin/tar xf $BBDIR/bbtmp.tar $BBDIR/www/html $BBVAR/logs
                fi
                /usr/bin/su - $BBUSER -c "cd $BBDIR;/usr/bin/nohup ./runbb.sh start"
        else
                /usr/bin/su - $BBUSER -c "cd $BBDIR;./runbb.sh stop"
                /usr/bin/tar cf $BBDIR/bbtmp.tar $BBDIR/www/html $BBVAR/logs
        fi
fi
 
Hope this helps with reducing the disk i/o.
 
Erwin
 
 -----Original Message-----
From: owner-bb@bb4.com [mailto:owner-bb@bb4.com]On Behalf Of brent.mccrackin@bell.ca
Sent: Wednesday, 26 January, 2005 20:58
To: bb@bb4.com
Subject: {bb} The bb_rename error problem

I have a very large and very busy BB server, and notice a lot of bb_rename errors logged to BBOUT where new status logs are unable to be renamed, with an errno 2 message.
 
Wed Jan 26 08:56:23 2005 bbd bb_rename Could not rename /bbvar/logs/.somehost.http to /bbvar/logs/somehost.http - errno: 2
 
I've looked through the list archives, and suggestions have been that this is a result of a host appearing multiple times in the BB-HOSTS file either on the server or the client.  This is most definitley not the case for me.
 
The root cause of the problem is high I/O wait times on the disks where the logs are stored, with the affected disks running at a fairly constant 80% to 90% busy.  This can be alleviated with faster disks, higher I/O bandwidth, and separating the BBVAR directory across multiple filesystems.
...


-----------------------------------------------------------------
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.

Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------

Home | Main Index | Thread Index