my.cnf corrupts Plesk database

[BryanE]

I just upgraded to a new Dual Xeon 5520 w/12 Gig ram Linux/Plesk server at ThePlanet.com. I prepared a new my.cnf file based on the one I was using in my previous Plesk server, but when I installed it and restarted the services, the Plesk database got corrupted -- this happens every time and was confirmed by ThePlanet support people. We have to restore to the previously saved version.

However, no one knows which command is causing the problem. All they can tell me is that they think my.cnf file is "too restrictive" for the version of Plesk that I'm running now. Until I figure this out I'm stuck using the default my.cnf file. Please let me know specifically why this my.cnf is corrupting the Plesk database. Thanks!

[mysqld]
set-variable=local-infile=0
datadir=/var/lib/mysql
socket=/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
skip-locking
max_user_connections=25
max_connections=500
join_buffer_size = 2M
read_buffer_size = 2M
sort_buffer_size = 2M
key_buffer = 256M
myisam_sort_buffer_size = 64M
table_cache=1024
max_allowed_packet=16M
max_connect_errors = 10
interactive_timeout=100
wait_timeout=300
connect_timeout=15
thread_cache_size = 100
query_cache_type = 1
query_cache_limit = 1M
query_cache_size =128M
tmp_table_size = 128M
max_heap_table_size = 128M
long_query_time = 5
#Mod TP-Ryan
#skip-innodb
innodb_log_file_size = 64M
innodb_log_buffer_size = 64M
record_buffer = 2M
read_rnd_buffer_size=1M
innodb_buffer_pool_size = 128M
skip-bdb
thread_concurrency=4

[isamchk]
key_buffer = 64M
sort_buffer_size = 64M
read_buffer = 16M
write_buffer = 16M

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

[mysqlhotcopy]
interactive-timeout

[mysql.server]
user=mysql
basedir=/var/lib

[mysqld_safe]
open_files_limit = 8192
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

 

[lvalics]

I feel you have upgraded to 5.1 in new server and then rid off this line
skip-bdb

Then will work.

 

[rockstar]

Brilliant!

Thank you so much Ivalics! You saved me a LOT of grief this afternoon. Your solution worked perfectly.

 

[lvalics]

Welcome