We haven't been able to solve our problem so we switched to a staging/live configuration. The probloem hasn't occurred after that. We think the cause was a race-condition involving the Repligard table when using a single db.
Aegirfan --- In [EMAIL PROTECTED], "aegirfan2003" <[EMAIL PROTECTED]> wrote: > Gentlemen, > > Thank you for your advice. We are focusing on MySQL now. Please give > us any comment you may have on the MySQL settings we use: > > Variable_name Value > back_log 50 > basedir /usr/ > bdb_cache_size 8388600 > bdb_log_buffer_size 32768 > bdb_home /var/lib/mysql/ > bdb_max_lock 10000 > bdb_logdir > bdb_shared_data OFF > bdb_tmpdir /tmp/ > bdb_version Sleepycat Software: Berkeley DB > 3.2.9a: (February 14, 2002) > binlog_cache_size 32768 > character_set latin1 > character_sets latin1 big5 cp1251 cp1257 croat czech > danish dec8 dos > estonia euc_kr gb2312 gbk german1 > greek hebrew hp8 > hungarian koi8_ru koi8_ukr latin2 > latin5 swe7 usa7 > win1250 win1251 win1251ukr ujis sjis > tis620 > concurrent_insert ON > connect_timeout 5 > datadir /var/lib/mysql/ > delay_key_write ON > delayed_insert_limit 100 > delayed_insert_timeout 300 > delayed_queue_size 1000 > flush ON > flush_time 0 > have_bdb YES > have_gemini NO > have_innodb DISABLED > have_isam YES > have_raid YES > have_openssl NO > init_file > innodb_additional_mem_pool_size 1048576 > innodb_buffer_pool_size 8388608 > innodb_data_file_path > innodb_data_home_dir > innodb_file_io_threads 4 > innodb_force_recovery 0 > innodb_thread_concurrency 8 > innodb_flush_log_at_trx_commit OFF > innodb_fast_shutdown OFF > innodb_flush_method > innodb_lock_wait_timeout 50 > innodb_log_arch_dir > innodb_log_archive OFF > innodb_log_buffer_size 1048576 > innodb_log_file_size 5242880 > innodb_log_files_in_group 2 > innodb_log_group_home_dir > innodb_mirrored_log_groups 1 > interactive_timeout 600 > join_buffer_size 131072 > key_buffer_size 16773120 > language /usr/share/mysql/english/ > large_files_support ON > locked_in_memory OFF > log ON > log_update OFF > log_bin OFF > log_slave_updates OFF > log_long_queries OFF > long_query_time 10 > low_priority_updates OFF > lower_case_table_names 0 > max_allowed_packet 1047552 > max_binlog_cache_size 4294967295 > max_binlog_size 1073741824 > max_connections 100 > max_connect_errors 10 > max_delayed_threads 20 > max_heap_table_size 16777216 > max_join_size 4294967295 > max_sort_length 1024 > max_user_connections 0 > max_tmp_tables 32 > max_write_lock_count 4294967295 > myisam_max_extra_sort_file_size 256 > myisam_max_sort_file_size 2047 > myisam_recover_options 1 > myisam_sort_buffer_size 8388608 > net_buffer_length 64512 > net_read_timeout 60 > net_retry_count 10 > net_write_timeout 60 > open_files_limit 0 > pid_file /var/run/mysqld/mysqld.pid > port 3306 > protocol_version 10 > record_buffer 131072 > record_rnd_buffer 131072 > query_buffer_size 0 > safe_show_database OFF > server_id 0 > slave_net_timeout 3600 > skip_locking ON > skip_networking OFF > skip_show_database OFF > slow_launch_time 2 > socket /var/run/mysqld/mysqld.sock > sort_buffer 2097144 > sql_mode 0 > table_cache 64 > table_type MYISAM > thread_cache_size 0 > thread_stack 131072 > transaction_isolation READ-COMMITTED > timezone CEST > tmp_table_size 33554432 > tmpdir /tmp/ > version 3.23.49-log > wait_timeout 600 > > Regards, > > Aegirfan > > --- In [EMAIL PROTECTED], "aegirfan2003" > <[EMAIL PROTECTED]> wrote: > > We want to implement Aegir, but we keep getting corrupt tables in > the > > database. This involves the 'repligard' table and different other > > tables each time. > > > > Does anybody recognise this problem? We haven't been able to > > reproduce it yet, it just occurs now and then. > > > > We use Aegir 1.0 RC2 and Midgard 1.4.3 with MySQL 3.23.55 and > Apache > > 1.3.27 on Debian Woody. > > > > We reported this on the Midgard Bug Tracker (ID=0000456) but no > reply > > so far. > > > > We like Aegir a lot, but if we don't solve this, then we will have > to > > look for an other CMS. > > > > > > ------------------------------------------------------------------ -- > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > -------------------------------------------------------------------- - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
