Yep... got it... as luck has it, I was just able to log in and use the CP.

Here is what I'm seeing:

Beginning at 09:28 this morning this is the error message that filled my log file:
Script: - Line: Unable to connect to the database! - Can't create a new thread (errno 12); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug

Then from 11:46 to 13:13 it was this:
Script: - Line: Unable to connect to the database! - User vccachat already has more than 'max_user_connections' active connections

Then from 13:14 to 13:43 it went back to this:
Script: - Line: Unable to connect to the database! - Can't create a new thread (errno 12); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug

Then from 13:55 to 14:18
Script: - Line: Unable to connect to the database! - Lost connection to MySQL server at 'reading initial communication packet', system error: 0
=====================
Does this look like it could be caused by increaed users on the forum??? That's what the HOST is telling me... and of course, they want me to upgrade to a VPS for more $$$ per month.

Well, if you've seen a substantial increase in users, then potentially that could be the problem. Not from just a couple more users however. And the upgrade from 7.4 to 7.5 definitely doesn't add any more database connections.

Are you running the forum stats box on your site, and if so has your max online record been set recently?

errno 12 comes from a couple of things.

Primarily, there is a bug in earlier versions of MySQL 5.1 and some 5.0.x versions. http://bugs.mysql.com/bug.php?id=20815 You might want to upgrade your MySQL version. 5.0.x versions previous to 5.0.48 also exhibit this behavior.

The next possibility is that you've reached the limit of a 32 bit OS and can't allocate more memory but that would take millions of posts, not thousands.

Thanks. Every little bit helps.

1) No our Max Online hasn't changed since 03/31/08.
2) We finally got back on line by turning OFF the FastCGI function.
3) An SA at the hosting company finally admitted that he upped the PageFile setting.

Currently set at:
max_user_connections set to 100
max_connections=300 set to 300

After four days of relative calm, some users still experience some slowdowns and error messages, but most are doing okay.

I'm thinking about moving to a VPS. Does anyone have experience with hosting UBB and the MySQL db on the same server??

"I'm thinking about moving to a VPS. Does anyone have experience with hosting UBB and the MySQL db on the same server??"

This one is. As is UBBDev. They are not vps though.

Did you check on the MySQL server version number?

PHP Version 5.2.6

We had another 20 minute SLOW DOWN today... I got dozens of emails from people letting me know. I just sent the entire log file to the host... but they don't seem to know what to do.

I'm now looking at webintellects.com VPS with Linux.

But I'm wondering if having UBB and MySQL on the same server is a good idea or not.

Bill, I'm not trying to give you a hard time, but 3 times you've seemed to miss the one thing above all that causes this error. http://bugs.mysql.com/bug.php?id=20815

Have you checked your MySQL server version yet against the versions known to have the bug that most commonly gives the errno 12 error? You answered with PHP version but is not MySQL server version.

Please check that as it is the most likely cause.

And regarding MySQL and the webserver on the same host; that's actually how most environments are...

David, I love you man. Give me a hard time. ?!?!

Sorry, I was too distracted to stay focused. Tonight for the first time in 3 years, my host has finally sent me the list of the server settings.

Here's what I just pulled for the MySQL info:
MySQL client version: 5.0.22
and
Server version: 5.0.45-community-nt


Here is a copy of the current mysql configuration:

[MySQLD]
port=3306
basedir=E:\\Databases\\MySQL
datadir=E:\\Databases\\MySQL\\Data
default-character-set=latin1
default-storage-engine=INNODB
read_buffer_size=1M
read_rnd_buffer_size=256K
sort_buffer_size=256K
innodb_additional_mem_pool_size=2M
innodb_flush_log_at_trx_commit=1
innodb_log_buffer_size=1M
innodb_buffer_pool_size=16M
innodb_log_file_size=10M
innodb_thread_concurrency=8
max_connections=400
old_passwords=1
max_user_connections=100
thread_cache_size=4
thread_stack=196608
binlog_cache_size=32768
net_read_timeout=300
net_retry_count=10
net_write_timeout=300
thread_concurrency=10
wait_timeout=400
interactive_timeout=400
open_files_limit=0
[client]

5.0.45. In other words, 3 sub versions before the bug was fixed at 5.0.48. Your server version has the bug known to cause issue that you have. Encourage them to upgrade to something newer. Give them the link to to that bug if they need to understand why they need to upgrade.