I work for vBulletin and have some input on this. First off, you really
should look into upgrading to version 2.2.x, as not only are there many
new features, but there have been a number of performance enhancements
done that may help your situation. You also might want to take a look
at the vBul
Error code 28: No space left on device
You're out of disk space on the drive where your databases are stored.
Chris Schreiber
-Original Message-
From: John Lepone [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 17, 2001 3:20 PM
To: '[EMAIL PROTECTED]'
Subject: ERROR 1006: Can't crea
Actually I setup a vBulletin forum for MySQL over at www.mysqlforums.com
and I am the moderator of the MySQL and Server Configuration forums over
at www.vbulletin.com/forum/
I've been keeping an archive of the mailing lists, mainly for my own
purposes to search through old questions and answers f
Sure, open up a new MySQL session, and use "SHOW PROCESSLIST;" to monitor
the query status. It should report what it's doing and how long the
process has been running.
Chris Schreiber
-Original Message-
From: Karl Stubsjoen [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 10, 2001 8:38
I've had the same experience myself. I had a client running a large MySQL
database with 500+ concurrent users on a Sun E420R quad processor machine
with 2GB RAM and mirrored SCSI drives. Performance was acceptable, but
there
were some performance problems during peak usage times, that shouldn't
If you are running FreeBSD, there is an inner limit, which doesn't allow
malloc() calls greater then 500MB. You need to reconfigure the kernel
sources and recompile (or change your InnoDB parameters to use less then
500MB of RAM).
Chris Schreiber
-Original Message-
From: Heikki Tuuri [m
