Vesta Control Panel - Forum

I have a server in Digital Ocean, Ubuntu 12.04 with 512MB RAM, previously used directly without VestaCP LAMP or similar. Last week migrated to the formatted VestaCP and today was the third time that I have problem with MySQL, the service for some reason falls and can not get back. The first time I tried to restart the service by the Vesta panel or the server console and still did not work, the service only returned when restarted the server. Today I managed to restart the service directly by the server, but I'm still finding the odd stop working service. Detail: the three times were in similar times, between 6am and 7am. Follow the logs below, I hope they can help me. Thank you!

PS: just to test left the disabled backup job, it seems to me that this time something happens.
PS²: There is the possibility the server has few resources to keep VestaCP and running blog?

150516 6:55:23 [Note] Plugin 'FEDERATED' is disabled.
150516 6:55:23 InnoDB: The InnoDB memory heap is disabled
150516 6:55:23 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150516 6:55:23 InnoDB: Compressed tables use zlib 1.2.3.4
150516 6:55:23 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
150516 6:55:23 InnoDB: Completed initialization of buffer pool
150516 6:55:23 InnoDB: Fatal error: cannot allocate memory for the buffer pool
150516 6:55:23 [ERROR] Plugin 'InnoDB' init function returned error.
150516 6:55:23 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
150516 6:55:23 [ERROR] Unknown/unsupported storage engine: InnoDB
150516 6:55:23 [ERROR] Aborting
150516 6:55:23 [Note] /usr/sbin/mysqld: Shutdown complete
150516 6:55:25 [Note] Plugin 'FEDERATED' is disabled.
150516 6:55:25 InnoDB: The InnoDB memory heap is disabled
150516 6:55:25 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150516 6:55:25 InnoDB: Compressed tables use zlib 1.2.3.4
150516 6:55:25 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
150516 6:55:25 InnoDB: Completed initialization of buffer pool
150516 6:55:25 InnoDB: Fatal error: cannot allocate memory for the buffer pool
150516 6:55:25 [ERROR] Plugin 'InnoDB' init function returned error.
150516 6:55:25 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
150516 6:55:25 [ERROR] Unknown/unsupported storage engine: InnoDB
150516 6:55:25 [ERROR] Aborting
150516 6:55:25 [Note] /usr/sbin/mysqld: Shutdown complete

service mysql status
mysql stop/waiting

service mysql restart
stop: Unknown instance:
mysql start/running, process 21927

150516 10:50:18 [Note] Plugin 'FEDERATED' is disabled.
150516 10:50:18 InnoDB: The InnoDB memory heap is disabled
150516 10:50:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150516 10:50:18 InnoDB: Compressed tables use zlib 1.2.3.4
150516 10:50:18 InnoDB: Initializing buffer pool, size = 128.0M
150516 10:50:18 InnoDB: Completed initialization of buffer pool
150516 10:50:18 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!
150516 10:50:18 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...
150516 10:50:18 InnoDB: Waiting for the background threads to start
150516 10:50:19 InnoDB: 5.5.43 started; log sequence number 16602150
150516 10:50:19 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
150516 10:50:19 [Note] - '0.0.0.0' resolves to '0.0.0.0';
150516 10:50:19 [Note] Server socket created on IP: '0.0.0.0'.
150516 10:50:19 [Note] Event Scheduler: Loaded 0 events
150516 10:50:19 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.43-0ubuntu0.12.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)

Someone?

One: viewtopic.php?f=14&t=6861#p20691

Two: in your my.cnf