Problems with PLESK DB under certain conditions.

[DiegoMax]

Hi there, im running PSA 8.2 on a centOS 4.5 machine. Yesterday, the guys from VBulletin.com suggested me to change some configurations on my mysql configuration file, and after i did that, it is impossible to access plesk anymore.
I'm pasting here the problematic my.cnf file in the hope that somebody here can tell me what's the part that PSA seems to hate.

[mysqld]
#old_passwords
log-slow-queries = /tmp/mysql_slow.log
long_query_time = 1
back_log = 50
skip-innodb
max_connections = 650
key_buffer_size = 64M
myisam_sort_buffer_size = 64M
join_buffer_size = 1M
read_buffer_size = 1M
sort_buffer_size = 2M
table_cache = 2500
thread_cache_size = 384
wait_timeout = 35
connect_timeout = 10
tmp_table_size = 128M
max_heap_table_size = 128M
max_allowed_packet = 64M
max_connect_errors = 10
thread_concurrency = 4
concurrent_insert = 2
table_lock_wait_timeout = 35
read_rnd_buffer_size = 524288
bulk_insert_buffer_size = 8M
query_cache_limit = 6M
query_cache_size = 96M
query_cache_type = 1
query_prealloc_size = 131072
query_alloc_block_size = 65536
default-storage-engine = MyISAM

[mysqld_safe] 
nice = -5
open_files_limit = 8192

[mysqldump]
quick
max_allowed_packet = 16M

[myisamchk] 
key_buffer = 64M 
sort_buffer = 64M
read_buffer = 16M
write_buffer = 16M

If i use this configuration file, it is inpossible to access the plesk control panel both for users and/or site owners.

Thanks in advance.
Diego Massanti.

 

[DiegoMax]

Originally posted by DiegoMax
Hi there, im running PSA 8.2 on a centOS 4.5 machine. Yesterday, the guys from VBulletin.com suggested me to change some configurations on my mysql configuration file, and after i did that, it is impossible to access plesk anymore.
I'm pasting here the problematic my.cnf file in the hope that somebody here can tell me what's the part that PSA seems to hate.

Scratch all this. I am officially an idiot.

The problematic config statment was (obviously):

skip-innodb

This is not documented but it seems to drop any support for tables other than myISAM, and the guys at vbulletin seems to like this

In any case, that was the problem.
Thanks.

 

[siren@]

They guys at vBulletin don't like people running VB on shared boxes either from my experience.

Which means what they recommend is aimed at a box "ONLY" running vBulletin or a seperate MySQL Server.

 

[breun]

skip-innodb is documented and tells MySQL to disable support for InnoDB tables.