I run a development server on AWS which has worked perfectly fine without a hitch. Recently, periodically the mysql server starts to not work. I then type in
service mysqld restart
which yields an error message
MySQL Daemon failed to start.
Now if I stop the instance and then start it, and then restart the server from the command line, everything works fine (this annoyingly forced me to re-edit my zone file due to changed ip addresses, but I've read that a reboot won't get rid of ip addresses). But are there any clues as to why this wouldn't be working?
Here are a few lines from var/log/mysqld.log that I cannot make heads or tails of.
130613 23:12:21 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130613 23:12:21 [Note] Plugin 'FEDERATED' is disabled. 130613 23:12:21 InnoDB: The InnoDB memory heap is disabled 130613 23:12:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins 130613 23:12:21 InnoDB: Compressed tables use zlib 1.2.5 130613 23:12:21 InnoDB: Using Linux native AIO 130613 23:12:21 InnoDB: Initializing buffer pool, size = 128.0M 130613 23:12:21 InnoDB: Completed initialization of buffer pool InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 130613 23:12:21 InnoDB: Setting file ./ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 130613 23:12:22 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 130613 23:12:23 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: 127 rollback segment(s) active. InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 130613 23:12:24 InnoDB: Waiting for the background threads to start 130613 23:12:25 InnoDB: 5.5.31 started; log sequence number 0 130613 23:12:25 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 130613 23:12:25 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 130613 23:12:25 [Note] Server socket created on IP: '0.0.0.0'. 130613 23:12:25 [Note] Event Scheduler: Loaded 0 events 130613 23:12:25 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.5.31' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) 130614 6:08:52 [Note] /usr/libexec/mysqld: Normal shutdown 130614 6:08:53 [Note] Event Scheduler: Purging the queue. 0 events
I read at other posts on stackexchange that sometimes this can be due to disk size limitations. df - h says
Filesystem Size Used Avail Use% Mounted on /dev/xvda1 7.9G 1.7G 6.2G 22% / tmpfs 298M 0 298M 0% /dev/shm
Anyone have any idea what else I should be hunting for?