Bug #38076 rpl_drop mysqltest returned unexpected code 127
Submitted: 12 Jul 2008 19:36 Modified: 28 Jul 2010 12:03
Reporter: Andrei Elkin Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Tests: Replication Severity:S3 (Non-critical)
Version:5.1-bugteam OS:Any
Assigned to: Alfranio Tavares Correia Junior CPU Architecture:Any
Tags: pushbuild, sporadic, test failure

[12 Jul 2008 19:36] Andrei Elkin
Description:
        tfl_name: rpl.rpl_drop 'stmt'
    tfl_tst_type: ps_stm
        psh_tree: bzr_mysql-5.1-bugteam
       psh_order: 44
tfl_bld_platform: pb-valgrind
        tfl_text: rpl.rpl_drop 'stmt'            [ fail ]

ERROR: mysqltest returned unexpected code 127, it has probably crashed

nothing valuable has been found in error logs.

How to repeat:
https://intranet.mysql.com/secure/pushbuild/xref.pl?startdate=&enddate=&dir=&plat=pb-valgr...
https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-5.1-bugteam&order=44 bzr_mysql-5.1-bugteam/44pb-valgrind/ps_stm
[28 Jul 2010 11:27] Alfranio Tavares Correia Junior
The last two failures since December 2009 are

1 -
mysqltest: In included file "./include/master-slave.inc": At line 7: query 'connect  master1,127.0.0.1,root,,test,$MASTER_MYPORT,' failed: 2003: Can't connect to MySQL server on '127.0.0.1' (125)
Failed to read from '/export/home/pb2/test/sb_0-1881251-1276564796.2/mysql-5.5.5-m3-solaris10-sparc-64bit-test/mysql-test/var-ps_row/log/rpl_drop.log', errno: 22

2 - 
mysqltest failed but provided no output
The result from queries just before the failure was:
< snip >
stop slave;
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
reset master;
reset slave;
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
start slave;
drop table if exists t1, t2;
create table t1 (a int);
drop table t1, t2;
ERROR 42S02: Unknown table 't2'

------

In the latter, there is no information to track down the cause. In the former, apparently there is an environment problem because it is not possible to read
rpl_drop.log. The "read" operation fails with EINVAL (errno = 22).
[28 Jul 2010 11:52] Alfranio Tavares Correia Junior
The failures reported above happened at 2010-06-01 and 2010-03-26, respectively.
[28 Jul 2010 12:03] Alfranio Tavares Correia Junior
The apparently environment problem reported in 1 ([28 Jul 13:27] Alfranio Correia) seems to be related to BUG#48304, BUG#36967, BUG#49978.

So I am closing it as "can't repeat".