Re: Could not start mysql, any ideas?

On Thursday, August 20, 2015 at 10:37:25 PM UTC+8, Jerry Stuckle wrote:
> On 8/20/2015 9:55 AM, Raymond Fung wrote:
> > Could not start mysql, any ideas?
> >
> > 150820 21:47:08 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
> > 2015-08-20 21:47:08 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
> > 2015-08-20 21:47:08 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
> > 2015-08-20 21:47:08 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-log) starting as process 6797 ...
> > 2015-08-20 21:47:08 6797 [Note] Plugin 'FEDERATED' is disabled.
> > 2015-08-20 21:47:08 6797 [Note] InnoDB: Using atomics to ref count buffer pool pages
> > 2015-08-20 21:47:08 6797 [Note] InnoDB: The InnoDB memory heap is disabled
> > 2015-08-20 21:47:08 6797 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
> > 2015-08-20 21:47:08 6797 [Note] InnoDB: Memory barrier is not used
> > 2015-08-20 21:47:08 6797 [Note] InnoDB: Compressed tables use zlib 1.2.3
> > 2015-08-20 21:47:08 6797 [Note] InnoDB: Using Linux native AIO
> > 2015-08-20 21:47:08 6797 [Note] InnoDB: Using CPU crc32 instructions
> > 2015-08-20 21:47:08 6797 [Note] InnoDB: Initializing buffer pool, size = 8.0G
> > 2015-08-20 21:47:08 6797 [Note] InnoDB: Completed initialization of buffer pool
> > 2015-08-20 21:47:08 6797 [ERROR] InnoDB: Space id in fsp header 1416128883,but in the page header 824195850
> > 2015-08-20 21:47:08 7f8ab4333720 InnoDB: Assertion failure in thread 140233705469728 in file srv0start.cc line 1031
> > InnoDB: Failing assertion: one_opened || space == TRX_SYS_SPACE
> > 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:47:08 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.
> >
>
> What happened just before this error started? Did you upgrade MySQL,
> for instance? Restore a database? IOW, what is different now then when
> it was working?
>
> You might be getting hit by bug 69623:
>
> https://bugs.mysql.com/bug.php?id=69623
>
> (This took me about 30 seconds to find in a Google search).
>
> See the notes towards the bottom of the comments about
> upgrading/downgrading.
>
> --
> ==================
> Remove the "x" from my email address
> Jerry Stuckle
> jstucklex_at_attglobal.net
> ==================

Thanks Jerry.

Nothing observed from log files when the DB crashed. It crashed after a few weeks running.

The symptoms are similar to the bug 69623 you mentioned except that there is no report of checksum mismatch. Received on Thu Aug 20 2015 - 20:58:25 CEST