Bug #25245 rpl_row_max_relay_size.test fails on sapsrv1 with warnings
Submitted: 22 Dec 2006 12:28 Modified: 3 Jul 2007 8:26
Reporter: Ingo Strüwing Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Replication Severity:S2 (Serious)
Version:5.1.15 OS:Any
Assigned to: Georgi Kodinov CPU Architecture:Any

[22 Dec 2006 12:28] Ingo Strüwing 
Description:
Quote from https://intranet.mysql.com/~knielsen/pb/getlog.pl?dir=mysql-5.1-engines&entry=istruewing@c...

WARNING:  'Attempting backtrace. You can use the following information to find out'
    COUNT: 1
    FILES:    slave.err
    TESTS:    rpl_row_max_relay_size

How to repeat:
See pushbuild log.
[31 Jan 2007 13:50] Alexander Barkov 
It seems to be a one-time accident failure.
Does not happen anymore.
[26 Jun 2007 9:03] Lars Thalmann 
Happened again.

Tree: mysql-5.1  (Main tree)
Main: Mon Jun 25 23:48:56 2007 ibabaev

This time running suite "ps_row" on "double whopper".

Slave crashes with following message:

safe_mutex: Trying to destroy a mutex that was locked at slave.cc, line 2453 at rpl_rli.cc, line 68
070626  3:53:41 - mysqld got signal 6;
[3 Jul 2007 8:26] Georgi Kodinov 
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicate of bug #27675
[3 Jul 2007 10:08] Ingo Strüwing 
Thank you very much for the indoctrination. But this bug was issued last year, while the other bug was issued this April. If at all, you could call the other bug a duplicate of this one and tell the other guy not to issue duplicates.