Public bug reported: Running mydumper causes:
root@mysql:/home/supervisor# mydumper -B gitlabhq_production ** (mydumper:15451): CRITICAL **: Failed to connect to database: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) root@mysql:/home/supervisor# MySQL error log: 2014-08-25 18:29:54 1438 [Note] WSREP: Provider paused at 87720985-2c49-11e4-948d-4a356f963e28:270 (3) 15:29:54 UTC - mysqld got signal 11 ; 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 XtraDB Cluster better by reporting any bugs at https://bugs.launchpad.net/percona-xtradb-cluster key_buffer_size=33554432 read_buffer_size=131072 max_used_connections=1 max_threads=202 thread_count=3 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 113385 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f96bd469a40 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 = 7f9684079e00 thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x7f96bb22b04c] /usr/sbin/mysqld(handle_fatal_signal+0x3cb)[0x7f96baf71a2b] /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f96b941c340] /usr/sbin/mysqld(+0x6e4cd7)[0x7f96bb1d5cd7] /usr/sbin/mysqld(+0x3a8a5a)[0x7f96bae99a5a] /usr/sbin/mysqld(_Z24plugin_foreach_with_maskP3THDPFcS0_P13st_plugin_intPvEijS3_+0x1dd)[0x7f96bb015b8d] /usr/sbin/mysqld(_Z28ha_start_consistent_snapshotP3THD+0x281)[0x7f96bae9ea51] /usr/sbin/mysqld(_Z11trans_beginP3THDj+0x100)[0x7f96bb09c910] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x2b9b)[0x7f96bb0050fb] /usr/sbin/mysqld(+0x519ee8)[0x7f96bb00aee8] /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1280)[0x7f96bb00c680] /usr/sbin/mysqld(_Z10do_commandP3THD+0x16c)[0x7f96bb00e8fc] /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x31d)[0x7f96bafcfd3d] /usr/sbin/mysqld(handle_one_connection+0x40)[0x7f96bafcfde0] /usr/sbin/mysqld(pfs_spawn_thread+0x140)[0x7f96bb4a3fb0] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f96b9414182] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f96b892138d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7f9644014460): is an invalid pointer Connection ID (thread ID): 8 Status: NOT_KILLED You may download the Percona XtraDB Cluster operations manual by visiting http://www.percona.com/software/percona-xtradb-cluster/. You may find information in the manual which will help you identify the cause of the crash. 140825 18:29:54 mysqld_safe Number of processes running now: 0 140825 18:29:54 mysqld_safe WSREP: not restarting wsrep node automatically 140825 18:29:54 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended The same issue repeats on all nodes, so it's unlikely a hardware issue. Configuration: [client] port = 3306 socket = /var/run/mysqld/mysqld.sock [mysqld_safe] socket = /var/run/mysqld/mysqld.sock nice = 0 [mysqld] user = mysql pid-file = /var/run/mysqld/mysqld.pid socket = /var/run/mysqld/mysqld.sock port = 3306 basedir = /usr datadir = /var/lib/mysql tmpdir = /tmp lc-messages-dir = /usr/share/mysql skip-external-locking key_buffer = 32M max_allowed_packet = 32M myisam-recover = BACKUP query_cache_limit = 1M log_error = /var/log/mysql/error.log character-set-server=utf8 collation-server=utf8_general_ci key-buffer-size = 32M myisam-recover = FORCE,BACKUP default-storage-engine = InnoDB max-allowed-packet = 16M max-connect-errors = 100000 skip-name-resolve innodb = FORCE innodb-strict-mode = 1 tmp-table-size = 32M max-heap-table-size = 32M query-cache-type = 0 query-cache-size = 0 max-connections = 200 open-files-limit = 65535 table-definition-cache = 4096 table-open-cache = 1000 innodb-flush-method = O_DIRECT innodb-log-files-in-group = 2 innodb-log-file-size = 512M innodb-flush-log-at-trx-commit = 1 innodb-file-per-table = 1 innodb-buffer-pool-size = 300M binlog_format = ROW ignore-db-dir = lost+found #wsrep_cluster_address=gcomm:// wsrep_cluster_address=gcomm://192.168.100.130,192.168.100.131,192.168.100.132 wsrep_provider=/usr/lib/galera3/libgalera_smm.so wsrep_sst_method=xtrabackup-v2 wsrep_cluster_name=asfasf wsrep_sst_auth="sadflkjsaf:ASdfsadfads" [mysqldump] quick quote-names max_allowed_packet = 16M [isamchk] key_buffer = 16M ** Affects: percona-xtradb-cluster Importance: Undecided Status: New ** Affects: mydumper (Ubuntu) Importance: Undecided Status: New ** Also affects: mydumper (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361265 Title: mydumper crashes Percona XtraDB Cluster To manage notifications about this bug go to: https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1361265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
