MySQL stops randomly
MySQL stops randomly
I replied to a thread where someone is experiencing a similar problem, but I think it's best to start a new thread.
First I want to tell you that I am new to the VPS-world. I started learning and testing since 2 weeks. I tried some different panels but I find VestaCP the easiest to work with. About a week ago I started hosting my first website on a VPS. However I am having some problems.
So I have a problem with my MySQL server, it stops randomly. I searched for a solution and some people where having the same problem because their root password was incorrect in their /usr/local/vesta/conf/mysql.conf. So I changed the password and added the new password to /usr/local/vesta/conf/mysql.conf. But now I see I also have a /root/.my.cnf file. Does the password need to be changed there too? Because I am not sure if that is my old password (definitely not my new password).
When the MySQL server stops I can't restart it using the service panel on the vesta control panel. I have to restart my server to have it working correctly.
I am on a 768MB Vultr VPS (CentOS 6 x64, KVM, 1 CPU, SSD)
Currently I am hosting a small WooCommerce webshop. MySQL size: +-680KB, public_html size +- 80MB
I don't think it has to do something with ram anymore, because it was running fine before (but slow in my opinion) on a 5$ shared hosting package from Stablehost. Now it is much faster.
Some emails I received from my server:
Email 1
Subject: Error: Connection failed
Content: /usr/local/vesta/func/main.sh: line 55: [: 15 2014-12-16 02:15:02 v-update-database-disk admin admin_WPDB : integer expression expected
Email 2
Subject: admin → backup failed
Content: Can't connect to localhost
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
Free -m results:
(full) /var/log/mysqld.log:
EDIT/deleted: It looks like it wasn't full after all. I didn't notice I could change pages when I SSH on my server. I replied with the latest MySQL logs under this post. They are from yesterday and today. This morning I received the emails again.
/etc/my.cnf:
Let me know if you require more information. Please also let me know if I am sharing information that is too sensitive.
First I want to tell you that I am new to the VPS-world. I started learning and testing since 2 weeks. I tried some different panels but I find VestaCP the easiest to work with. About a week ago I started hosting my first website on a VPS. However I am having some problems.
So I have a problem with my MySQL server, it stops randomly. I searched for a solution and some people where having the same problem because their root password was incorrect in their /usr/local/vesta/conf/mysql.conf. So I changed the password and added the new password to /usr/local/vesta/conf/mysql.conf. But now I see I also have a /root/.my.cnf file. Does the password need to be changed there too? Because I am not sure if that is my old password (definitely not my new password).
When the MySQL server stops I can't restart it using the service panel on the vesta control panel. I have to restart my server to have it working correctly.
I am on a 768MB Vultr VPS (CentOS 6 x64, KVM, 1 CPU, SSD)
Currently I am hosting a small WooCommerce webshop. MySQL size: +-680KB, public_html size +- 80MB
I don't think it has to do something with ram anymore, because it was running fine before (but slow in my opinion) on a 5$ shared hosting package from Stablehost. Now it is much faster.
Some emails I received from my server:
Email 1
Subject: Error: Connection failed
Content: /usr/local/vesta/func/main.sh: line 55: [: 15 2014-12-16 02:15:02 v-update-database-disk admin admin_WPDB : integer expression expected
Email 2
Subject: admin → backup failed
Content: Can't connect to localhost
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
Free -m results:
Code: Select all
total used free shared buffers cached
Mem: 742 673 69 0 23 76
-/+ buffers/cache: 573 169
Swap: 0 0 0EDIT/deleted: It looks like it wasn't full after all. I didn't notice I could change pages when I SSH on my server. I replied with the latest MySQL logs under this post. They are from yesterday and today. This morning I received the emails again.
/etc/my.cnf:
Code: Select all
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
symbolic-links=0
max_connections=70
max_user_connections=30
wait_timeout=10
interactive_timeout=50
long_query_time=5
#log-queries-not-using-indexes
#log-slow-queries=/var/log/mysql/log-slow-queries.log
key_buffer = 16M
myisam_sort_buffer_size = 32M
join_buffer_size=1M
read_buffer_size=1M
sort_buffer_size=2M
table_cache=1024
thread_cache_size=286
interactive_timeout=25
connect_timeout=5
max_allowed_packet=1M
max_connect_errors=1000
query_cache_limit=1M
query_cache_size=8M
query_cache_type=1
tmp_table_size=16M
#innodb_use_native_aio = 0
innodb_file_per_table
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
Last edited by balboni on Fri Dec 19, 2014 10:49 am, edited 1 time in total.
Re: MySQL stops randomly
Just to give you some more information.
This is the error message I receive when trying to restart the mysqld service: "restart" "'mysqld'" failed
Today MySQL stopped again. I only noticed it when I received the same 2 emails as in my first post.
I think I receive the 2 emails just because my server can't do the cron jobs. So maybe the MySQL is even longer offline than I think.
Latest MySQL logs from yesterday and today:
This is the error message I receive when trying to restart the mysqld service: "restart" "'mysqld'" failed
Today MySQL stopped again. I only noticed it when I received the same 2 emails as in my first post.
I think I receive the 2 emails just because my server can't do the cron jobs. So maybe the MySQL is even longer offline than I think.
Latest MySQL logs from yesterday and today:
Code: Select all
141218 0:45:56 [Warning] IP address '61.147.107.66' could not be resolved: Name or service not known
141218 14:10:36 [Warning] IP address '182.254.210.147' could not be resolved: Name or service not known
141218 23:20:01 mysqld_safe Number of processes running now: 0
141218 23:20:01 mysqld_safe mysqld restarted
141218 23:20:01 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
141218 23:20:01 [Note] Plugin 'FEDERATED' is disabled.
141218 23:20:01 InnoDB: The InnoDB memory heap is disabled
141218 23:20:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141218 23:20:01 InnoDB: Compressed tables use zlib 1.2.3
141218 23:20:01 InnoDB: Using Linux native AIO
141218 23:20:01 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
141218 23:20:01 InnoDB: Completed initialization of buffer pool
141218 23:20:01 InnoDB: Fatal error: cannot allocate memory for the buffer pool
141218 23:20:01 [ERROR] Plugin 'InnoDB' init function returned error.
141218 23:20:01 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
141218 23:20:01 [ERROR] Unknown/unsupported storage engine: InnoDB
141218 23:20:01 [ERROR] Aborting
141218 23:20:01 [Note] /usr/libexec/mysqld: Shutdown complete
141218 23:20:01 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
141219 09:06:33 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
141219 9:06:33 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
141219 9:06:33 [Note] Plugin 'FEDERATED' is disabled.
141219 9:06:33 InnoDB: The InnoDB memory heap is disabled
141219 9:06:33 [Note] Plugin 'FEDERATED' is disabled.
141219 9:06:33 InnoDB: The InnoDB memory heap is disabled
141219 9:06:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141219 9:06:33 InnoDB: Compressed tables use zlib 1.2.3
141219 9:06:33 InnoDB: Using Linux native AIO
141219 9:06:33 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
141219 9:06:33 InnoDB: Completed initialization of buffer pool
141219 9:06:33 InnoDB: Fatal error: cannot allocate memory for the buffer pool
141219 9:06:33 [ERROR] Plugin 'InnoDB' init function returned error.
141219 9:06:33 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
141219 9:06:33 [ERROR] Unknown/unsupported storage engine: InnoDB
141219 9:06:33 [ERROR] Aborting
141219 9:06:33 [Note] /usr/libexec/mysqld: Shutdown complete
141219 09:06:33 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
141219 09:07:27 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
141219 9:07:27 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
141219 9:07:28 [Note] Plugin 'FEDERATED' is disabled.
141219 9:07:28 InnoDB: The InnoDB memory heap is disabled
141219 9:07:28 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141219 9:07:28 InnoDB: Compressed tables use zlib 1.2.3
141219 9:07:28 InnoDB: Using Linux native AIO
141219 9:07:28 InnoDB: Initializing buffer pool, size = 128.0M
141219 9:07:28 InnoDB: Completed initialization of buffer pool
141219 9:07:28 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!
141219 9:07:28 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...
141219 9:07:28 InnoDB: Waiting for the background threads to start
141219 9:07:29 InnoDB: 5.5.41 started; log sequence number 28702244
141219 9:07:29 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
141219 9:07:29 [Note] - '0.0.0.0' resolves to '0.0.0.0';
141219 9:07:29 [Note] Server socket created on IP: '0.0.0.0'.
141219 9:07:29 [Note] Event Scheduler: Loaded 0 events
141219 9:07:29 [Note] /usr/libexec/mysqld: ready for connections.Re: MySQL stops randomly
I have the same problem.
Re: MySQL stops randomly
I got the problem again today.. Who can help me or atleast point me in the right direction?
Results /var/log/mysqld.log today:
I will try and change the password in the /root/.my.cnf file today.
Results /var/log/mysqld.log today:
Code: Select all
141219 15:47:39 [Warning] IP address '119.148.161.110' could not be resolved: Name or service not known
141220 4:29:31 [Warning] IP address '182.254.210.147' could not be resolved: Name or service not known
141220 04:36:50 mysqld_safe Number of processes running now: 0
141220 04:36:50 mysqld_safe mysqld restarted
141220 4:36:50 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
141220 4:36:50 [Note] Plugin 'FEDERATED' is disabled.
141220 4:36:50 InnoDB: The InnoDB memory heap is disabled
141220 4:36:50 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141220 4:36:50 InnoDB: Compressed tables use zlib 1.2.3
141220 4:36:50 InnoDB: Using Linux native AIO
141220 4:36:50 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
141220 4:36:50 InnoDB: Completed initialization of buffer pool
141220 4:36:50 InnoDB: Fatal error: cannot allocate memory for the buffer pool
141220 4:36:50 [ERROR] Plugin 'InnoDB' init function returned error.
141220 4:36:50 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
141220 4:36:50 [ERROR] Unknown/unsupported storage engine: InnoDB
141220 4:36:50 [ERROR] Aborting
141220 4:36:50 [ERROR] Unknown/unsupported storage engine: InnoDB
141220 4:36:50 [ERROR] Aborting
141220 4:36:50 [Note] /usr/libexec/mysqld: Shutdown complete
141220 04:36:50 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
141220 11:57:55 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
141220 11:57:55 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
141220 11:57:55 [Note] Plugin 'FEDERATED' is disabled.
141220 11:57:55 InnoDB: The InnoDB memory heap is disabled
141220 11:57:55 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141220 11:57:55 InnoDB: Compressed tables use zlib 1.2.3
141220 11:57:55 InnoDB: Using Linux native AIO
141220 11:57:55 InnoDB: Initializing buffer pool, size = 128.0M
141220 11:57:55 InnoDB: Completed initialization of buffer pool
141220 11:57:55 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 32688809
141220 11:57:55 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 32701542
141220 11:57:55 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 $
InnoDB: Apply batch completed
141220 11:57:55 InnoDB: Waiting for the background threads to start
141220 11:57:56 InnoDB: 5.5.41 started; log sequence number 32701542
141220 11:57:56 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
141220 11:57:56 [Note] - '0.0.0.0' resolves to '0.0.0.0';
141220 11:57:56 [Note] Server socket created on IP: '0.0.0.0'.
141220 11:57:56 [Note] Event Scheduler: Loaded 0 events
141220 11:57:56 [Note] /usr/libexec/mysqld: ready for connections.Re: MySQL stops randomly
Can you please provide us with /etc/mysql/my.cnf or /etc/my.cnf and /root.my.cnf. The reason your getting email #1 & #2 is because vesta is unable to connect to mysql cause its offline.
Re: MySQL stops randomly
/etc/mysql/my.cnf and /root.my.cnf are empty.joem wrote:Can you please provide us with /etc/mysql/my.cnf or /etc/my.cnf and /root.my.cnf. The reason your getting email #1 & #2 is because vesta is unable to connect to mysql cause its offline.
If you mean /root/.my.cnf instead of /root.my.cnf than this is the file:
Code: Select all
[client]
password='#########'However my logs are still showing some weird things. Like the: "[Warning] IP address '107.160.36.136' could not be resolved: Temporary failure in name resolution" messages. I don't know, but can this have to anything with using Cloudflare? Or maybe some spammers? I get allot of comments for approval which are all spammy ones.
My MySQL logs since my last post:
Code: Select all
Version: '5.5.41' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Remi
141219 15:47:39 [Warning] IP address '119.148.161.110' could not be resolved: Name or service not known
141220 4:29:31 [Warning] IP address '182.254.210.147' could not be resolved: Name or service not known
141220 04:36:50 mysqld_safe Number of processes running now: 0
141220 04:36:50 mysqld_safe mysqld restarted
141220 4:36:50 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
141220 4:36:50 [Note] Plugin 'FEDERATED' is disabled.
141220 4:36:50 InnoDB: The InnoDB memory heap is disabled
141220 4:36:50 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141220 4:36:50 InnoDB: Compressed tables use zlib 1.2.3
141220 4:36:50 InnoDB: Using Linux native AIO
141220 4:36:50 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
141220 4:36:50 InnoDB: Completed initialization of buffer pool
141220 4:36:50 InnoDB: Fatal error: cannot allocate memory for the buffer pool
141220 4:36:50 [ERROR] Plugin 'InnoDB' init function returned error.
141220 4:36:50 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
141220 4:36:50 [ERROR] Unknown/unsupported storage engine: InnoDB
141220 4:36:50 [ERROR] Aborting
141220 4:36:50 [Note] /usr/libexec/mysqld: Shutdown complete
141220 04:36:50 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
141220 11:57:55 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
141220 11:57:55 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
141220 11:57:55 [Note] Plugin 'FEDERATED' is disabled.
141220 11:57:55 InnoDB: The InnoDB memory heap is disabled
141220 11:57:55 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141220 11:57:55 InnoDB: Compressed tables use zlib 1.2.3
141220 11:57:55 InnoDB: Using Linux native AIO
141220 11:57:55 InnoDB: Initializing buffer pool, size = 128.0M
141220 11:57:55 InnoDB: Completed initialization of buffer pool
141220 11:57:55 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 32688809
141220 11:57:55 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 32701542
141220 11:57:55 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95$
InnoDB: Apply batch completed
141220 11:57:55 InnoDB: Waiting for the background threads to start
141220 11:57:56 InnoDB: 5.5.41 started; log sequence number 32701542
141220 11:57:56 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
141220 11:57:56 [Note] - '0.0.0.0' resolves to '0.0.0.0';
141220 11:57:56 [Note] Server socket created on IP: '0.0.0.0'.
141220 11:57:56 [Note] - '0.0.0.0' resolves to '0.0.0.0';
141220 11:57:56 [Note] Server socket created on IP: '0.0.0.0'.
141220 11:57:56 [Note] Event Scheduler: Loaded 0 events
141220 11:57:56 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.41' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Remi
141220 13:44:33 [Note] /usr/libexec/mysqld: Normal shutdown
141220 13:44:33 [Note] Event Scheduler: Purging the queue. 0 events
141220 13:44:33 InnoDB: Starting shutdown...
141220 13:44:35 InnoDB: Shutdown completed; log sequence number 33235982
141220 13:44:35 [Note] /usr/libexec/mysqld: Shutdown complete
141220 13:44:35 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
141220 13:44:57 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
141220 13:44:57 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
141220 13:44:57 [Note] Plugin 'FEDERATED' is disabled.
141220 13:44:57 InnoDB: The InnoDB memory heap is disabled
141220 13:44:57 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141220 13:44:57 InnoDB: Compressed tables use zlib 1.2.3
141220 13:44:57 InnoDB: Using Linux native AIO
141220 13:44:57 InnoDB: Initializing buffer pool, size = 128.0M
141220 13:44:57 InnoDB: Completed initialization of buffer pool
141220 13:44:57 InnoDB: highest supported file format is Barracuda.
141220 13:44:57 InnoDB: Waiting for the background threads to start
141220 13:44:58 InnoDB: 5.5.41 started; log sequence number 33235982
141220 13:44:58 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
141220 13:44:58 [Note] - '0.0.0.0' resolves to '0.0.0.0';
141220 13:44:58 [Note] Server socket created on IP: '0.0.0.0'.
141220 13:44:58 [Note] Event Scheduler: Loaded 0 events
141220 13:44:58 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.41' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Remi
141220 15:11:13 [Warning] IP address '210.212.98.235' could not be resolved: Name or service not known
141221 5:06:19 [Warning] IP address '111.73.46.224' could not be resolved: Name or service not known
141221 6:12:38 [Warning] IP address '122.226.102.10' could not be resolved: Name or service not known
141221 6:42:13 [Warning] IP address '118.193.188.146' could not be resolved: Name or service not known
141221 15:15:34 [Warning] IP address '120.24.62.200' could not be resolved: Name or service not known
141221 15:28:31 [Warning] IP address '107.160.36.136' could not be resolved: Temporary failure in name resolution
141221 15:47:21 [Warning] IP address '202.109.143.16' could not be resolved: Temporary failure in name resolution
141221 15:47:22 [Warning] IP address '202.109.143.16' could not be resolved: Temporary failure in name resolution
141222 7:57:33 [Warning] IP address '182.254.210.91' could not be resolved: Name or service not known
141222 11:43:02 [Warning] IP address '182.254.210.147' could not be resolved: Name or service not known
141222 14:27:57 [Warning] IP address '107.160.36.136' could not be resolved: Temporary failure in name resolution
Code: Select all
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
symbolic-links=0
max_connections=70
max_user_connections=30
wait_timeout=10
interactive_timeout=50
long_query_time=5
#log-queries-not-using-indexes
#log-slow-queries=/var/log/mysql/log-slow-queries.log
key_buffer = 16M
myisam_sort_buffer_size = 32M
join_buffer_size=1M
read_buffer_size=1M
sort_buffer_size=2M
table_cache=1024
thread_cache_size=286
interactive_timeout=25
connect_timeout=5
max_allowed_packet=1M
max_connect_errors=1000
query_cache_limit=1M
query_cache_size=8M
query_cache_type=1
tmp_table_size=16M
tmp_table_size=16M
#innodb_use_native_aio = 0
innodb_file_per_table
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pidRe: MySQL stops randomly
Yes I did mean /root/.my.cnf sorry copy and paste error :P The problem is mysql cant start because the innodb buffer pool size cant not get ahold of 128m of ram. Try changing it from 128m to half that maybe. You can do this by adding the code below under [mysqld] in /etc/my.cnf
Code: Select all
innodb_buffer_pool_size=64MRe: MySQL stops randomly
Thank you for your help! I will change it tomorrow (very late here).
I didn't receive the emails and my site kept working the last few days. So do you think it somehow found the needed 128m ram? How could it otherwise possibly start?
I didn't receive the emails and my site kept working the last few days. So do you think it somehow found the needed 128m ram? How could it otherwise possibly start?
Re: MySQL stops randomly
You may have some ram available now. Sometimes, other programs have spikes in ram usage. Some more information can be found here.balboni wrote:Thank you for your help! I will change it tomorrow (very late here).
I didn't receive the emails and my site kept working the last few days. So do you think it somehow found the needed 128m ram? How could it otherwise possibly start?
-
david_treblig
- Posts: 1
- Joined: Fri Feb 20, 2015 4:26 pm
Re: MySQL stops randomly
If anyone finds that topic over and over again like I did when I was searching for more information, there is a really good guide on how to create a swap space (trigger your disk to be used instead of your ram when running out) on Ubuntu at DigitalOcean's community guides : https://www.digitalocean.com/community/ ... untu-14-04
The problem has stopped for now after I did this. I don't know if it's going to be enough but for now it seems to work.
The problem has stopped for now after I did this. I don't know if it's going to be enough but for now it seems to work.