I don't actually see the error message in the output you sent. but I found a
similar problem yesterday and have the following work around:
===== myisamchk.c 1.69 vs edited =====
*** /tmp/myisamchk.c-1.69-20535 Thu Feb 7 17:21:33 2002
--- edited/myisamchk.c Sat Feb 9 22:48:57 2002
***************
*** 574,582 ****
check_param.testflag|= T_UPDATE_STATE;
break;
case '#':
! if (argument && *argument == '0')
DBUG_POP();
! else
DBUG_PUSH(argument ? argument : "d:t:o,/tmp/myisamchk.trace");
break;
case 'V':
--- 574,582 ----
check_param.testflag|= T_UPDATE_STATE;
break;
case '#':
! if (argument && *argument == '0') {
DBUG_POP();
! } else
DBUG_PUSH(argument ? argument : "d:t:o,/tmp/myisamchk.trace");
break;
case 'V':
Of course after applying this I ran into a different problem:
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
Which is apparently because it isn't asking the master for the correct file name:
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.00 sec)
which should be spode-bin.001
My guess is that I need an extra entry of some sort 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
But I'm nto sure what it should be. /var/lib/mysql/master.info looks OK:
spode-bin.001
251797980
db1.tias.com
slave
<password>
3306
60
0
075316828
Jeremy Zawodny wrote:
> On Sat, Feb 09, 2002 at 09:41:25PM -0700, Sasha Pachev wrote:
>
>>Dear MySQL users,
>>
>>I have just pushed my latest changes in the replication code in our
>>4.0 development tree, which change the slave to use two threads -
>>I/O thread that gets the data from the master and logs it, and SQL
>>thread which processes the logged data. I have tested it
>>extensively, and it has passed all of my tests. However, as we all
>>know, field testing tends to find nasty bugs that have not been
>>caught in regression tests and visual code examination.
>>
>
> Excellent. I'm ready to test...
>
>
>>Testing the new code is relatively easy, and does not require
>>risking the stability of your application by running alpha
>>code. Here is what you need to do:
>>
>>Find a machine that will act as a test server. With the availablity
>>of Linux and FreeBSD, this can be done cost-effectively by
>>sacrificing some useless dust-gathering PC in your office. In some
>>case, you may even try it with your own desktop.
>>
>
> Got it.
>
>
>>If you want to do it this very moment, read the instructions at
>>http://www.mysql.com/doc/I/n/Installing_source_tree.html and install
>>a pre-release 4.0.2 MySQL on your test server. You may also wait
>>until 4.0.2 is released, but in that case, replication in 4.0.2 may
>>have a bug you could have caught on your system and it will not be
>>fixed until 4.0.3.
>>
>
> I just updated my bitkeeper tree and have been having a hell of a time
> getting it to build. I've checked that I have automake 1.4 and
> autoconf 2.13.
>
> I run `BUILD/compile-pentium --prefix=/home/mysql` and it fails after
> several minutes. The output is large, so I've posted it here:
>
> http://public.yahoo.com/~jzawodn/mysql-build.log
>
> (the good stuff is at the end, of course...)
>
> I believe I've followed the directions properly, but let me know if it
> looks like I've missed anything.
>
> Thanks,
>
> Jeremy
>
---------------------------------------------------------------------
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
