fossable / sandpolis

Ultimate virtual estate monitoring and management!

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Fix MariaDB error

cilki opened this issue · comments

The following failure happens occasionally on MacOS:

ch.vorburger.exec.ManagedProcessException: An error occurred while installing the database
        at ch.vorburger.mariadb4j.DB.install(DB.java:134)
        at ch.vorburger.mariadb4j.DB.newEmbeddedDB(DB.java:81)
        at ch.vorburger.mariadb4j.DB.newEmbeddedDB(DB.java:97)
        at com.sandpolis.core.storage.ormlite.OrmliteStoreProviderTest.setup(OrmliteStoreProviderTest.java:314)
        Caused by:
        ch.vorburger.exec.ManagedProcessException: Program [/var/folders/nz/vv4_9tw56nv9k3tkvyszvwg80000gn/T/MariaDB4j/base/bin/mysql_install_db, --datadir=/private/var/folders/nz/vv4_9tw56nv9k3tkvyszvwg80000gn/T/MariaDB4j/data/8001, --basedir=/private/var/folders/nz/vv4_9tw56nv9k3tkvyszvwg80000gn/T/MariaDB4j/base, --no-defaults, --force, --skip-name-resolve] (in working directory /var/folders/nz/vv4_9tw56nv9k3tkvyszvwg80000gn/T/MariaDB4j/base) failed, exitValue=1, last 100 lines of console:
        Installing MariaDB/MySQL system tables in '/private/var/folders/nz/vv4_9tw56nv9k3tkvyszvwg80000gn/T/MariaDB4j/data/8001' ...
        190501 11:46:47 [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 https://mariadb.com/kb/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.2.11-MariaDB
        key_buffer_size=134217728
        read_buffer_size=131072
        max_used_connections=0
        max_threads=153
        thread_count=0
        It is possible that mysqld could use up to 
        key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467247 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 = 0x0 thread_stack 0x49000
        0   mysqld                              0x00000001093f7a98 my_print_stacktrace + 60
        0   mysqld                              0x0000000108e42ad9 handle_fatal_signal + 695
        0   libsystem_platform.dylib            0x00007fff7c164f5a _sigtramp + 26
        0   ???                                 0x000000010d509650 0x0 + 4518352464
        0   libsystem_pthread.dylib             0x00007fff7c16d167 pthread_cond_broadcast + 540
        0   mysqld                              0x00000001092130e7 _ZL12innobase_endP10handlerton17ha_panic_function + 167
        0   mysqld                              0x0000000108e435a2 _Z22ha_finalize_handlertonP13st_plugin_int + 71
        0   mysqld                              0x0000000108fe1116 _ZL19plugin_deinitializeP13st_plugin_intb + 142
        0   mysqld                              0x0000000108fdfa2a _ZL12reap_pluginsv + 282
        0   mysqld                              0x0000000108fe1388 _Z15plugin_shutdownv + 177
        0   mysqld                              0x0000000108f13fe2 _ZL8clean_upb + 189
        0   mysqld                              0x0000000108f146ba unireg_abort + 867
        0   mysqld                              0x0000000108f19897 _Z11mysqld_mainiPPc + 13637
        0   libdyld.dylib                       0x00007fff7bee3115 start + 1
        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.
        /var/folders/nz/vv4_9tw56nv9k3tkvyszvwg80000gn/T/MariaDB4j/base/bin/mysql_install_db: line 454:  2034 Segmentation fault: 11  "$mysqld_bootstrap" $defaults "$mysqld_opt" --bootstrap $silent_startup "--basedir=$basedir" "--datadir=$ldata" --log-warnings=0 --enforce-storage-engine="" $args --max_allowed_packet=8M --net_buffer_length=16K
        Installation of system tables failed!  Examine the logs in
        /private/var/folders/nz/vv4_9tw56nv9k3tkvyszvwg80000gn/T/MariaDB4j/data/8001 for more information.
        The problem could be conflicting information in an external
        my.cnf files. You can ignore these by doing:
            shell> /var/folders/nz/vv4_9tw56nv9k3tkvyszvwg80000gn/T/MariaDB4j/base/bin/mysql_install_db --defaults-file=~/.my.cnf
        You can also try to start the mysqld daemon with:
            shell> /private/var/folders/nz/vv4_9tw56nv9k3tkvyszvwg80000gn/T/MariaDB4j/base/bin/mysqld --skip-grant --general-log &
        and use the command line tool /private/var/folders/nz/vv4_9tw56nv9k3tkvyszvwg80000gn/T/MariaDB4j/base/bin/mysql
        to connect to the mysql database and look at the grant tables:
            shell> /private/var/folders/nz/vv4_9tw56nv9k3tkvyszvwg80000gn/T/MariaDB4j/base/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 /private/var/folders/nz/vv4_9tw56nv9k3tkvyszvwg80000gn/T/MariaDB4j/data/8001 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
            at ch.vorburger.exec.ManagedProcess.checkResult(ManagedProcess.java:295)
            at ch.vorburger.exec.ManagedProcess.waitForExitMaxMsWithoutLog(ManagedProcess.java:416)
            at ch.vorburger.exec.ManagedProcess.waitForExit(ManagedProcess.java:385)
            at ch.vorburger.mariadb4j.DB.install(DB.java:132)
            ... 3 more
            Caused by:
            org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)