> mysql> show slave status\G;
> *************************** 1. row ***************************
>           Master_Host: hubble
>           Master_User: replica
>           Master_Port: 3306
>         Connect_retry: 60
>       Master_Log_File: hubble-bin.009
>   Read_Master_Log_Pos: 646906124
>        Relay_Log_File: gemini-relay-bin.008
>         Relay_Log_Pos: 1006270724
> Relay_Master_Log_File: hubble-bin.009
>      Slave_IO_Running: No
>     Slave_SQL_Running: No
>       Replicate_do_db:
>   Replicate_ignore_db:
>            Last_errno: 0
>            Last_error: error 'unexpected success or fatal error' on query 'INSERT 
> INTO COBGE7ÊA'
>          Skip_counter: 0
>   Exec_master_log_pos: 646905758
>       Relay_log_space: 1006271180
> 1 row in set (0.01 sec)
>   



On Fri, 2004-11-05 at 14:37 -0800, Max Michaels wrote:

> Please run the command as 'show slave status\G' and send those results. Makes it 
> much, much easier to read :)
> 
> 
> -----Original Message-----
> From: Alvaro Avello [mailto:[EMAIL PROTECTED] 
> Sent: Friday, November 05, 2004 3:36 PM
> To: [EMAIL PROTECTED]
> Subject: replication log error
> 
> Hi. 
> I'm having a problem with a slave replication server. the 'show slave
> status'  command shows :
> 
> mysql> show slave status;
> +-------------+-------------+-------------+---------------+-----------------+---------------------+----------------------+---------------+-----------------------+------------------+-------------------+-----------------+---------------------+------------+------------------------------------------------------------------------------+--------------+---------------------+-----------------+
> | Master_Host | Master_User | Master_Port | Connect_retry |
> Master_Log_File | Read_Master_Log_Pos | Relay_Log_File       |
> Relay_Log_Pos | Relay_Master_Log_File | Slave_IO_Running |
> Slave_SQL_Running | Replicate_do_db | Replicate_ignore_db | Last_errno |
> Last_error                     | Skip_counter | Exec_master_log_pos |
> Relay_log_space |
> +-------------+-------------+-------------+---------------+-----------------+---------------------+----------------------+---------------+-----------------------+------------------+-------------------+-----------------+---------------------+------------+------------------------------------------------------------------------------+--------------+---------------------+-----------------+
> | hubble      | replica     | 3306        | 60            |
> hubble-bin.009  | 646906124           | gemini-relay-bin.008 |
> 1006270724    | hubble-bin.009      | No               | No
> |                 |                     | 0          | error 'unexpected
> success or fatal error' on query 'INSERT INTO COBGE7ÊA' | 0
> | 646905758           | 1006271180      |
> +-------------+-------------+-------------+---------------+-----------------+---------------------+----------------------+---------------+-----------------------+------------------+-------------------+-----------------+---------------------+------------+------------------------------------------------------------------------------+--------------+---------------------+-----------------+
> 1 row in set (0.00 sec)
>  
> the query shows a table that don't exists ( COBGE7ÊA ) , so what I
> thought is that the relay log was corrupt. I'm trying to read the log
> with mysqlbinlog  : 
> 
>  mysqlbinlog -f gemini-relay-bin.008 > nuevo.sql 
> 
> and got :
> 
> ERROR: Error in Log_event::read_log_event(): 'Event too small',
> data_len=0,event_type=0
> ERROR: Could not read entry at offset 909811060 : Error in log format or
> read error
> 
> 
>  Could i skip the lines before the infamous offset number or  something
> else...? 
> 
> Thanks in advance and have a good weekend.....

-- 
Alvaro Avello <[EMAIL PROTECTED]>
Servinco S.A.

Reply via email to