On Sunday 10 February 2002 01:17 am, you wrote:
> I can't get it to start replicating.
> 
> Note, the master (db1.tias.com) is a 3.23 server. The slave is 4.0.2 
> (noritake.tias.com).
> 
> On the master I get:
> 
> mysql> show master status;
> +---------------+------------+--------------+------------------+
> | File ? ? ? ? ?| Position ? | Binlog_do_db | Binlog_ignore_db |
> +---------------+------------+--------------+------------------+
> | spode-bin.020 | 1058168617 | ? ? ? ? ? ? ?| ? ? ? ? ? ? ? ? ?|
> +---------------+------------+--------------+------------------+
> 1 row in set (0.00 sec)
> 
> 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 |
> 
+-------------+-------------+-------------+---------------+-----------------+---------------------+------------------------+---------------+-----------------------+------------------+-------------------+-----------------+---------------------+------------+------------+--------------+---------------------+
> | ? ? ? ? ? ? | ? ? ? ? ? ? | 0 ? ? ? ? ? | 0 ? ? ? ? ? ? | ? ? ? ? ? ? ? ? 
| 0 
> ? ? ? ? ? ? ? ? ? ?| noritake-relay-bin.001 | 4 ? ? ? ? ? ? | 
> ? ? ?| No ? ? ? ? ? ? ? | No ? ? ? ? ? ? ? ?| ? ? ? ? ? ? ? ? | 
> ? ? ?| 0 ? ? ? ? ?| ? ? ? ? ? ?| 0 ? ? ? ? ? ?| 0 ? ? ? ? ? ? ? ? ? |
> 
+-------------+-------------+-------------+---------------+-----------------+---------------------+------------------------+---------------+-----------------------+------------------+-------------------+-----------------+---------------------+------------+------------+--------------+---------------------+
> 1 row in set (0.01 sec)
> 
> and in noritake.tias.com.err:
> 
> 020210 00:07:21 ?mysqld started
> 020210 ?0:07:21 ?Could not find first log during relay log initialization
> 020210 ?0:07:21 ?Warning: Can't create threads to handle slave
> /usr/local/libexec/mysqld: ready for connections
> 
> and in /etc/my.cnf on the slave:
> 
> [mysqld]
> replicate-ignore-table=curioscape.avstemp
> replicate-ignore-table=tias.avtemp
> replicate-ignore-table=inventory.availableQuantity
> replicate-ignore-table=inventory.thisItem
> replicate-ignore-table=inventory.auctionStatus
> replicate-ignore-table=inventory.itemTable
> master-host=db1.tias.com
> master-user=slave
> master-password=<password>
> log=db.log
> # master-port=
> server-id=2
> 
> and on the server:
> 
> [mysqld]
> set-variable = tmp_table_size=8M
> set-variable = key_buffer=384M
> set-variable = max_allowed_packet=2M
> set-variable = max_connections=1024
> set-variable = table_cache=8192
> set-variable = thread_cache_size=32
> set-variable = sort_buffer=4M
> set-variable = record_buffer=2M
> log-slow-queries
> log-bin
> server-id=1
> 
> It appears the problem is that the new replication code is using a 
different 
> file name convention?
> 
> This set up did work before. Until the 4.0.1 MySQL starting crashing 
because of 
> a fulltext index bug that I reported earlier.

Mike:

Thanks for reporting the bug. To troubleshoot it, lets do the following:

in slave.cc around line 186, you find the following code:

 if (rli->relay_log.find_first_log(&rli->linfo,log))
  {
    *errmsg="Could not find first log during relay log initialization";
    goto err;
  }

make it:

 if (rli->relay_log.find_first_log(&rli->linfo,log))
  {
    sql_print_error("Could not find first log during relay initialization");
    abort();
    *errmsg="Could not find first log during relay log initialization";
    goto err;
  }

and then run BUILD/compile-pentium-debug and install the new binary.

It will coredump when it hits the error. You will find a core file ( 
core.<pid_of_mysql>) in your datadir. FTP the core file to 
support.mysql.com/pub/mysql/secret along with your binary and a readme file 
all in a tar archive.

Thanks again for your efforts to help us make MySQL 4.0 more stable.

-- 
MySQL Development Team
For technical support contracts, visit https://order.mysql.com/
   __  ___     ___ ____  __ 
  /  |/  /_ __/ __/ __ \/ /   Sasha Pachev <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, http://www.mysql.com/
/_/  /_/\_, /___/\___\_\___/  Provo, Utah, USA
       <___/                  

---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to