[rt-users] Eeek! RT is unable to connect to database

Jerrad Pierce jpierce at cambridgeenergyalliance.org
Tue Feb 10 14:42:47 EST 2009


On Tue, Feb 10, 2009 at 14:37,  <jmoseley at corp.xanadoo.com> wrote:
> Report the results of a diff between the old version of my.cnf and the one
> after your changes.
As previously reported, the changes have already been undone. The diff
is /dev/null

They were nothing ground-breaking:
--- /etc/my.cnf 2008-10-06 17:08:18.000000000 -0400
+++ /etc/my.new 2009-02-10 14:34:40.000000000 -0500
@@ -5,19 +5,26 @@
 # clients (those using the mysqlclient10 compatibility package).
 #old_passwords=1
 skip-networking
+skip-isam
+skip-bdb

 #my-large.cnf
 key_buffer = 256M
 max_allowed_packet = 4M
 table_cache = 256
-sort_buffer_size = 1M
+sort_buffer_size = 2M
 read_buffer_size = 1M
 read_rnd_buffer_size = 4M
 myisam_sort_buffer_size = 64M
 thread_cache = 8
 query_cache_size= 16M
 thread_concurrency = 4
+#mysqltuner.pl{
+  tmp_table_size = 32M
+  max_heap_table_size = 32M
+#}

+#XXX skip-innodb
 # You can set .._buffer_pool_size up to 50 - 80 %
 # of RAM but beware of setting memory usage too high
 innodb_buffer_pool_size = 256M
@@ -33,7 +40,6 @@
 innodb_additional_mem_pool_size=2M
 innodb_file_io_threads=4
 innodb_lock_wait_timeout=50
-sort_buffer=2M
 innodb_additional_mem_pool_size = 20M



-- 
Cambridge Energy Alliance: Save money. Save the planet.



More information about the rt-users mailing list