Hello,
I don't know if it's related, but today I updated some modules
(ecommerce, gsitemap) on my drupal test site , and then something
broke.
Now, whenever I edit a node (page or product)
I now get a blank screen and another instance of /usr/bin/php index.php
is added to the process table.
After a few click edit cycles, I get The MySQL error :
User kettlest_sqladmi has already more than 'max_user_connections' active connections.
Below, I've excerpted the runtime mysql stats that are highlighted in
red as trouble, and was hoping someone could either explain what
happened or give me some hints as to the cause before I resort to the
backup database and hope the problem goes away.
Thanks,
-------------------------------
Handler_read_rnd 2,564 k The number of requests to read a row based on a fixed position. This is high if you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan whole tables or you have joins that don't use keys properly.
Handler_read_rnd_next 260 M The number of requests to read the next row in the data file. This is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.
Qcache_lowmem_prunes 118 k The number of queries that have been removed from the cache to free up memory for caching new queries. This information can help you tune the query cache size. The query cache uses a least recently used (LRU) strategy to decide which queries to remove from the cach
Threads_cached 31 The number of threads in the thread cache. The cache hit rate can be calculated as Threads_created/Connections. If this value is red you should raise your thread_cache_size.
Created_tmp_disk_tables 18 k The number of temporary tables on disk created automatically by the server while executing statements. If Created_tmp_disk_tables is big, you may want to increase the tmp_table_size value to cause temporary tables to be memory-based instead of disk-based.
Select_full_join 6,290 The number of joins that do not use indexes. If this value is not 0, you should carefully check the indexes of your tables.
Select_range_check 18 The number of joins without keys that check for key usage after each row. (If this is not 0, you should carefully check the indexes of your tables.)
Sort_merge_passes 374 The number of merge passes the sort algorithm has had to do. If this value is large, you should consider increasing the value of the sort_buffer_size system variable.
Opened_tables 17 k The number of tables that have been opened. If opened tables is big, your table cache value is probably too small.
Table_locks_immediate 1,567 k The number of times that a table lock was acquired immediately.
Table_locks_waited 904 The number of times that a table lock could not be acquired immediately and a wait was needed. If this is high, and you have performance problems, you should first optimize your queries, and then either split your table or tables or use replication.
