LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
Reload this Page Mariadb not starting at all
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices


Reply
Page 1 of 2 1 2
  Search this Thread
Old 01-19-2020, 11:47 PM   #1
kajlaajay
LQ Newbie
 
Registered: Jan 2020
Posts: 9

Rep: Reputation: Disabled
Unhappy Mariadb not starting at all

Please help me with this issue MariaDB not starting. Its a production server so not able to reinstall and clean the data at all.

(This command executed by me) systemctl -l status mariadb.service

● mariadb.service - MariaDB 10.1.36 database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Mon 2020-01-20 10:58:08 IST; 3s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 8176 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 8165 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 8158 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 8176 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"

2020-01-20 10:58:03 139801831975168 [ERROR] Plugin 'InnoDB' init function returned error.
2020-01-20 10:58:03 139801831975168 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2020-01-20 10:58:03 139801831975168 [Note] Plugin 'FEEDBACK' is disabled.
2020-01-20 10:58:03 139801831975168 [ERROR] Unknown/unsupported storage engine: InnoDB
2020-01-20 10:58:03 139801831975168 [ERROR] Aborting
Error in my_thread_global_end(): 1 threads didn't exit
mariadb.service: main process exited, code=exited, status=1/FAILURE
Failed to start MariaDB 10.1.36 database server.
Unit mariadb.service entered failed state.
mariadb.service failed.
 
Old 01-20-2020, 01:21 AM   #2
berndbausch
LQ Addict
 
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316

Rep: Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002
You need to find more log messages to understand what's wrong with InnoDB. Either journalctl -u mariadb, or better the log files under /var/log/mysql (from memory, and might be configured differently).

EDIT: The internet has answers that may or may not fit your problem, for example https://stackoverflow.com/questions/...ailed-when-sta.
Last edited by berndbausch; 01-20-2020 at 01:22 AM.
 
Old 01-20-2020, 02:22 AM   #3
j-ray
Senior Member
 
Registered: Jan 2002
Location: germany
Distribution: ubuntu, mint, suse
Posts: 1,591

Rep: Reputation: 145Reputation: 145
As berndbausch suggested it is important to get a more detailed info about what is not working. When I looked around on the web I stumbled across this:

https://duntuk.com/mariadbmysql-how-...-engine-innodb

So this is one possible fault + solution. But your case might be a different one.
 
Old 01-20-2020, 03:38 AM   #4
kajlaajay
LQ Newbie
 
Registered: Jan 2020
Posts: 9

Original Poster
Rep: Reputation: Disabled
Unhappy Thanks but not working
Thanks for the help j-ray but its not working for me
 
Old 01-20-2020, 04:21 AM   #5
berndbausch
LQ Addict
 
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316

Rep: Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002
Use the full log, and search the internet for "Plugin 'InnoDB' registration as a STORAGE ENGINE failed".
 
Old 01-20-2020, 10:19 AM   #6
TB0ne
LQ Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 26,635

Rep: Reputation: 7965Reputation: 7965Reputation: 7965Reputation: 7965Reputation: 7965Reputation: 7965Reputation: 7965Reputation: 7965Reputation: 7965Reputation: 7965Reputation: 7965
Quote:
Originally Posted by kajlaajay View Post
Thanks for the help j-ray but its not working for me
Might also help to tell us what version/distro of Linux you're using, and what happened to cause this. Server failure? Power outage?? If it was a production server and was fully functional, then SOMETHING had to have happened to cause it to shut down. Any ideas?

I also see references to Galera cluster and mysql...is this part of a cluster and did you attempt an upgrade?
 
Old 01-20-2020, 08:33 PM   #7
kajlaajay
LQ Newbie
 
Registered: Jan 2020
Posts: 9

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by TB0ne View Post
Might also help to tell us what version/distro of Linux you're using, and what happened to cause this. Server failure? Power outage?? If it was a production server and was fully functional, then SOMETHING had to have happened to cause it to shut down. Any ideas?

I also see references to Galera cluster and mysql...is this part of a cluster and did you attempt an upgrade?
My OS is Centos 7 with CWP in it. the day before yesterday it was all fine i leave it after my shift was ended. But next day its like that only. No changes made to server in my knowledge. any server not able to start at all few things i found that its happening by mariadb because its not able to recover its data. I am expert here. I just know few commands on it. Please let me know if you need additional details.

Because its production server things got messy here and i dont have backup.
 
Old 01-20-2020, 08:38 PM   #8
kajlaajay
LQ Newbie
 
Registered: Jan 2020
Posts: 9

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by berndbausch View Post
Use the full log, and search the internet for "Plugin 'InnoDB' registration as a STORAGE ENGINE failed".
Tried but nothing comes to resolve this issue
 
Old 01-20-2020, 10:28 PM   #9
kajlaajay
LQ Newbie
 
Registered: Jan 2020
Posts: 9

Original Poster
Rep: Reputation: Disabled
Unhappy After log file delete
Hi Friends

After deleting var/lib/mysql log file delete and restore previous files my error is changed. Now this is coming can anybody know about this

systemctl status mariadb.service

● mariadb.service - MariaDB 10.1.36 database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: activating (auto-restart) (Result: signal) since Tue 2020-01-21 09:54:18 IST; 1s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 3855 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=killed, signal=ABRT)
Process: 3840 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 3838 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 3855 (code=killed, signal=ABRT)
Status: "Starting Innodb crash recovery"

Jan 21 09:54:18 systemd[1]: Failed to start MariaDB 10.1.36 database server.
Jan 21 09:54:18 systemd[1]: Unit mariadb.service entered failed state.
Jan 21 09:54:18 systemd[1]: mariadb.service failed.
 
Old 01-20-2020, 11:16 PM   #10
kajlaajay
LQ Newbie
 
Registered: Jan 2020
Posts: 9

Original Poster
Rep: Reputation: Disabled
Angry Temporary Solution Found but need permanent solution with innodb
Hi Guys

Temporary Solution Found but need a permanent solution with InnoDB.

i added "default-storage-engine=myisam" to /etc/my.cnf.d/server.cnf in the [mysqld] section to skip the "innoDB".

Now everything works but why not my InnoDB working
 
Old 01-20-2020, 11:28 PM   #11
berndbausch
LQ Addict
 
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316

Rep: Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002
Quote:
Originally Posted by kajlaajay View Post
Jan 21 09:54:18 systemd[1]: Failed to start MariaDB 10.1.36 database server.
Jan 21 09:54:18 systemd[1]: Unit mariadb.service entered failed state.
Jan 21 09:54:18 systemd[1]: mariadb.service failed.
The systemctl start/restart/status commands only print a few lines from the log. All we know is that InnoDB crashed, which is important but not sufficient: To troubleshoot, we need to have details about why it crashed.

It's very likely that useful information is in the systemd journal and/or the MariaDB logs. Read that before changing your configuration.
Last edited by berndbausch; 01-20-2020 at 11:30 PM.
 
Old 01-21-2020, 01:18 AM   #12
kajlaajay
LQ Newbie
 
Registered: Jan 2020
Posts: 9

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by berndbausch View Post
The systemctl start/restart/status commands only print a few lines from the log. All we know is that InnoDB crashed, which is important but not sufficient: To troubleshoot, we need to have details about why it crashed.

It's very likely that useful information is in the systemd journal and/or the MariaDB logs. Read that before changing your configuration.
I tried 1 thing that i truncate the ib_logfile1, ib_logfile0 and ibdata1 to check weather these making some error but nothing happen same error comes.

After this, i check this comment journalctl -xe

-- Subject: Unit user-1001.slice has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman.../systemd-devel
--
-- Unit user-1001.slice has finished shutting down.
Jan 21 12:37:04 "HOST" postfix/cleanup[19115]: warning: 6AD462696: virtual_alias_maps map lookup problem for "USER"@"HOST"
Jan 21 12:37:04 "HOST" systemd[1]: Stopping User Slice of "USER".
-- Subject: Unit user-1001.slice has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman.../systemd-devel
--
-- Unit user-1001.slice has begun shutting down.
Jan 21 12:37:04 "HOST" postfix/cleanup[19115]: warning: proxy:mysql:/etc/postfix/mysql-virtual_vacation.cf lookup error
Jan 21 12:37:04 "HOST" postfix/cleanup[19115]: warning: 6AD462696: recipient_bcc_maps lookup problem
Jan 21 12:37:04 "HOST" postfix/pickup[21070]: 6C243746: uid=1001 from=<"USER">
Jan 21 12:37:04 "HOST" postfix/cleanup[18808]: 6C243746: message-id=<20200121070704.6C243746@"HOST">
Jan 21 12:37:04 "HOST" postfix/cleanup[18808]: warning: proxy:mysql:/etc/postfix/mysql-virtual_alias_maps.cf lookup erro
Jan 21 12:37:04 "HOST" postfix/cleanup[18808]: warning: 6C243746: virtual_alias_maps map lookup problem for "USER"@"HOST"
Jan 21 12:37:04 "HOST" postfix/cleanup[18808]: warning: proxy:mysql:/etc/postfix/mysql-virtual_vacation.cf lookup error
Jan 21 12:37:04 "HOST" postfix/cleanup[18808]: warning: 6C243746: recipient_bcc_maps lookup problem
Jan 21 12:37:04 "HOST" postfix/smtpd[25327]: disconnect from unknown[IP]
Jan 21 12:37:04 "HOST" postfix/smtpd[25802]: disconnect from unknown[IP]
Jan 21 12:37:07 "HOST" postfix/smtpd[20539]: warning: unknown[IP]: SASL LOGIN authentication failed: Connecti
lines 1589-1611/1611 (END)

i think this is coming because my innodb is stopped. (few field in it modified due to security reasons)
 
Old 01-21-2020, 02:15 AM   #13
berndbausch
LQ Addict
 
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316

Rep: Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002
These are messages from the Postfix Mail Transfer Agent, not MariaDB. They have absolutely nothing to do with your problem.

Run this to get all MariaDB messages in the journal:
Code:
journalctl -u mariadb
However I think the really interesting messages are in /var/log/mysql (or perhaps /var/log/mariadb or something similar).
 
Old 01-21-2020, 02:59 AM   #14
kajlaajay
LQ Newbie
 
Registered: Jan 2020
Posts: 9

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by berndbausch View Post
These are messages from the Postfix Mail Transfer Agent, not MariaDB. They have absolutely nothing to do with your problem.

Run this to get all MariaDB messages in the journal:
Code:
journalctl -u mariadb
However I think the really interesting messages are in /var/log/mysql (or perhaps /var/log/mariadb or something similar).
Hey friend as you say to take mariadb log by using your command here it is: its not complete but out of all few which are show at top by using command.

# journalctl -u mariadb
-- Logs begin at Tue 2020-01-21 09:58:28 IST, end at Tue 2020-01-21 14:20:31 IST. --
Jan 21 09:58:35 systemd[1]: Starting MariaDB 10.1.36 database server...
Jan 21 09:58:37 mysqld[825]: 2020-01-21 9:58:37 139850859440384 [Note] /usr/sbin/mysqld (mysqld 10.1.36-MariaDB)
Jan 21 09:58:38 mysqld[825]: 2020-01-21 9:58:38 139850859440384 [Note] InnoDB: innodb_empty_free_list_algorithm
Jan 21 09:58:38 mysqld[825]: 2020-01-21 9:58:38 139850859440384 [Note] InnoDB: Using mutexes to ref count buffer
Jan 21 09:58:38 mysqld[825]: 2020-01-21 9:58:38 139850859440384 [Note] InnoDB: The InnoDB memory heap is disable
Jan 21 09:58:38 mysqld[825]: 2020-01-21 9:58:38 139850859440384 [Note] InnoDB: Mutexes and rw_locks use GCC atom
Jan 21 09:58:38 mysqld[825]: 2020-01-21 9:58:38 139850859440384 [Note] InnoDB: GCC builtin __atomic_thread_fence
Jan 21 09:58:38 mysqld[825]: 2020-01-21 9:58:38 139850859440384 [Note] InnoDB: Compressed tables use zlib 1.2.7
Jan 21 09:58:38 mysqld[825]: 2020-01-21 9:58:38 139850859440384 [Note] InnoDB: Using Linux native AIO
Jan 21 09:58:38 mysqld[825]: 2020-01-21 9:58:38 139850859440384 [Note] InnoDB: Using SSE crc32 instructions
Jan 21 09:58:38 mysqld[825]: 2020-01-21 9:58:38 139850859440384 [Note] InnoDB: Initializing buffer pool, size =
Jan 21 09:58:38 mysqld[825]: 2020-01-21 9:58:38 139850859440384 [Note] InnoDB: Completed initialization of buffe
Jan 21 09:58:38 mysqld[825]: 2020-01-21 9:58:38 139850859440384 [Note] InnoDB: Highest supported file format is
Jan 21 09:58:38 mysqld[825]: 2020-01-21 9:58:38 139850859440384 [Note] InnoDB: Starting crash recovery from chec
Jan 21 09:58:50 mysqld[825]: 2020-01-21 09:58:50 7f3190cc6900 InnoDB: Assertion failure in thread 13985085944038
Jan 21 09:58:50 mysqld[825]: InnoDB: We intentionally generate a memory trap.
Jan 21 09:58:50 mysqld[825]: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
Jan 21 09:58:50 mysqld[825]: InnoDB: If you get repeated assertion failures or crashes, even
Jan 21 09:58:50 mysqld[825]: InnoDB: immediately after the mysqld startup, there may be
Jan 21 09:58:50 mysqld[825]: InnoDB: corruption in the InnoDB tablespace. Please refer to
Jan 21 09:58:50 mysqld[825]: InnoDB: http://dev.mysql.com/doc/refman/5.6/...-recovery.html
Jan 21 09:58:50 mysqld[825]: InnoDB: about forcing recovery.
Jan 21 09:58:50 mysqld[825]: 200121 9:58:50 [ERROR] mysqld got signal 6 ;
Jan 21 09:58:50 mysqld[825]: This could be because you hit a bug. It is also possible that this binary
Jan 21 09:58:50 mysqld[825]: or one of the libraries it was linked against is corrupt, improperly built,
Jan 21 09:58:50 mysqld[825]: or misconfigured. This error can also be caused by malfunctioning hardware.
Jan 21 09:58:50 mysqld[825]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Jan 21 09:58:50 mysqld[825]: We will try our best to scrape up some info that will hopefully help
Jan 21 09:58:50 mysqld[825]: diagnose the problem, but since we have already crashed,
Jan 21 09:58:50 mysqld[825]: something is definitely wrong and this may fail.
Jan 21 09:58:50 mysqld[825]: Server version: 10.1.36-MariaDB
Jan 21 09:58:50 mysqld[825]: key_buffer_size=134217728
Jan 21 09:58:50 mysqld[825]: read_buffer_size=131072
Jan 21 09:58:50 mysqld[825]: max_used_connections=0
Jan 21 09:58:50 mysqld[825]: max_threads=153
Jan 21 09:58:50 mysqld[825]: thread_count=0
Jan 21 09:58:50 mysqld[825]: It is possible that mysqld could use up to
Jan 21 09:58:50 mysqld[825]: It is possible that mysqld could use up to
Jan 21 09:58:50 mysqld[825]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467164 K byte
Jan 21 09:58:50 mysqld[825]: Hope that's ok; if not, decrease some variables in the equation.
Jan 21 09:58:50 mysqld[825]: Thread pointer: 0x0
Jan 21 09:58:50 mysqld[825]: Attempting backtrace. You can use the following information to find out
Jan 21 09:58:50 mysqld[825]: where mysqld died. If you see no messages after this, something went
Jan 21 09:58:50 mysqld[825]: terribly wrong...
Jan 21 09:58:50 mysqld[825]: stack_bottom = 0x0 thread_stack 0x48400
Jan 21 09:58:51 mysqld[825]: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5592453c771e]
Jan 21 09:58:51 mysqld[825]: /usr/sbin/mysqld(handle_fatal_signal+0x305)[0x559244eead75]
Jan 21 09:58:51 mysqld[825]: sigaction.c:0(__restore_rt)[0x7f31908b56d0]
Jan 21 09:58:51 mysqld[825]: :0(__GI_raise)[0x7f318e955277]
Jan 21 09:58:51 mysqld[825]: :0(__GI_abort)[0x7f318e956968]
Jan 21 09:58:51 mysqld[825]: include/fut0lst.ic:50(flst_write_addr(unsigned char*, fil_addr_t, mtr_t*) [clone .pa
Jan 21 09:58:51 mysqld[825]: fsp/fsp0fsp.cc:1880(fseg_inode_get)[0x55924530328a]
Jan 21 09:58:51 mysqld[825]: ibuf/ibuf0ibuf.cc:604(ibuf_init_at_db_start())[0x55924515e304]
Jan 21 09:58:51 mysqld[825]: dict/dict0boot.cc:464(dict_boot())[0x5592452b1a9b]
Jan 21 09:58:51 mysqld[825]: srv/srv0start.cc:2647(innobase_start_or_create_for_mysql())[0x55924521f736]
Jan 21 09:58:51 mysqld[825]: handler/ha_innodb.cc:4526(innobase_init(void*))[0x55924513d3cd]
Jan 21 09:58:51 mysqld[825]: sql/handler.cc:522(ha_initialize_handlerton(st_plugin_int*))[0x559244eed024]
Jan 21 09:58:51 mysqld[825]: sql/sql_plugin.cc:1409(plugin_initialize(st_mem_root*, st_plugin_int*, int*, char**,
Jan 21 09:58:51 mysqld[825]: sql/sql_plugin.cc:1686(plugin_init(int*, char**, int))[0x559244d73e2a]
Jan 21 09:58:51 mysqld[825]: sql/mysqld.cc:5153(init_server_components())[0x559244cc9261]
Jan 21 09:58:51 mysqld[825]: sql/mysqld.cc:5746(mysqld_main(int, char**))[0x559244ccd0f0]
Jan 21 09:58:51 mysqld[825]: /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f318e941445]
Jan 21 09:58:51 mysqld[825]: /usr/sbin/mysqld(+0x39a7cd)[0x559244cc07cd]
Jan 21 09:58:51 mysqld[825]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Jan 21 09:58:51 mysqld[825]: information that should help you find out what is causing the crash.
Jan 21 09:58:51 systemd[1]: mariadb.service: main process exited, code=killed, status=6/ABRT
Jan 21 09:58:51 systemd[1]: Failed to start MariaDB 10.1.36 database server.
Jan 21 09:58:51 systemd[1]: Unit mariadb.service entered failed state.
Jan 21 09:58:51 systemd[1]: mariadb.service failed.
Jan 21 09:58:56 systemd[1]: mariadb.service holdoff time over, scheduling restart.
Jan 21 09:58:56 systemd[1]: Starting MariaDB 10.1.36 database server...
Jan 21 09:58:57 mysqld[1680]: 2020-01-21 9:58:57 139764494727424 [Note] /usr/sbin/mysqld (mysqld 10.1.36-MariaDB
Jan 21 09:58:57 mysqld[1680]: 2020-01-21 9:58:57 139764494727424 [Note] InnoDB: innodb_empty_free_list_algorithm
Jan 21 09:58:57 mysqld[1680]: 2020-01-21 9:58:57 139764494727424 [Note] InnoDB: Using mutexes to ref count buffe
Jan 21 09:58:57 mysqld[1680]: 2020-01-21 9:58:57 139764494727424 [Note] InnoDB: The InnoDB memory heap is disabl
Jan 21 09:58:57 mysqld[1680]: 2020-01-21 9:58:57 139764494727424 [Note] InnoDB: Mutexes and rw_locks use GCC ato
Jan 21 09:58:57 mysqld[1680]: 2020-01-21 9:58:57 139764494727424 [Note] InnoDB: GCC builtin __atomic_thread_fenc
Jan 21 09:58:57 mysqld[1680]: 2020-01-21 9:58:57 139764494727424 [Note] InnoDB: Compressed tables use zlib 1.2.7
Jan 21 09:58:57 mysqld[1680]: 2020-01-21 9:58:57 139764494727424 [Note] InnoDB: Using Linux native AIO
Jan 21 09:58:57 mysqld[1680]: 2020-01-21 9:58:57 139764494727424 [Note] InnoDB: Using SSE crc32 instructions
Jan 21 09:58:57 mysqld[1680]: 2020-01-21 9:58:57 139764494727424 [Note] InnoDB: Initializing buffer pool, size =
Jan 21 09:58:57 mysqld[1680]: 2020-01-21 9:58:57 139764494727424 [Note] InnoDB: Completed initialization of buff
Jan 21 09:58:57 mysqld[1680]: 2020-01-21 9:58:57 139764494727424 [Note] InnoDB: Highest supported file format is
Jan 21 09:58:57 mysqld[1680]: 2020-01-21 9:58:57 139764494727424 [Note] InnoDB: Starting crash recovery from che
Jan 21 09:58:57 mysqld[1680]: 2020-01-21 09:58:57 7f1d750f7900 InnoDB: Assertion failure in thread 1397644947274
Jan 21 09:58:57 mysqld[1680]: InnoDB: We intentionally generate a memory trap.
Jan 21 09:58:57 mysqld[1680]: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
Jan 21 09:58:57 mysqld[1680]: InnoDB: If you get repeated assertion failures or crashes, even
Jan 21 09:58:57 mysqld[1680]: InnoDB: immediately after the mysqld startup, there may be
Jan 21 09:58:57 mysqld[1680]: InnoDB: corruption in the InnoDB tablespace. Please refer to
Jan 21 09:58:57 mysqld[1680]: InnoDB: http://dev.mysql.com/doc/refman/5.6/...-recovery.html
Jan 21 09:58:57 mysqld[1680]: InnoDB: about forcing recovery.
Jan 21 09:58:57 mysqld[1680]: 200121 9:58:57 [ERROR] mysqld got signal 6 ;
Jan 21 09:58:57 mysqld[1680]: This could be because you hit a bug. It is also possible that this binary
Jan 21 09:58:57 mysqld[1680]: or one of the libraries it was linked against is corrupt, improperly built,
Jan 21 09:58:57 mysqld[1680]: or misconfigured. This error can also be caused by malfunctioning hardware.
Jan 21 09:58:57 mysqld[1680]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Jan 21 09:58:57 mysqld[1680]: We will try our best to scrape up some info that will hopefully help
Jan 21 09:58:57 mysqld[1680]: diagnose the problem, but since we have already crashed,
Jan 21 09:58:57 mysqld[1680]: something is definitely wrong and this may fail.
Jan 21 09:58:57 mysqld[1680]: Server version: 10.1.36-MariaDB
Jan 21 09:58:57 mysqld[1680]: key_buffer_size=134217728
Jan 21 09:58:57 mysqld[1680]: read_buffer_size=131072
Jan 21 09:58:57 mysqld[1680]: max_used_connections=0
Jan 21 09:58:57 mysqld[1680]: max_threads=153
Jan 21 09:58:57 mysqld[1680]: thread_count=0
Jan 21 09:58:57 mysqld[1680]: It is possible that mysqld could use up to
Jan 21 09:58:57 mysqld[1680]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467164 K byt
Jan 21 09:58:57 mysqld[1680]: Hope that's ok; if not, decrease some variables in the equation.
Jan 21 09:58:57 mysqld[1680]: Thread pointer: 0x0
Jan 21 09:58:57 mysqld[1680]: Attempting backtrace. You can use the following information to find out
Jan 21 09:58:57 mysqld[1680]: where mysqld died. If you see no messages after this, something went
Jan 21 09:58:57 mysqld[1680]: terribly wrong...
Jan 21 09:58:57 mysqld[1680]: stack_bottom = 0x0 thread_stack 0x48400
Jan 21 09:58:57 mysqld[1680]: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55bf5c82d71e]
Jan 21 09:58:57 mysqld[1680]: /usr/sbin/mysqld(handle_fatal_signal+0x305)[0x55bf5c350d75]
Jan 21 09:58:58 mysqld[1680]: sigaction.c:0(__restore_rt)[0x7f1d74ce66d0]
Jan 21 09:58:58 mysqld[1680]: :0(__GI_raise)[0x7f1d72d86277]
Jan 21 09:58:58 mysqld[1680]: :0(__GI_abort)[0x7f1d72d87968]
Jan 21 09:58:58 mysqld[1680]: /usr/sbin/mysqld(+0x38332d)[0x55bf5c10f32d]
Jan 21 09:58:58 mysqld[1680]: include/fut0lst.ic:50(flst_write_addr(unsigned char*, fil_addr_t, mtr_t*) [clone .p
Jan 21 09:58:58 mysqld[1680]: ibuf/ibuf0ibuf.cc:604(ibuf_init_at_db_start())[0x55bf5c5c4304]
Jan 21 09:58:58 mysqld[1680]: dict/dict0boot.cc:464(dict_boot())[0x55bf5c717a9b]
Jan 21 09:58:58 mysqld[1680]: srv/srv0start.cc:2647(innobase_start_or_create_for_mysql())[0x55bf5c685736]
Jan 21 09:58:58 mysqld[1680]: handler/ha_innodb.cc:4526(innobase_init(void*))[0x55bf5c5a33cd]
Jan 21 09:58:58 mysqld[1680]: sql/handler.cc:522(ha_initialize_handlerton(st_plugin_int*))[0x55bf5c353024]
Jan 21 09:58:58 mysqld[1680]: sql/sql_plugin.cc:1409(plugin_initialize(st_mem_root*, st_plugin_int*, int*, char**
Jan 21 09:58:58 mysqld[1680]: sql/sql_plugin.cc:1686(plugin_init(int*, char**, int))[0x55bf5c1d9e2a]
Jan 21 09:58:58 mysqld[1680]: /usr/sbin/mysqld(+0x3a3261)[0x55bf5c12f261]
Jan 21 09:58:58 mysqld[1680]: sql/mysqld.cc:5153(init_server_components())[0x55bf5c1330f0]
Jan 21 09:58:58 mysqld[1680]: /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f1d72d72445]
Jan 21 09:58:58 mysqld[1680]: /usr/sbin/mysqld(+0x39a7cd)[0x55bf5c1267cd]
Jan 21 09:58:58 mysqld[1680]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Jan 21 09:58:58 mysqld[1680]: information that should help you find out what is causing the crash.
Jan 21 09:58:58 systemd[1]: mariadb.service: main process exited, code=killed, status=6/ABRT
Jan 21 09:58:58 systemd[1]: Failed to start MariaDB 10.1.36 database server.
Jan 21 09:58:58 systemd[1]: Unit mariadb.service entered failed state.
Jan 21 09:58:58 systemd[1]: mariadb.service failed.
Jan 21 09:59:03 systemd[1]: mariadb.service holdoff time over, scheduling restart.
Jan 21 09:59:03 systemd[1]: Starting MariaDB 10.1.36 database server...
Jan 21 09:59:04 mysqld[1759]: 2020-01-21 9:59:04 140691459795200 [Note] /usr/sbin/mysqld (mysqld 10.1.36-MariaDB
Jan 21 09:59:05 mysqld[1759]: 2020-01-21 9:59:05 140691459795200 [Note] InnoDB: innodb_empty_free_list_algorithm
Jan 21 09:59:05 mysqld[1759]: 2020-01-21 9:59:05 140691459795200 [Note] InnoDB: Using mutexes to ref count buffe
Jan 21 09:59:05 mysqld[1759]: 2020-01-21 9:59:05 140691459795200 [Note] InnoDB: The InnoDB memory heap is disabl
Jan 21 09:59:05 mysqld[1759]: 2020-01-21 9:59:05 140691459795200 [Note] InnoDB: Mutexes and rw_locks use GCC ato
Jan 21 09:59:05 mysqld[1759]: 2020-01-21 9:59:05 140691459795200 [Note] InnoDB: GCC builtin __atomic_thread_fenc
Jan 21 09:59:05 mysqld[1759]: 2020-01-21 9:59:05 140691459795200 [Note] InnoDB: Compressed tables use zlib 1.2.7
Jan 21 09:59:05 mysqld[1759]: 2020-01-21 9:59:05 140691459795200 [Note] InnoDB: Using Linux native AIO
Jan 21 09:59:05 mysqld[1759]: 2020-01-21 9:59:05 140691459795200 [Note] InnoDB: Using SSE crc32 instructions
Jan 21 09:59:05 mysqld[1759]: 2020-01-21 9:59:05 140691459795200 [Note] InnoDB: Initializing buffer pool, size =
Jan 21 09:59:05 mysqld[1759]: 2020-01-21 9:59:05 140691459795200 [Note] InnoDB: Completed initialization of buff
Jan 21 09:59:05 mysqld[1759]: 2020-01-21 9:59:05 140691459795200 [Note] InnoDB: Highest supported file format is
Jan 21 09:59:05 mysqld[1759]: 2020-01-21 9:59:05 140691459795200 [Note] InnoDB: Starting crash recovery from che
Jan 21 09:59:05 mysqld[1759]: 2020-01-21 09:59:05 7ff5487be900 InnoDB: Assertion failure in thread 1406914597952
Jan 21 09:59:05 mysqld[1759]: InnoDB: We intentionally generate a memory trap.
Jan 21 09:59:05 mysqld[1759]: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
Jan 21 09:59:05 mysqld[1759]: InnoDB: If you get repeated assertion failures or crashes, even
Jan 21 09:59:05 mysqld[1759]: InnoDB: immediately after the mysqld startup, there may be
Jan 21 09:59:05 mysqld[1759]: InnoDB: corruption in the InnoDB tablespace. Please refer to
Jan 21 09:59:05 mysqld[1759]: InnoDB: http://dev.mysql.com/doc/refman/5.6/...-recovery.html
Jan 21 09:59:05 mysqld[1759]: InnoDB: about forcing recovery.
Jan 21 09:59:05 mysqld[1759]: 200121 9:59:05 [ERROR] mysqld got signal 6 ;
Jan 21 09:59:05 mysqld[1759]: This could be because you hit a bug. It is also possible that this binary
Jan 21 09:59:05 mysqld[1759]: or one of the libraries it was linked against is corrupt, improperly built,
Jan 21 09:59:05 mysqld[1759]: or misconfigured. This error can also be caused by malfunctioning hardware.
Jan 21 09:59:05 mysqld[1759]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Jan 21 09:59:05 mysqld[1759]: We will try our best to scrape up some info that will hopefully help
Jan 21 09:59:05 mysqld[1759]: diagnose the problem, but since we have already crashed,
Jan 21 09:59:05 mysqld[1759]: something is definitely wrong and this may fail.
Jan 21 09:59:05 mysqld[1759]: Server version: 10.1.36-MariaDB
Jan 21 09:59:05 mysqld[1759]: key_buffer_size=134217728
Jan 21 09:59:05 mysqld[1759]: read_buffer_size=131072
Jan 21 09:59:05 mysqld[1759]: max_used_connections=0
Jan 21 09:59:05 mysqld[1759]: max_threads=153
Jan 21 09:59:05 mysqld[1759]: thread_count=0
 
Old 01-21-2020, 03:06 AM   #15
berndbausch
LQ Addict
 
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316

Rep: Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002
I should have told you to redirect the journalctl output to a file in order to obtain full lines. When you run journalctl at the command prompt, it truncates lines to the width of the terminal by default.

Still, I think the important part is
Code:
Jan 21 09:59:05 mysqld[1759]: InnoDB: If you get repeated assertion failures or crashes, even
Jan 21 09:59:05 mysqld[1759]: InnoDB: immediately after the mysqld startup, there may be
Jan 21 09:59:05 mysqld[1759]: InnoDB: corruption in the InnoDB tablespace. Please refer to
Jan 21 09:59:05 mysqld[1759]: InnoDB: http://dev.mysql.com/doc/refman/5.6/...-recovery.html
Jan 21 09:59:05 mysqld[1759]: InnoDB: about forcing recovery.
Since you do get repeated crashes, see if the referenced web page https://dev.mysql.com/doc/refman/5.6...-recovery.html helps.

Personally, my MySQL/MariaDB/InnoDB skill level is not really high, so that I am not sure what precisely is wrong here.
 
  


Reply
Page 1 of 2 1 2



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: KDE Participating in Google Summer of Code 2019, MariaDB Releasing New Open-Source MariaDB Enterprise Server, CentOS Celebrates 15th B LXer Syndicated Linux News 0 02-28-2019 06:50 AM
starting MariaDB 10.1.30 in CentOS 7 server mkomid Linux - Server 14 02-17-2018 08:26 PM
MariaDB Galera Cluster Starting Issue blakk Red Hat 2 03-05-2015 02:17 PM
When Centos 6.3 starting,All services starting OK and starting Atd: OK .And stop scr. DeSouffle Linux - General 4 08-29-2013 12:46 AM
[SOLVED] Starting File System .. Starting File System .. Starting File System .. Starting File rmknox Linux - Newbie 3 08-15-2010 11:30 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 03:41 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration