Patrick, That error is documented in bug 811341. Joe's on it.
-- You received this bug notification because you are a member of UBUNTU - AL - BR, which is subscribed to Drizzle. https://bugs.launchpad.net/bugs/799269 Title: slave.basic test failing randomly on Natty with slave assertion on execute() - replication problem? Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications: Incomplete Status in Drizzle fremont series: Incomplete Bug description: The test slave.basic is failing for me, at least on Natty. This occurred when I updated my branch from trunk - not sure of the exact code / revision that is causing it, but these files were touched in update: modified client/drizzletest.cc modified drizzled/filesort.cc modified drizzled/join.cc modified drizzled/my_hash.cc modified drizzled/my_hash.h modified drizzled/sql_base.cc modified drizzled/sql_select.cc modified drizzled/sql_select.h modified drizzled/sql_table.cc modified drizzled/structs.h modified drizzled/table.cc modified drizzled/table_proto.cc modified drizzled/memory/multi_malloc.cc modified drizzled/memory/root.cc modified drizzled/plugin/storage_engine.cc modified libdrizzle-2.0/libdrizzle/column.cc modified libdrizzle-2.0/libdrizzle/conn.cc modified libdrizzle-2.0/libdrizzle/drizzle.cc modified libdrizzle-2.0/libdrizzle/field.cc modified libdrizzle-2.0/libdrizzle/query.cc modified libdrizzle-2.0/libdrizzle/result.cc modified libdrizzle-2.0/libdrizzle/row.cc modified plugin/auth_pam/auth_pam.cc modified plugin/memory/hp_block.cc failure output: fail ] 3052 20110618-175553 drizzletest: At line 14: query 'connect slave_con,127.0.0.1,root,,test, $BOT0_S1' failed: 21: drizzle_state_connect:could not connect 20110618-175553 20110618-175553 The result from queries just before the failure was: 20110618-175553 DROP TABLE IF EXISTS t1; 20110618-175553 Populating master server 20110618-175553 CREATE TABLE t1 (a int not null auto_increment, primary key(a)); 20110618-175553 INSERT INTO t1 VALUES (),(),(); 20110618-175553 SELECT * FROM t1; 20110618-175553 a 20110618-175553 1 20110618-175553 2 20110618-175553 3 20110618-175553 Connecting to slave... 20110618-175553 20110618-175553 More results from queries before failure can be found in drizzle/tests/workdir/bot0/s0/var/log/basic.log 20110618-175553 Log output: cat var/log/s1.err InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: 127 rollback segment(s) active. InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 110618 17:55:49 - drizzled got signal 6; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. read_buffer_size=131072 max_used_connections=1 connection_count=0 It is possible that drizzled could use up to (read_buffer_size + sort_buffer_size)*thread_count bytes of memory Hope that's ok; if not, decrease some variables in the equation. Number of stack frames obtained: 24 /home/pcrews/bzr/work/drizzle/drizzled/.libs/lt-drizzled() [0x6d1ec9] () gsignal() abort() () () cfree() std::string::assign(std::string const&) /home/pcrews/bzr/work/drizzle/drizzled/.libs/lt-drizzled() [0x5347d4] /home/pcrews/bzr/work/drizzle/drizzled/.libs/lt-drizzled() [0x57aa33] drizzled::Execute::run(std::string const&, drizzled::sql::ResultSet&) () () () () () () () () () thread_proxy() () clone() To manage notifications about this bug go to: https://bugs.launchpad.net/drizzle/+bug/799269/+subscriptions -- Mailing list: https://launchpad.net/~linux-traipu Post to : [email protected] Unsubscribe : https://launchpad.net/~linux-traipu More help : https://help.launchpad.net/ListHelp
