[MDEV-400] Galera: debug server crashes with "debugger aborting because missing DBUG_RETURN or DBUG_VOID_RETURN macro in function "?func" Created: 2012-07-18  Updated: 2012-09-19  Resolved: 2012-09-19

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.5.28a-galera

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Seppo Jaakola
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates

 Description   

sql/mysqld: debugger aborting because missing DBUG_RETURN or DBUG_VOID_RETURN macro in function "?func"
 
#3  0x083e7298 in handle_fatal_signal (sig=6) at sql/signal_handler.cc:279
#4  <signal handler called>
#5  0xffffe430 in __kernel_vsyscall ()
#6  0xb75b67af in raise () from /lib/libc.so.6
#7  0xb75b80f0 in abort () from /lib/libc.so.6
#8  0x088beed1 in DbugExit (why=0xac33d024 "missing DBUG_RETURN or DBUG_VOID_RETURN macro in function \"?func\"\n")
    at dbug/dbug.c:1987
#9  0x088bdcd2 in _db_return_ (_line_=4788, _stack_frame_=0xac33d358) at dbug/dbug.c:1178
#10 0x081a0c87 in start_wsrep_THD (arg=0x8252773) at sql/mysqld.cc:4788
#11 0xb788eb25 in start_thread () from /lib/libpthread.so.0
#12 0xb765e38e in clone () from /lib/libc.so.6

It happens when I am trying to start a second node and it complains like this:

120718  6:29:30 [Note] WSREP: Shifting OPEN -> PRIMARY (TO: 0)
120718  6:29:30 [Note] WSREP: State transfer required: 
	Group state: 24d7c213-d077-11e1-0800-735beb8d9754:0
	Local state: 00000000-0000-0000-0000-000000000000:-1
120718  6:29:30 [Note] WSREP: New cluster view: global state: 24d7c213-d077-11e1-0800-735beb8d9754:0, view# 14: Primary, number of nodes: 2, my index: 1, protocol version 2
120718  6:29:30 [Warning] WSREP: Gap in state sequence. Need state transfer.
120718  6:29:32 [Note] WSREP: Running: 'wsrep_sst_rsync 'joiner' '192.168.1.4' '' '/home/elenst/galera-5.5/data/' '' '28324' 2>sst.err'
120718  6:29:32 [ERROR] WSREP: Failed to read 'ready <addr>' from: wsrep_sst_rsync 'joiner' '192.168.1.4' '' '/home/elenst/galera-5.5/data/' '' '28324' 2>sst.err
	Read: '(null)'
120718  6:29:32 [ERROR] WSREP: Process completed with error: wsrep_sst_rsync 'joiner' '192.168.1.4' '' '/home/elenst/galera-5.5/data/' '' '28324' 2>sst.err: 2 (No such file or directory)
120718  6:29:32 [ERROR] WSREP: Failed to prepare for 'rsync' SST. Unrecoverable.
120718  6:29:32 [ERROR] Aborting
 
120718  6:29:34 [Note] WSREP: Closing send monitor...
120718  6:29:34 [Note] WSREP: Closed send monitor.
120718  6:29:34 [Note] WSREP: gcomm: terminating thread
120718  6:29:34 [Note] WSREP: gcomm: joining thread
120718  6:29:34 [Note] WSREP: gcomm: closing backend
120718  6:29:34 [Note] WSREP: view(view_id(NON_PRIM,24d5e05e-d077-11e1-0800-c115641623bf,14) memb {
	66a4917d-d080-11e1-0800-06360442bf16,
} joined {
} left {
} partitioned {
	24d5e05e-d077-11e1-0800-c115641623bf,
})
120718  6:29:34 [Note] WSREP: New COMPONENT: primary = no, bootstrap = no, my_idx = 0, memb_num = 1
120718  6:29:34 [Note] WSREP: view((empty))
120718  6:29:34 [Note] WSREP: gcomm: closed
120718  6:29:34 [Note] WSREP: Flow-control interval: [8, 16]
120718  6:29:34 [Note] WSREP: Received NON-PRIMARY.
120718  6:29:34 [Note] WSREP: Shifting PRIMARY -> OPEN (TO: 0)
120718  6:29:34 [Note] WSREP: Received self-leave message.
120718  6:29:34 [Note] WSREP: Flow-control interval: [0, 0]
120718  6:29:34 [Note] WSREP: Received SELF-LEAVE. Closing connection.
120718  6:29:34 [Note] WSREP: Shifting OPEN -> CLOSED (TO: 0)
120718  6:29:34 [Note] WSREP: RECV thread exiting 0: Success
120718  6:29:34 [Note] WSREP: recv_thread() joined.
120718  6:29:34 [Note] WSREP: Closing slave action queue.
120718  6:29:34 [Note] WSREP: Service disconnected.
120718  6:29:34 [Note] WSREP: rollbacker thread exiting
sql/mysqld: debugger aborting because missing DBUG_RETURN or DBUG_VOID_RETURN macro in function "?func"

So far I have no problem reproducing it, because it always happens when I'm trying to start the 2nd node (still on my way of solving the problem)
If it turns out to be necessary, I will try to combine some kind of a test, but I suppose the issue should be easy to fix for those familiar with the code.



 Comments   
Comment by Daniel Bartholomew [ 2012-07-27 ]

On Fri, 27 Jul 2012 22:04:49 +0300
Michael Widenius <michael.widenius@gmail.com> wrote:

Monty>
Monty> Hi!
Monty>
Monty> >>>>> "Elena" == Elena Stepanova <(JIRA)"
Monty> >>>>> <jira@mariadb.atlassian.net>> writes:

Elena> [ https://mariadb.atlassian.net/browse/MDEV-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711#comment-12711 ]

Elena> Elena Stepanova commented on MDEV-400:
Elena> --------------------------------------
Elena>
Elena> Assigned to Monty only because it turns out I have no
Elena> idea who assign bugs on the galera tree to: LP doesn't
Elena> seem to accept bugs anymore, and JIRA doesn't find
Elena> Seppo.

Monty> Daniel, can you give Seppo write access to Jira.

I've looked and I don't think my JIRA user has user-admin rights,
because I don't see anywhere where I can add users or modify the rights
of existing users. I'm guessing I must be in the system as just a
regular user.

Rasmus: Can you give me rights?

Elena> I'm also not sure what to put in "fix versions",
Elena> probably we need to add galera to the list?

Monty> Yes, we should add galera to the list.

Thanks.


Daniel Bartholomew
Google+ - http://gplus.to/dbart
Twitter - http://twitter.com/daniel_bart

MariaDB: An Enhanced Drop-in Replacement for MySQL
Website - http://mariadb.org
Twitter - http://twitter.com/mariadb
Google+ - http://gplus.to/mariadb
Facebook - http://fb.com/MariaDB.dbms
Knowledgebase - http://kb.askmonty.org
Monty Program - http://montyprogram.com

Comment by Seppo Jaakola [ 2012-09-19 ]

Fix merged from upstream (https://bugs.launchpad.net/codership-mysql/+bug/1052668) in: http://bazaar.launchpad.net/~maria-captains/maria/maria-5.5-galera/revision/3353

Generated at Thu Feb 08 06:28:28 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.