Skip navigation links

MySQL Forums :: Replication :: [Warning] Slave SQL: Could not execute Query event. Detailed error: ;, Error_code: 0


Advanced Search

[Warning] Slave SQL: Could not execute Query event. Detailed error: ;, Error_code: 0
Posted by: Erik Hoekstra ()
Date: February 19, 2013 02:54AM

On a multi master setup with 5.6.10 (rhel6) the logs fillup with this message (when using log_warnings 2). I haven't reported this as a bug yet since i'm not fully sure this isn't a setup problem...

2013-02-19 09:38:51 13051 [Warning] Slave SQL: Could not execute Query event. Detailed error: ;, Error_code: 0
2013-02-19 09:38:51 13051 [Warning] Slave SQL: Could not execute Query event. Detailed error: ;, Error_code: 0
2013-02-19 09:38:51 13051 [Warning] Slave SQL: Could not execute Query event. Detailed error: ;, Error_code: 0
2013-02-19 09:38:51 13051 [Warning] Slave SQL: Could not execute Query event. Detailed error: ;, Error_code: 0
2013-02-19 09:38:51 13051 [Warning] Slave SQL: Could not execute Query event. Detailed error: ;, Error_code: 0
2013-02-19 09:38:51 13051 [Warning] Slave SQL: Could not execute Query event. Detailed error: ;, Error_code: 0
2013-02-19 09:38:52 13051 [Warning] Slave SQL: Could not execute Query event. Detailed error: ;, Error_code: 0
2013-02-19 09:38:52 13051 [Warning] Slave SQL: Could not execute Query event. Detailed error: ;, Error_code: 0
2013-02-19 09:38:52 13051 [Warning] Slave SQL: Could not execute Query event. Detailed error: ;, Error_code: 0
2013-02-19 09:38:52 13051 [Warning] Slave SQL: Could not execute Query event. Detailed error: ;, Error_code: 0

----


Here some cnf info

[MYSQL]
skip-auto-rehash
default-character-set = utf8
reconnect

[MYSQLD]
server-id=11
secure-auth = true

skip-name-resolve
skip-external-locking
ignore-builtin-innodb
default-storage-engine = myisam
event_scheduler = disabled
explicit_defaults_for_timestamp = true
performance_schema = off

general-log = 0
log-output = file
log-error = /var/lib/mysql/X.err
log-bin = /var/lib/mysql/X-bin
relay-log = /var/lib/mysql/X-relay-bin
log-warnings = 2

auto_increment_increment = 2
auto_increment_offset = 1

slave-skip-errors = all
slave_exec_mode = idempotent
slave_parallel_workers = 3
gtid_mode = off

character-set-server = utf8
collation-server = utf8_unicode_ci

expire_logs_days = 4
log-slave-updates

binlog-format = row
binlog_row_image = minimal

binlog-ignore-db = mysql
replicate-ignore-db = mysql
replicate-wild-ignore-table = mysql.%

binlog-ignore-db = information_schema
replicate-ignore-db = information_schema
replicate-wild-ignore-table = information_schema.%

binlog-ignore-db = performance_schema
replicate-ignore-db = preformance_schema
replicate-wild-ignore-table = performance_schema.%

binlog-ignore-db = X_raw
replicate-ignore-db = X_raw
replicate-wild-ignore-table = X_raw.%

replicate-wild-ignore-table = %_raw.%



query_prealloc_size = 16M
max_prepared_stmt_count = 32000

query_cache_type = 1
query_cache_size = 512M
query_cache_limit = 4M

key_buffer_size = 1536

delayed_insert_limit = 1500
delayed_queue_size = 3000

table_open_cache = 800
table_definition_cache = 600

group_concat_max_len = 2048

bulk_insert_buffer_size = 12M
read_buffer_size = 256k
read_rnd_buffer_size = 384k

thread_cache_size = 254

max_connections = 1024
max_user_connections = 1024
max_connect_errors = 1000000
max_allowed_packet = 32M

connect_timeout = 25
wait_timeout = 180
interactive_timeout = 180
net_read_timeout = 60
net_write_timeout = 80


----


My thought are this could be a message about a query/row not to replica on a slave due to replication rules? But then the message should be a notice right?

Options: ReplyQuote


Subject Views Written By Posted
[Warning] Slave SQL: Could not execute Query event. Detailed error: ;, Error_code: 0 1670 Erik Hoekstra 02/19/2013 02:54AM
Re: [Warning] Slave SQL: Could not execute Query event. Detailed error: ;, Error_code: 0 588 Erik Hoekstra 02/19/2013 06:54AM
Re: [Warning] Slave SQL: Could not execute Query event. Detailed error: ;, Error_code: 0 426 Rick James 02/24/2013 05:00PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.