Date: Sun, 15 Feb 2015 18:53:40 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 196399] databases/mariadb100-server: MariaDB daemon segfaults when built with clang 3.4 on 10.1-i386 Message-ID: <bug-196399-13-6nxbykzjih@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-196399-13@https.bugs.freebsd.org/bugzilla/> References: <bug-196399-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196399 Dimitry Andric <dim@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dim@FreeBSD.org --- Comment #5 from Dimitry Andric <dim@FreeBSD.org> --- This is most likely not related to bug 197389. It also dies when built on a freshly built current, using clang 3.6.0rc3: $ sudo /usr/local/etc/rc.d/mysql-server onestart Installing MariaDB/MySQL system tables in '/var/db/mysql' ... 150215 19:50:44 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150215 19:50:44 [Note] InnoDB: The InnoDB memory heap is disabled 150215 19:50:44 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 150215 19:50:44 [Note] InnoDB: Memory barrier is not used 150215 19:50:44 [Note] InnoDB: Compressed tables use zlib 1.2.8 150215 19:50:44 [Note] InnoDB: Not using CPU crc32 instructions 150215 19:50:44 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150215 19:50:44 [Note] InnoDB: Completed initialization of buffer pool 150215 19:50:44 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created! 150215 19:50:44 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB 150215 19:50:44 [Note] InnoDB: Database physically writes the file full: wait... 150215 19:50:44 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB 150215 19:50:44 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB 150215 19:50:45 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 150215 19:50:45 [Warning] InnoDB: New log files created, LSN=45781 150215 19:50:45 [Note] InnoDB: Doublewrite buffer not found: creating new 150215 19:50:45 [Note] InnoDB: Doublewrite buffer created 150215 19:50:45 [Note] InnoDB: 128 rollback segment(s) are active. 150215 19:50:45 [Warning] InnoDB: Creating foreign key constraint system tables. 150215 19:50:45 [Note] InnoDB: Foreign key constraint system tables created 150215 19:50:45 [Note] InnoDB: Creating tablespace and datafile system tables. 150215 19:50:45 [Note] InnoDB: Tablespace and datafile system tables created. 150215 19:50:45 [Note] InnoDB: Waiting for purge to start 150215 19:50:45 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.22-71.0 started; log sequence number 0 150215 19:50:45 [ERROR] 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. To report this bug, see http://kb.askmonty.org/en/reporting-bugs 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. Server version: 10.0.16-MariaDB key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=0 max_threads=153 thread_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466005 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x3b7c1008 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 = 0xba69ef68 thread_stack 0x48000 Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): is an invalid pointer Connection ID (thread ID): 1 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. Installation of system tables failed! Examine the logs in /var/db/mysql for more information. The problem could be conflicting information in an external my.cnf files. You can ignore these by doing: shell> /usr/local/scripts/scripts/mysql_install_db --defaults-file=~/.my.cnf You can also try to start the mysqld daemon with: shell> /usr/local/libexec/mysqld --skip-grant --general-log & and use the command line tool /usr/local/bin/mysql to connect to the mysql database and look at the grant tables: shell> /usr/local/bin/mysql -u root mysql mysql> show tables; Try 'mysqld --help' if you have problems with paths. Using --general-log gives you a log in /var/db/mysql that may be helpful. The latest information about mysql_install_db is available at https://mariadb.com/kb/en/installing-system-tables-mysql_install_db MariaDB is hosted on launchpad; You can find the latest source and email lists at http://launchpad.net/maria Please check all of the above before submitting a bug report at http://mariadb.org/jira /usr/local/etc/rc.d/mysql-server: WARNING: failed precmd routine for mysql Can somebody tell me how to run *just* the mysqld executable under gdb, so I can get a reliable backtrace, instead of relying on the built-in one that doesn't seem to work? -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-196399-13-6nxbykzjih>