MySQL Forums
Forum List  »  Install & Repo

Re: Cannot start mysqld after fresh install
Posted by: Dale Schmitz
Date: April 12, 2016 07:35AM

Unfortunately nothing worked, but I did find this information in my /var/lib/mysql/hostname.err log:

160412 08:31:58 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2016-04-12 08:31:58 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-04-12 08:31:58 0 [Note] /usr/sbin/mysqld (mysqld 5.6.29) starting as process 4902 ...
2016-04-12 08:31:58 4902 [Note] Plugin 'FEDERATED' is disabled.
2016-04-12 08:31:58 4902 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-04-12 08:31:58 4902 [Note] InnoDB: The InnoDB memory heap is disabled
2016-04-12 08:31:58 4902 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-04-12 08:31:58 4902 [Note] InnoDB: Memory barrier is not used
2016-04-12 08:31:58 4902 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-04-12 08:31:58 4902 [Note] InnoDB: Using Linux native AIO
2016-04-12 08:31:58 4902 [Note] InnoDB: Not using CPU crc32 instructions
2016-04-12 08:31:58 4902 [Note] InnoDB: Initializing buffer pool, size = 2.0G
2016-04-12 08:31:58 4902 [Note] InnoDB: Completed initialization of buffer pool
2016-04-12 08:31:58 7fc07769b720 InnoDB: Assertion failure in thread 140464613865248 in file fil0fil.cc line 754
InnoDB: Failing assertion: space->purpose != FIL_LOG
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
13:31:58 UTC - mysqld got signal 6 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68108 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 = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8e10d5]
/usr/sbin/mysqld(handle_fatal_signal+0x494)[0x6669d4]
/lib64/libpthread.so.0[0x386200f710]
/lib64/libc.so.6(gsignal+0x35)[0x3861c32625]
/lib64/libc.so.6(abort+0x175)[0x3861c33e05]
/usr/sbin/mysqld[0xa5a472]
/usr/sbin/mysqld[0xa5c6c2]
/usr/sbin/mysqld[0x9c33cc]
/usr/sbin/mysqld[0x9099ed]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x5aa408]
/usr/sbin/mysqld[0x6efe71]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xbb6)[0x6f3b96]
/usr/sbin/mysqld[0x59cd88]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x425)[0x5a1f95]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x3861c1ed5d]
/usr/sbin/mysqld[0x593bb5]
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.
160412 08:31:59 mysqld_safe mysqld from pid file /var/lib/mysql/mysql.pid ended

I don't know what all of this is. This is from Community Server 5.6. I've backtracked from 5.7 thinking it had a bug or I didn't have my system configured properly.

Can anyone help?

Options: ReplyQuote




Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.