Which version of the application are you using?:
Please choose how you got the application: Installer (Windows, Linux, macOS), cloud image (AWS, GCE, Azure, ...) or VM (VMDK, VBOX):
Have you installed any plugin or modified any configuration file?:
MySQL is set up to have a master slave relationship with RDS, Otherwise no other modifications
Describe here your question/suggestion/issue (expected and actual results):
Someone rebooted the server this morning because it was running slow. When I connected to the machine to restart apache and mysql, mysql would not start.
/opt/prestashop-220.127.116.11-0/mysql/scripts/ctl.sh : mysql not running
170608 16:37:25 mysqld_safe Logging to '/opt/prestashop-18.104.22.168-0/mysql/data/mysqld.log'.
170608 16:37:25 mysqld_safe Starting mysqld.bin daemon with databases from /opt/prestashop-22.214.171.124-0/mysql/data
170608 16:37:43 mysqld_safe mysqld from pid file /opt/prestashop-126.96.36.199-0/mysql/data/mysqld.pid ended
Perusal of the MySQL Log reveals the following:
2017-06-08 17:08:19 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-06-08 17:08:19 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-06-08 17:08:19 0 [Note] ./mysqld.bin (mysqld 5.6.34-log) starting as process 2463 ...
2017-06-08 17:08:19 2463 [Note] Plugin 'FEDERATED' is disabled.
2017-06-08 17:08:19 2463 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-06-08 17:08:19 2463 [Note] InnoDB: The InnoDB memory heap is disabled
2017-06-08 17:08:19 2463 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-06-08 17:08:19 2463 [Note] InnoDB: Memory barrier is not used
2017-06-08 17:08:19 2463 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-06-08 17:08:19 2463 [Note] InnoDB: Using Linux native AIO
2017-06-08 17:08:19 2463 [Note] InnoDB: Using CPU crc32 instructions
2017-06-08 17:08:19 2463 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-06-08 17:08:19 2463 [Note] InnoDB: Completed initialization of buffer pool
2017-06-08 17:08:19 2463 [Note] InnoDB: Highest supported file format is Barracuda.
2017-06-08 17:08:19 2463 [Note] InnoDB: 128 rollback segment(s) are active.
2017-06-08 17:08:19 2463 [Note] InnoDB: Waiting for purge to start
2017-06-08 17:08:19 2463 [Note] InnoDB: 5.6.34 started; log sequence number 36647118734
09:08:19 UTC - 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.
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.
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
stack_bottom = 0 thread_stack 0x40000
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.
Now if I start
mysqld directly as a root user using
./mysqld --user=root mysql starts up fine with no issues.
./ctlscript.sh start mysql fails every time
Anybody give me a hand with this one?