This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Using Droplet 512MB MySQL is Crashing very often
#3
RE: Using Droplet 512MB MySQL is Crashing very often
(05-06-2017, 03:43 AM)TGates Wrote: You need to review the logs to find out exactly why MySQL is shutting down.
(/var/logs/, /var/sentora/logs/)
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
InnoDB: buffer...
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.

Thanks!
Kreotuweb ---- Web solution in cuba.--- Web development & Web Design -- Hosting

[Image: K2w-logo.jpg]
Reply
Thanks given by:


Messages In This Thread
RE: Using Droplet 512MB MySQL is Crashing very often - by elpapoelg - 05-06-2017, 04:01 AM

Possibly Related Threads…
Thread Author Replies Views Last Post
MySQL Database user prefix MosleyCale 1 4 ,976 10-17-2020, 09:11 PM
Last Post: Ron-e
Senator crash problem with mysql provokas 3 9 ,711 08-20-2020, 04:11 AM
Last Post: Your Creator
MySQL remote access... pixelbat 11 38 ,280 05-02-2020, 07:40 PM
Last Post: upendra.sahu1990@gmail.com

Forum Jump:


Users browsing this thread: 1 Guest(s)