(05-06-2017, 03:43 AM)TGates Wrote: You need to review the logs to find out exactly why MySQL is shutting down.
You may also want to look into upgrading to at least 1gb ram also.
Thanks your help
that was what I find in var/log/mysql/error.log
170502 7:38:13 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170502 7:38:13 [Note] Plugin 'FEDERATED' is disabled.
170502 7:38:13 InnoDB: The InnoDB memory heap is disabled
170502 7:38:13 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170502 7:38:13 InnoDB: Compressed tables use zlib 1.2.8
170502 7:38:13 InnoDB: Using Linux native AIO
170502 7:38:13 InnoDB: Initializing buffer pool, size = 32.0M
170502 7:38:13 InnoDB: Completed initialization of buffer pool
170502 7:38:13 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!
170502 7:38:13 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
170502 7:38:13 InnoDB: Waiting for the background threads to start
170502 7:38:14 InnoDB: 5.5.54 started; log sequence number 577003798
170502 7:38:14 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
170502 7:38:14 [Note] - '127.0.0.1' resolves to '127.0.0.1';
170502 7:38:14 [Note] Server socket created on IP: '127.0.0.1'.
170502 7:38:14 [Note] Event Scheduler: Loaded 0 events
170502 7:38:14 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.54-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Can you help me to interpretate the log to find the specific problem.
In this moment I can not affor a droplet with 1GB RAM. For that reason I setup the swap space to see if it improve the server funtioning.