diff options
author | unknown <monty@narttu.mysql.fi> | 2003-06-05 17:33:38 +0300 |
---|---|---|
committer | unknown <monty@narttu.mysql.fi> | 2003-06-05 17:33:38 +0300 |
commit | 64d11bb395348ec002760d5354fbec0e373db593 (patch) | |
tree | 2f66999790d27b10bd1ddb8bdc47741a04c5c502 /sql/slave.cc | |
parent | ad5e39bf12b7aeefbc313e464a1349541a7b15c5 (diff) | |
parent | a3afb2bcbea96d4c5a326204151fb63cd0411aec (diff) | |
download | mariadb-git-64d11bb395348ec002760d5354fbec0e373db593.tar.gz |
Merge with 4.0.13
BitKeeper/deleted/.del-internals.texi~62b6f580a41c2a43:
Auto merged
innobase/os/os0file.c:
Auto merged
innobase/srv/srv0srv.c:
Auto merged
innobase/srv/srv0start.c:
Auto merged
mysql-test/r/func_str.result:
Auto merged
mysql-test/r/rpl_loaddata.result:
Auto merged
mysql-test/t/rpl_loaddata.test:
Auto merged
sql/handler.cc:
Auto merged
sql/item_strfunc.cc:
Auto merged
sql/net_serv.cc:
Auto merged
sql/slave.cc:
Auto merged
sql/sql_repl.cc:
Auto merged
support-files/mysql.spec.sh:
Auto merged
Diffstat (limited to 'sql/slave.cc')
-rw-r--r-- | sql/slave.cc | 11 |
1 files changed, 8 insertions, 3 deletions
diff --git a/sql/slave.cc b/sql/slave.cc index 4767245834a..cc27bb96ab7 100644 --- a/sql/slave.cc +++ b/sql/slave.cc @@ -287,7 +287,7 @@ int init_relay_log_pos(RELAY_LOG_INFO* rli,const char* log, goto err; rli->cur_log = &rli->cache_buf; } - if (pos > BIN_LOG_HEADER_SIZE) + if (pos >= BIN_LOG_HEADER_SIZE) my_b_seek(rli->cur_log,(off_t)pos); err: @@ -2154,8 +2154,13 @@ static int exec_relay_log_event(THD* thd, RELAY_LOG_INFO* rli) else { sql_print_error("\ -Could not parse log event entry, check the master for binlog corruption\n\ -This may also be a network problem, or just a bug in the master or slave code.\ +Could not parse relay log event entry. The possible reasons are: the master's \ +binary log is corrupted (you can check this by running 'mysqlbinlog' on the \ +binary log), the slave's relay log is corrupted (you can check this by running \ +'mysqlbinlog' on the relay log), a network problem, or a bug in the master's \ +or slave's MySQL code. If you want to check the master's binary log or slave's \ +relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' \ +on this slave.\ "); return 1; } |