mysqld在t2.micro上意外停止Amazon Linux實例

Question

我在EC2上運行t2.micro Amazon Linux實例。我安裝了LAMP和Wordpress。

我每次離開我的終端通過ssh連接到我的實例在睡覺/去外面之前，我一直在經歷許多意想不到的mysqld關閉。當我醒來/回到家時，mysqld總是關閉自己。 （而且我不確定這是否與自行停止問題有關。）或者這是一個內存問題？ （t2.micro實例只提供1GB內存）

每次mysqld關閉時，我配置的文件權限都消失了，而且每次重新應用文件權限都很煩人。

我剛開始使用這些服務器設置的東西，我仍然是一個新手... 有人可以幫助我，並告訴我該怎麼做，以防止未來的mysqld自我關閉，即使我離開終端連接打開，以及如何配置它，以便在關閉後不必重新應用文件權限？

這裏是mysqld的日誌：

150627 18:02:22 InnoDB: Mutexes and rw_locks use GCC atomic builtins 
150627 18:02:22 InnoDB: Compressed tables use zlib 1.2.7 
150627 18:02:22 InnoDB: Using Linux native AIO 
150627 18:02:22 InnoDB: Initializing buffer pool, size = 128.0M 
150627 18:02:22 InnoDB: Completed initialization of buffer pool 
150627 18:02:22 InnoDB: highest supported file format is Barracuda. 
InnoDB: Log scan progressed past the checkpoint lsn 10566571 
150627 18:02:22 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 doublewrite 
InnoDB: buffer... 
InnoDB: Doing recovery: scanned up to log sequence number 10566581 
150627 18:02:22 InnoDB: Waiting for the background threads to start 
150627 18:02:23 InnoDB: 5.5.42 started; log sequence number 10566581 
150627 18:02:23 Note Server hostname (bind-address): '0.0.0.0'; port: 3306 
150627 18:02:23 Note - '0.0.0.0' resolves to '0.0.0.0'; 
150627 18:02:23 Note Server socket created on IP: '0.0.0.0'. 
150627 18:02:23 Note Event Scheduler: Loaded 0 events 
150627 18:02:23 Note Server socket created on IP: '0.0.0.0'. 
150627 18:02:23 Note Event Scheduler: Loaded 0 events 
150627 18:02:23 Note /usr/libexec/mysqld: ready for connections. 
Version: '5.5.42' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Commu$ 
mysqld_safe Number of processes running now: 
150628 18:18:29 mysqld_safe mysqld restarted 
/usr/bin/mysqld_safe: line 165: /usr/bin/nohup: Cannot allocate memory 
150628 18:22:53 mysqld_safe Starting mysqld daemon with databases from /var/lib$ 
150628 18:22:53 Note Plugin 'FEDERATED' is disabled. 
150628 18:22:53 InnoDB: The InnoDB memory heap is disabled 
150628 18:22:53 InnoDB: Mutexes and rw_locks use GCC atomic builtins 
150628 18:22:53 InnoDB: Compressed tables use zlib 1.2.7 
150628 18:22:53 InnoDB: Using Linux native AIO 
150628 18:22:53 InnoDB: Initializing buffer pool, size = 128.0M 
150628 18:22:53 InnoDB: Completed initialization of buffer pool 
150628 18:22:53 InnoDB: highest supported file format is Barracuda. 
InnoDB: The log sequence number in ibdata files does not match 
InnoDB: the log sequence number in the ib_logfiles! 
150628 18:22:53 InnoDB: Database was not shut down normally! 
InnoDB: the log sequence number in the ib_logfiles! 
150628 18:22:53 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 doublewrite 
InnoDB: buffer... 
150628 18:22:54 InnoDB: Waiting for the background threads to start 
150628 18:22:55 InnoDB: 5.5.42 started; log sequence number 11269379 
150628 18:22:55 Note Server hostname (bind-address): '0.0.0.0'; port: 3306 
150628 18:22:55 Note - '0.0.0.0' resolves to '0.0.0.0'; 
150628 18:22:55 Note Server socket created on IP: '0.0.0.0'. 
150628 18:22:55 Note Event Scheduler: Loaded 0 events 
150628 18:22:55 Note /usr/libexec/mysqld: ready for connections. 
Version: '5.5.42' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Commu$ 
150628 18:28:10 mysqld_safe Number of processes running now: 0 
150628 18:28:13 mysqld_safe mysqld restarted 
/usr/libexec/mysqld: error while loading shared libraries: libkrb5.so.3: failed$ 

Answer 1

這是內存的問題：

/usr/bin/mysqld_safe: line 165: /usr/bin/nohup: Cannot allocate memory 

，你可以使用MySQL設置勾搭來嘗試解決這個問題，但它會更容易只使用更大的實例類型。你也可以看看如何使用RDS free tier在專用服務器上託管你的MySQL數據庫，並免費獲得備份。