I'm relatively new to Sys Admin, looking for assistance w/ a problem on my Amazon Linux EC2 server running Wordpress.Occasionally, the database goes down. To start debugging, I check mysqld status. It's down.[ec2-user ~]$ sudo service mysqld statusmysqld dead but pid file existsI know I'm running mysqld_safe in order to restart on errors. So I check the logs:[ec2-user ~] sudo cat /var/log/mysqld.log160629 22:15:57 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql160629 22:15:57 [Note] /usr/libexec/mysql55/mysqld (mysqld 5.5.46) starting as process 25953 ...160629 22:15:57 [Note] Plugin 'FEDERATED' is disabled.160629 22:15:57 InnoDB: The InnoDB memory heap is disabled160629 22:15:57 InnoDB: Mutexes and rw_locks use GCC atomic builtins160629 22:15:57 InnoDB: Compressed tables use zlib 1.2.8160629 22:15:57 InnoDB: Using Linux native AIO160629 22:15:57 InnoDB: Initializing buffer pool, size = 128.0M160629 22:15:57 InnoDB: Completed initialization of buffer pool160629 22:15:57 InnoDB: highest supported file format is Barracuda.InnoDB: Log scan progressed past the checkpoint lsn 4143876160629 22:15:57  InnoDB: Database was not shut down normally!InnoDB: Starting crash recovery.InnoDB: Reading tablespace information from the .ibd files...InnoDB: Restoring possible half-written data pages from the doublewriteInnoDB: buffer...InnoDB: Doing recovery: scanned up to log sequence number 4143886160629 22:15:57  InnoDB: Waiting for the background threads to start160629 22:15:58 InnoDB: 5.5.46 started; log sequence number 4143886160629 22:15:58 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306160629 22:15:58 [Note]   - '0.0.0.0' resolves to '0.0.0.0';160629 22:15:58 [Note] Server socket created on IP: '0.0.0.0'.160629 22:15:58 [Note] Event Scheduler: Loaded 0 events160629 22:15:58 [Note] /usr/libexec/mysql55/mysqld: ready for connections.Version: '5.5.46'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)160728 04:38:33 mysqld_safe Number of processes running now: 0 mysqld_safe mysqld restartedI'm not sure what to make of this log. InnoDB: Database was not shut down normally! is a bit suspicious. However, at the end, with mysqld_safe mysqld restarted I'd think it should be back online.I can resolve the issue by manually restarting. But that could be days after I realize the site is down.[ec2-user ~]$ sudo service mysqld startStarting mysqld:                                           [  OK  ]Any suggestions or debugging assistance?
mysqld_safe restarting, but mysqld remains dead
mysql;amazon ec2;aws;wordpress