I’m trying to troubleshoot a server that just keeps cracking up.
We get errors to the tune of “Could not select database;
Could not connect: Too many connections” printing to the screen, but when I go off and
the problem has cleared up. I’m not even sure how to tell where the problem is coming from.
I was ready to pin the blame on our Phorum forums, but I limited the phorum’s mysql user to 5 connections and it is still happening.
Can I tweak my logs at all to see where these scrums are coming from?
And: the timeouts of 3600 seem crazy long to me, but they were set by a predecessor.
my my.cnf is at [URL]Phpfi.com is for sale | HugeDomains or below.
[mysqld]datadir=/var/lib/mysqlsocket=/var/lib/mysql/mysql.sock# Default to using old password format for compatibility with mysql 3.x# clients (those using the mysqlclient10 compatibility package).old_passwords=1#ABH Edit 2008-01-09log-slow-queries = /var/log/mysql/mysql-slow.loglong_query_time = 5# Rackspace edit per #060815-01133key_buffer = 384Mmax_allowed_packet = 1Mtable_cache = 512sort_buffer_size = 2Mread_buffer_size = 2Mread_rnd_buffer_size = 8Mmyisam_sort_buffer_size = 64Mthread_cache_size = 8query_cache_size = 32M# Try number of CPU’s*2 for thread_concurrencythread_concurrency = 8wait_timeout = 3600interactive_timeout = 3600# End Rackspace edit[mysql.server]user=mysqlbasedir=/var/libmax_connections=200[mysqld_safe]#ABH Edit 2008-01-09#err-log=/var/log/mysqld.logerr-log=/var/log/mysql/err-mysqld.logpid-file=/var/run/mysqld/mysqld.pid## ABH EDIT 2008-4-16# The following can be used as easy to replay backup logs or for replication.#server-id = 1log_bin = /var/log/mysql/mysql-bin.log# WARNING: Using expire_logs_days without bin_log crashes the server! See README.Debian!expire_logs_days = 10max_binlog_size = 100M#binlog_do_db = include_database_name#binlog_ignore_db = include_database_name