Help with MySQL server message...

My forum is 3.5.4 on ipowerweb. When I moved to a new server about 3-4 months ago, (thanks to Heather from this site!) the board ran fine.

Now, members are getting error messages like "cannot connect to page" and here is the error I get sent to my email: (edited to say that the error is not ALL the time, just say 50% of the time)... My members are leaving left and right).

Database error in vBulletin 3.5.4:

Invalid SQL:

UPDATE datastore SET
data = data - 1,
data = IF(data < 0, 0, data)
WHERE title = 'mailqueue';

MySQL Error : MySQL server has gone away
Error Number : 2006

Can someone help me fix this? I am holding for ipower as we speak, but they are experiencing "high call volume" WONDER WHY!!!

[Delphiprogrammi]

hi,

read this this is a known error message

this may also become helpfull

[kellyandmike]

Oh my Gosh, that is SOOOO over my head. Can you help me determine which reason it is or at least which query to run to find out? I know how to run queries on mySql

[Delphiprogrammi]

hi,

best you could do is to get in touch with your host as you will be unable to correct this error if you are on a shared host.If you have a dedicated server you could try to edit the MySQL configuration file (/etc/my.cnf) or (my.ini on windows) and that might help.I don't know ipowerweb never dealed with them but it looks like there MySQL is crappy

[Marco van Herwaarden]

see Lost connection to MySQL server during query

[kellyandmike]

Well, much to my dismay, ipower tech didn't seem to know what to do. I think a 10 yr old would have known more. I sent an email to support, so we will see if they help. This is completely frustrating. And, I am NOT on a dedicated server.

[Farcaster]

When this error comes up is it usually the same? Based on the SQL being executed, it looks like vB is doing something with the mail queue. Perhaps the connection is being closed because sending mail is taking too long? You may want to try disable mail features (under "Email Options") or try reducing the number of emails sent in a batch.

That is, of course, a wild guess, but it might be worth trying.

[kellyandmike]

Farcaster,
It seems to have worked somewhat. I still get the error but not as much. I will post tomorrow AM when my members respond if it is better for them.

[Paul M]

In the ACP goto Maintenance > Diagnostics and run the System Information for MySQL variables. Right at the bottom you will find wait_timeout, what is it set to ?

[kellyandmike]

120

The whole chart is below...

Help MySQL Variables
Variable_name Value
back_log 50
basedir /usr/local/mysql/
binlog_cache_size 32768
bulk_insert_buffer_size 8388608
character_set latin1
character_sets latin1 dec8 dos german1 hp8 koi8_ru latin2 swe7 usa7 cp1251 danish hebrew win1251 estonia hungarian koi8_ukr win1251ukr greek win1250 croat cp1257 latin5
concurrent_insert ON
connect_timeout 5
convert_character_set
datadir /usr/local/mysql/var/
default_week_format 0
delay_key_write ON
delayed_insert_limit 100
delayed_insert_timeout 300
delayed_queue_size 1000
flush OFF
flush_time 0
ft_boolean_syntax + -><()~*:""&|
ft_min_word_len 4
ft_max_word_len 254
ft_max_word_len_for_sort 20
ft_stopword_file (built-in)
have_bdb NO
have_crypt YES
have_innodb DISABLED
have_isam YES
have_raid YES
have_symlink NO
have_openssl NO
have_query_cache YES
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 1
innodb_fast_shutdown ON
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
innodb_max_dirty_pages_pct 90
interactive_timeout 120
join_buffer_size 131072
key_buffer_size 268435456
language /usr/local/mysql/share/mysql/english/
large_files_support ON
local_infile ON
log OFF
log_update OFF
log_bin OFF
log_slave_updates OFF
log_slow_queries OFF
log_warnings OFF
long_query_time 10
low_priority_updates OFF
lower_case_table_names OFF
max_allowed_packet 2096128
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_relay_log_size 0
max_seeks_for_key 4294967295
max_sort_length 1024
max_user_connections 0
max_tmp_tables 32
max_write_lock_count 4294967295
myisam_max_extra_sort_file_size 268435456
myisam_max_sort_file_size 2147483647
myisam_repair_threads 1
myisam_recover_options OFF
myisam_sort_buffer_size 67108864
net_buffer_length 16384
net_read_timeout 30
net_retry_count 1000000
net_write_timeout 60
new OFF
open_files_limit 16384
pid_file /usr/local/mysql/var/host456.ipowerweb.com.pid
log_error
port 3306
protocol_version 10
query_alloc_block_size 8192
query_cache_limit 4194304
query_cache_size 67108864
query_cache_type ON
query_prealloc_size 8192
range_alloc_block_size 2048
read_buffer_size 2093056
read_only OFF
read_rnd_buffer_size 4190208
rpl_recovery_rank 0
server_id 1
slave_net_timeout 3600
skip_external_locking ON
skip_networking OFF
skip_show_database OFF
slow_launch_time 2
socket /tmp/mysql.sock
sort_buffer_size 4194296
sql_mode 0
table_cache 512
table_type MYISAM
thread_cache_size 8
thread_stack 196608
tx_isolation REPEATABLE-READ
timezone PDT
tmp_table_size 33554432
tmpdir /var/tmp/
transaction_alloc_block_size 8192
transaction_prealloc_size 4096
version 4.0.16
wait_timeout 120