[MDEV-14152] sudo mysql_install_db --user=mysql --basedir=/usr --datadir=/var/lib/mysql Created: 2017-10-26  Updated: 2017-10-30  Resolved: 2017-10-30

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Affects Version/s: 10.1.28
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Alf Plo Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

Kibojoe Linux 17.09rc4


 Description    

Installing MariaDB/MySQL system tables in '/var/lib/mysql' ...
 
2017-10-26 21:42:21 140635749863360 [Note] /usr/sbin/mysqld (mysqld 10.1.28-MariaDB) starting as process 2711 ...
 
2017-10-26 21:42:21 140635749863360 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
 
 
 
2017-10-26 21:42:21 140635749863360 [Note] InnoDB: Using mutexes to ref count buffer pool pages
 
2017-10-26 21:42:21 140635749863360 [Note] InnoDB: The InnoDB memory heap is disabled
 
2017-10-26 21:42:21 140635749863360 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
 
2017-10-26 21:42:21 140635749863360 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
 
2017-10-26 21:42:21 140635749863360 [Note] InnoDB: Compressed tables use zlib 1.2.11
 
2017-10-26 21:42:21 140635749863360 [Note] InnoDB: Using Linux native AIO
 
2017-10-26 21:42:21 140635749863360 [Note] InnoDB: Using generic crc32 instructions
 
2017-10-26 21:42:21 140635749863360 [Note] InnoDB: Initializing buffer pool, size = 128.0M
 
2017-10-26 21:42:21 140635749863360 [Note] InnoDB: Completed initialization of buffer pool
 
2017-10-26 21:42:21 140635749863360 [Note] InnoDB: Highest supported file format is Barracuda.
 
171026 21:42:21 [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.1.28-MariaDB
 
key_buffer_size=16777216
 
read_buffer_size=262144
 
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 = 137023 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 0x48400
 
/usr/sbin/mysqld(my_print_stacktrace+0x2f)[0x55778c972aff]
 
/usr/sbin/mysqld(handle_fatal_signal+0x566)[0x55778c48fc46]
 
/usr/lib/libpthread.so.0(+0x11da0)[0x7fe84db9ada0]
 
/usr/sbin/mysqld(+0x9eb32f)[0x55778c8db32f]
 
/usr/sbin/mysqld(+0x9eb720)[0x55778c8db720]
 
/usr/sbin/mysqld(+0x9f0ff6)[0x55778c8e0ff6]
 
/usr/sbin/mysqld(+0x9d798a)[0x55778c8c798a]
 
/usr/sbin/mysqld(+0x92b5ee)[0x55778c81b5ee]
 
/usr/sbin/mysqld(+0x83c896)[0x55778c72c896]
 
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x63)[0x55778c492123]
 
/usr/sbin/mysqld(+0x41ba05)[0x55778c30ba05]
 
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x83b)[0x55778c30cacb]
 
/usr/sbin/mysqld(+0x3725f7)[0x55778c2625f7]
 
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x1b13)[0x55778c2660b3]
 
/usr/lib/libc.so.6(__libc_start_main+0xea)[0x7fe84d11ff6a]
 
/usr/sbin/mysqld(_start+0x2a)[0x55778c25a03a]
 
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.


/usr/bin/mysql_install_db: строка 451:  2711 Ошибка сегментирования                   "$mysqld_bootstrap" $defaults "$mysqld_opt" --bootstrap "--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
 
/var/lib/mysql for more information.
 
 
 
The problem could be conflicting information in an external
 
my.cnf files. You can ignore these by doing:
 
 
 
    shell> /usr/scripts/scripts/mysql_install_db --defaults-file=~/.my.cnf
 
 
 
You can also try to start the mysqld daemon with:
 
 
 
    shell> /usr/sbin/mysqld --skip-grant --general-log &
 
 
 
and use the command line tool /usr/bin/mysql
 
to connect to the mysql database and look at the grant tables:
 
 
 
    shell> /usr/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/lib/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



 Comments   
Comment by Elena Stepanova [ 2017-10-26 ]

Are you building from source or using MariaDB packages/binaries? If you are using binaries, please indicate which particular ones. If you are building from source, please provide the cmake/build options.

Please also attach cnf files.

If possible, please produce a coredump and get a stack trace out of it.

Comment by Alf Plo [ 2017-10-27 ]

I am using package from repository Kibojoe.
After reboot and reinstall package mariadb 10.1.28-1 problem solved.

Comment by Elena Stepanova [ 2017-10-30 ]

That is, you've re-installed the same packages? Then the best guess is that something went very wrong with the initial installation.
Or maybe they had some problem with the original packages in their repo, and 10.1.28-1 fixes it?

We don't have Kibojoe in-house, so there isn't much we can say about packages that they provide, or the reliability of the installation process. If the problem occurs again, please inform us, we'll try to see if it's on the MariaDB server side.

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