Node1 crashed in 3 node cluster (WSREP: unserialize error invalid protocol version 2: 71 (Protocol error))

3,135 views
Skip to first unread message

Amol

unread,
Apr 14, 2013, 5:14:52 PM4/14/13
to percona-d...@googlegroups.com
130414 16:03:18 [Warning] WSREP: unserialize error invalid protocol version 2: 71 (Protocol error)
         at gcomm/src/gcomm/datagram.hpp:unserialize():108
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<asio::system_error> >'
  what():  Transport endpoint is not connected
20:10:42 UTC - mysqld 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.
Please help us make Percona Server better by reporting any

here is my Percona software version

$ sudo dpkg --list percona*
||/ Name                                           Version                                        Description
+++-==============================================-==============================================-
ii  percona-toolkit                                2.1.8                                          Advanced MySQL and system command-line tools
ii  percona-xtrabackup                             2.0.5-499.lucid                                Open source backup tool for InnoDB and XtraDB
ii  percona-xtradb-cluster-client-5.5              5.5.29-23.7.1-387.lucid                        Percona Server database client binaries
ii  percona-xtradb-cluster-common-5.5              5.5.29-23.7.1-387.lucid                        Percona Server database common files (e.g. /etc/mysql/my.cnf)
ii  percona-xtradb-cluster-galera-2.x              143.lucid                                      Galera components of Percona XtraDB Cluster
ii  percona-xtradb-cluster-server-5.5              5.5.29-23.7.1-387.lucid                        Percona Server database server binaries


No iptables rules or configurations have changed recently, so i wasn't sure what sort of error this was??

Amol

unread,
Apr 15, 2013, 11:30:39 AM4/15/13
to percona-d...@googlegroups.com
we later found out that it was this software 

that was causing this error, we were trying to run some portscans which probably broke the communication on cluster, need to see which action that could have been

Amol

unread,
Apr 15, 2013, 11:44:14 AM4/15/13
to percona-d...@googlegroups.com
here is the full stack trace

130414 16:03:18 [Warning] WSREP: unserialize error invalid protocol version 2: 71 (Protocol error)
         at gcomm/src/gcomm/datagram.hpp:unserialize():108
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<asio::system_error> >'
  what():  Transport endpoint is not connected
20:10:42 UTC - mysqld 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.
Please help us make Percona Server better by reporting any

key_buffer_size=67108864
read_buffer_size=131072
max_used_connections=32
max_threads=151
thread_count=13
connection_count=13
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 396021 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7f44f5]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x6bd2b4]
/lib/libpthread.so.0(+0xf8f0)[0x7f4f8389b8f0]
/lib/libc.so.6(gsignal+0x35)[0x7f4f82a72a75]
/lib/libc.so.6(abort+0x180)[0x7f4f82a765c0]
/usr/lib/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x115)[0x7f4f7fb9e8e5]
/usr/lib/libstdc++.so.6(+0xcad16)[0x7f4f7fb9cd16]
/usr/lib/libstdc++.so.6(+0xcad43)[0x7f4f7fb9cd43]
/usr/lib/libstdc++.so.6(+0xcae3e)[0x7f4f7fb9ce3e]
/usr/lib64/libgalera_smm.so(_ZN5boost15throw_exceptionIN4asio12system_errorEEEvRKT_+0x18a)[0x7f4f8050608a]
/usr/lib64/libgalera_smm.so(_ZNK4asio12basic_socketINS_2ip3tcpENS_21stream_socket_serviceIS2_EEE15remote_endpointEv+0x1fe)[0x7f4f8050c32e]
/usr/lib64/libgalera_smm.so(_ZN5gcomm13AsioTcpSocket18assign_remote_addrEv+0x627)[0x7f4f804f3637]
/usr/lib64/libgalera_smm.so(_ZN5gcomm15AsioTcpAcceptor14accept_handlerEN5boost10shared_ptrINS_6SocketEEERKN4asio10error_codeE+0xf3)[0x7f4f804f4283]
/usr/lib64/libgalera_smm.so(_ZN4asio6detail25reactive_socket_accept_opINS_12basic_socketINS_2ip3tcpENS_21stream_socket_serviceIS4_EEEES4_N5boost3_bi6bind_tIvNS8_4_mfi3mf2IvN5gcomm15AsioTcpAcceptorENS8_10shared_ptrINSD_6SocketEEERKNS_10error_codeEEENS9_5list3INS9_5valueIPSE_EENSN_ISH_EEPFNS8_3argILi1EEEvEEEEEE11do_completeEPNS0_15task_io_serviceEPNS0_25task_io_service_operationESI_m+0x180)[0x7f4f804fa2a0]
/usr/lib64/libgalera_smm.so(_ZN4asio6detail15task_io_service3runERNS_10error_codeE+0x431)[0x7f4f805200f1]
/usr/lib64/libgalera_smm.so(_ZN5gcomm12AsioProtonet10event_loopERKN2gu8datetime6PeriodE+0x1d6)[0x7f4f80515df6]
/usr/lib64/libgalera_smm.so(_ZN9GCommConn3runEv+0x67)[0x7f4f80533087]
/usr/lib64/libgalera_smm.so(_ZN9GCommConn6run_fnEPv+0x9)[0x7f4f80538529]
/lib/libpthread.so.0(+0x69ca)[0x7f4f838929ca]
/lib/libc.so.6(clone+0x6d)[0x7f4f82b25cdd]
You may download the Percona Server operations manual by visiting
in the manual which will help you identify the cause of the crash.
130414 16:10:42 mysqld_safe Number of processes running now: 0
130414 16:10:42 mysqld_safe WSREP: not restarting wsrep node automatically
130414 16:10:42 mysqld_safe mysqld from pid file /var/lib/mysql/load-db-node1.pid ended


On Monday, April 15, 2013 11:39:20 AM UTC-4, teemu ollakka wrote:

Hi,

Could you post full stack trace from logs anyway, this exception is probably not caught properly which causes node to crash.

- Teemu
Reply all
Reply to author
Forward
0 new messages