My database crash with out of memory error ~1-2 times per day. Last crash was at 17:30 in logs and at 19:30 in metrics (different timezones).
Errors in mariadb.log:
181120 16:09:00 [Warning] IP address '185.156.177.144' could not be resolved: Name or service not known
181120 16:35:40 [Warning] IP address '58.221.58.248' could not be resolved: Name or service not known
181120 17:30:38 mysqld_safe Number of processes running now: 0
181120 17:30:38 mysqld_safe mysqld restarted
181120 17:30:41 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
181120 17:30:41 [Note] /usr/libexec/mysqld (mysqld 5.5.52-MariaDB) starting as process 16636 ...
181120 17:30:41 [Warning] Changed limits: max_open_files: 1024 max_connections: 70 table_cache: 472
181120 17:30:41 InnoDB: The InnoDB memory heap is disabled
181120 17:30:41 InnoDB: Mutexes and rw_locks use GCC atomic builtins
181120 17:30:41 InnoDB: Compressed tables use zlib 1.2.7
181120 17:30:41 InnoDB: Using Linux native AIO
181120 17:30:41 InnoDB: Initializing buffer pool, size = 150.0M
181120 17:30:42 InnoDB: Completed initialization of buffer pool
181120 17:30:42 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!
181120 17:30:42 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...
181120 17:30:46 InnoDB: Waiting for the background threads to start
181120 17:30:47 Percona XtraDB (http://www.percona.com) 5.5.49-MariaDB-38.0 started; log sequence number 18741266161
181120 17:30:47 [Note] Plugin 'FEEDBACK' is disabled.
181120 17:30:48 [Note] Server socket created on IP: '0.0.0.0'.
181120 17:30:49 [Note] Event Scheduler: Loaded 0 events
181120 17:30:49 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.52-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
181120 17:30:53 [ERROR] mysqld: Table './admin_wikis/wp_posts' is marked as crashed and should be repaired
181120 17:30:53 [Warning] Checking table: './admin_wikis/wp_posts'
181120 17:31:58 mysqld_safe Number of processes running now: 0
181120 17:31:58 mysqld_safe mysqld restarted
181120 17:32:01 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
181120 17:32:01 [Note] /usr/libexec/mysqld (mysqld 5.5.52-MariaDB) starting as process 16899 ...
181120 17:32:01 [Warning] Changed limits: max_open_files: 1024 max_connections: 70 table_cache: 472
181120 17:32:01 InnoDB: The InnoDB memory heap is disabled
181120 17:32:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
181120 17:32:01 InnoDB: Compressed tables use zlib 1.2.7
181120 17:32:01 InnoDB: Using Linux native AIO
181120 17:32:01 InnoDB: Initializing buffer pool, size = 150.0M
InnoDB: mmap(161447936 bytes) failed; errno 12
181120 17:32:01 InnoDB: Completed initialization of buffer pool
181120 17:32:01 InnoDB: Fatal error: cannot allocate memory for the buffer pool
181120 17:32:01 [ERROR] Plugin 'InnoDB' init function returned error.
181120 17:32:01 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
181120 17:32:01 [ERROR] mysqld: Out of memory (Needed 128917504 bytes)
181120 17:32:01 [ERROR] mysqld: Out of memory (Needed 96681984 bytes)
181120 17:32:01 [ERROR] mysqld: Out of memory (Needed 72499200 bytes)
181120 17:32:01 [Note] Plugin 'FEEDBACK' is disabled.
181120 17:32:02 [ERROR] Unknown/unsupported storage engine: InnoDB
181120 17:32:02 [ERROR] Aborting
181120 17:32:02 [Note] /usr/libexec/mysqld: Shutdown complete
There is nothing interesing in apache log in this time. Event requests count
$ sudo grep -r "GET \/" /etc/httpd/logs/domains/ | cut -d' ' -f4 | sed 's/\[//;s/\]//;s/\"//' | cut -d':' -f1-2 | sort | uniq -c
459 19/Nov/2018:03
426 19/Nov/2018:04
239 19/Nov/2018:05
350 19/Nov/2018:06
381 19/Nov/2018:07
415 19/Nov/2018:08
778 19/Nov/2018:09
500 19/Nov/2018:10
450 19/Nov/2018:11
633 19/Nov/2018:12
458 19/Nov/2018:13
527 19/Nov/2018:14
713 19/Nov/2018:15
654 19/Nov/2018:16
573 19/Nov/2018:17
413 19/Nov/2018:18
471 19/Nov/2018:19
499 19/Nov/2018:20
661 19/Nov/2018:21
452 19/Nov/2018:22
773 19/Nov/2018:23
934 20/Nov/2018:00
295 20/Nov/2018:01
369 20/Nov/2018:02
441 20/Nov/2018:03
384 20/Nov/2018:04
927 20/Nov/2018:05
524 20/Nov/2018:06
972 20/Nov/2018:07
612 20/Nov/2018:08
609 20/Nov/2018:09
677 20/Nov/2018:10
753 20/Nov/2018:11
615 20/Nov/2018:12
717 20/Nov/2018:13
474 20/Nov/2018:14
973 20/Nov/2018:15
510 20/Nov/2018:16
534 20/Nov/2018:17
415 20/Nov/2018:18
90 20/Nov/2018:19
I get some metrics:
Processes before crash:
Processes in the moment of crash:
Memory and CPU usage:
Total RAM 3.6G. Does someone have any ideas?
httpd is the largest memory user; decrease its settings, especially the number of 'children' it is willing to spawn. (Under 10 should suffice for most small installations.)
max_connections: 70 table_cache: 472 -- Cut each of those in half; this will help a little with memory allocation.
Next time the CPU hits 100%, do SHOW FULL PROCESSLIST; in MySQL. That may give you a clue of what runaway queries you have. Then we can focus on them. If that fails, turn on the slowlog; it will catch some of them.
Consider moving to an 8GB server. (Is this a cloud server?)
Related
I have 4 containers using mgt-commerce/mgt-development-environment-7.2. Basically everything runs well until I cannot access the control panel. It returns 500.
After checking the services, logs, etc, it seems like mysql is unable to start. Here is the error log captured in /var/log/mysql/error.log during starting mysql service using sudo service mysql start.
2019-09-26T23:38:43.740283Z mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2019-09-26T23:38:43.921450Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.26-29) starting as process 1576 ...
2019-09-26T23:38:43.924613Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-09-26T23:38:43.924635Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-09-26T23:38:43.924639Z 0 [Note] InnoDB: Uses event mutexes
2019-09-26T23:38:43.924642Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-09-26T23:38:43.924644Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-09-26T23:38:43.924647Z 0 [Note] InnoDB: Using Linux native AIO
2019-09-26T23:38:43.924859Z 0 [Note] InnoDB: Number of pools: 1
2019-09-26T23:38:43.924920Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-09-26T23:38:43.925849Z 0 [Note] InnoDB: Initializing buffer pool, total size = 1G, instances = 8, chunk size = 128M
2019-09-26T23:38:43.946744Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-09-26T23:38:43.955252Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-09-26T23:38:43.966654Z 0 [Note] InnoDB: Recovering partial pages from the parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite
2019-09-26T23:38:44.033822Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-09-26T23:38:44.033986Z 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
2019-09-26T23:38:44.034023Z 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
2019-09-26T23:38:44.034040Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2019-09-26T23:38:45.135220Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2019-09-26T23:38:45.135270Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2019-09-26T23:38:45.135283Z 0 [ERROR] Failed to initialize builtin plugins.
2019-09-26T23:38:45.135291Z 0 [ERROR] Aborting
2019-09-26T23:38:45.135301Z 0 [Note] Binlog end
2019-09-26T23:38:45.135371Z 0 [Note] Shutting down plugin 'CSV'
2019-09-26T23:38:45.136207Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
Is there anyone using this image ever getting this kind of error?
Update
It seems like mysql doesn't have the access to a particular file(s) or directory(ies), but I'm not sure which file(s) or directory(ies) . Here is the permission of mysql data directory:
clp#magento2dev:/$ ls -la /var/lib | grep mysql
drwxr-x--- 1 mysql mysql 4096 Sep 26 23:38 mysql
drwxrwx--- 2 mysql mysql 4096 Jul 11 15:24 mysql-files
drwxr-x--- 2 mysql mysql 4096 Jul 11 15:24 mysql-keyring
I am using Mariadb (mysql Ver 15.1 Distrib 5.5.40-MariaDB) in CentOS (CentOS Linux release 7.0.1406). I tried to restart Mariadb.
systemctl start mariadb
Job for mariadb.service failed. See 'systemctl status mariadb.service' and 'journalctl -xn' for details.
When I checked : /var/log/mysql-error.log as suggested by 'systemctl status mariadb.service'
170523 10:20:10 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
170523 10:20:10 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
170523 10:20:10 [Warning] Changed limits: max_open_files: 1024 max_connections: 214 table_cache: 400
170523 10:20:10 InnoDB: The InnoDB memory heap is disabled
170523 10:20:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170523 10:20:10 InnoDB: Compressed tables use zlib 1.2.7
170523 10:20:10 InnoDB: Using Linux native AIO
170523 10:20:11 InnoDB: Initializing buffer pool, size = 15.6G
170523 10:20:11 InnoDB: Completed initialization of buffer pool
170523 10:20:11 InnoDB: highest supported file format is Barracuda.
170523 10:20:12 InnoDB: Waiting for the background threads to start
170523 10:20:13 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 5336723441509
170523 10:20:13 [Note] Plugin 'FEEDBACK' is disabled.
170523 10:20:13 [ERROR] /usr/libexec/mysqld: unknown variable 'extra-lsndir=/var/tmp'
170523 10:20:13 [ERROR] Aborting
170523 10:20:13 InnoDB: Starting shutdown...
170523 10:20:15 InnoDB: Shutdown completed; log sequence number 5336723441509
170523 10:20:15 [Note] /usr/libexec/mysqld: Shutdown complete
170523 10:20:15 mysqld_safe mysqld from pid file /var/lib/mysql/master.compare-prices.repchecker.jp.pid ended
170523 10:21:10 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
170523 10:21:10 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
170523 10:21:10 [Warning] Changed limits: max_open_files: 1024 max_connections: 214 table_cache: 400
170523 10:21:10 InnoDB: The InnoDB memory heap is disabled
170523 10:21:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170523 10:21:10 InnoDB: Compressed tables use zlib 1.2.7
170523 10:21:10 InnoDB: Using Linux native AIO
170523 10:21:10 InnoDB: Initializing buffer pool, size = 15.6G
170523 10:21:11 InnoDB: Completed initialization of buffer pool
170523 10:21:11 InnoDB: highest supported file format is Barracuda.
170523 10:21:12 InnoDB: Waiting for the background threads to start
170523 10:21:13 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 5336723441509
170523 10:21:13 [Note] Plugin 'FEEDBACK' is disabled.
170523 10:21:13 [ERROR] /usr/libexec/mysqld: unknown variable 'extra-lsndir=/var/tmp'
170523 10:21:13 [ERROR] Aborting
.
.
.
.
PS: /var/lib/mysql directory is owned by mysql (there is one more directory mysql~ which is empty)
drwxr-xr-x 8 mysql mysql 4096 May 23 11:05 mysql
drwxr-xr-x. 3 mysql mysql 26 Feb 4 2015 mysql~
Please provide some suggestion. How can I restart my mariadb, I have important database under mariadb.
From the last line of error
[ERROR] /usr/libexec/mysqld: unknown variable 'extra-lsndir=/var/tmp'
It is clear that this variable is not known so try to comment it from /etc/my.cnf and try again.
# Point the following paths to different dedicated disks
tmpdir = /var/tmp
extra-lsndir = /var/tmp ------> Comment this line
target-dir=/var/tmp
I hope it will help.
I have a server running wordpress on it.
It is running well these days, but today I found it can not connect database.
So I checked server, found mysql service was shutdown.
Then I restart , but it only work for a while, after some seconds, it shutdown again.
This is mysql log:
160508 10:07:36 [Warning] IP address '222.186.59.174' could not be resolved: Name or service not known
160508 14:08:14 [Warning] IP address '210.209.127.33' could not be resolved: Name or service not known
160508 23:08:15 [Warning] IP address '183.63.89.196' could not be resolved: Name or service not known
160509 16:08:02 [Warning] IP address '198.55.114.190' has been resolved to the host name '198.55.114.190.static.quadranet.com', which resembles IPv4-address itself.
160510 8:30:34 [Warning] IP address '222.186.134.25' could not be resolved: Name or service not known
160510 12:39:02 [Warning] IP address '118.193.255.253' could not be resolved: Name or service not known
160510 16:06:36 [Warning] IP address '118.193.218.65' could not be resolved: Name or service not known
160511 0:02:03 [Warning] IP address '116.255.183.230' could not be resolved: Name or service not known
160511 00:39:09 mysqld_safe Number of processes running now: 0
160511 00:39:09 mysqld_safe mysqld restarted
160511 0:39:10 [Note] /usr/libexec/mysqld (mysqld 5.5.47-MariaDB) starting as process 24298 ...
160511 0:39:42 InnoDB: The InnoDB memory heap is disabled
160511 0:39:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160511 0:39:42 InnoDB: Compressed tables use zlib 1.2.7
160511 0:39:42 InnoDB: Using Linux native AIO
160511 0:39:42 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137756672 bytes) failed; errno 12
160511 0:39:42 InnoDB: Completed initialization of buffer pool
160511 0:39:42 InnoDB: Fatal error: cannot allocate memory for the buffer pool
160511 0:39:42 [ERROR] Plugin 'InnoDB' init function returned error.
160511 0:39:42 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160511 0:39:42 [ERROR] mysqld: Out of memory (Needed 128917504 bytes)
160511 0:39:42 [ERROR] mysqld: Out of memory (Needed 96681984 bytes)
160511 0:39:42 [ERROR] mysqld: Out of memory (Needed 72499200 bytes)
160511 00:39:44 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
160511 17:11:08 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160511 17:11:08 [Note] /usr/libexec/mysqld (mysqld 5.5.47-MariaDB) starting as process 24894 ...
160511 17:11:08 InnoDB: The InnoDB memory heap is disabled
160511 17:11:08 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160511 17:11:08 InnoDB: Compressed tables use zlib 1.2.7
160511 17:11:08 InnoDB: Using Linux native AIO
160511 17:11:08 InnoDB: Initializing buffer pool, size = 128.0M
160511 17:11:08 InnoDB: Completed initialization of buffer pool
160511 17:11:08 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!
160511 17:11:08 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...
160511 17:11:08 InnoDB: Waiting for the background threads to start
160511 17:11:09 Percona XtraDB (http://www.percona.com) 5.5.46-MariaDB-37.6 started; log sequence number 8239814
160511 17:11:09 [Note] Plugin 'FEEDBACK' is disabled.
160511 17:11:09 [Note] Server socket created on IP: '0.0.0.0'.
160511 17:11:09 [Note] Event Scheduler: Loaded 0 events
160511 17:11:09 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.47-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
160511 17:12:21 mysqld_safe Number of processes running now: 0
160511 17:12:21 mysqld_safe mysqld restarted
160511 17:12:21 [Note] /usr/libexec/mysqld (mysqld 5.5.47-MariaDB) starting as process 25104 ...
160511 17:12:21 InnoDB: The InnoDB memory heap is disabled
160511 17:12:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160511 17:12:21 InnoDB: Compressed tables use zlib 1.2.7
160511 17:12:21 InnoDB: Using Linux native AIO
160511 17:12:21 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137756672 bytes) failed; errno 12
160511 17:12:21 InnoDB: Completed initialization of buffer pool
160511 17:12:21 InnoDB: Fatal error: cannot allocate memory for the buffer pool
160511 17:12:21 [ERROR] Plugin 'InnoDB' init function returned error.
160511 17:12:21 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160511 17:12:21 [ERROR] mysqld: Out of memory (Needed 128917504 bytes)
160511 17:12:21 [ERROR] mysqld: Out of memory (Needed 96681984 bytes)
160511 17:12:21 [ERROR] mysqld: Out of memory (Needed 72499200 bytes)
160511 17:12:21 [Note] Plugin 'FEEDBACK' is disabled.
160511 17:12:21 [ERROR] Unknown/unsupported storage engine: InnoDB
160511 17:12:21 [ERROR] Aborting
160511 17:12:21 [Note] /usr/libexec/mysqld: Shutdown complete
160511 17:12:21 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
I always see there are a lot failed login attempt when I ssh to my server, and you can see there are many ip in log, is attackers caused this problem or my server has been attacked? ?
If not, what happend to my server?
Please check your memory allocation on server.
Real cause of this problem in error log lines below:
160511 17:12:21 [ERROR] mysqld: Out of memory (Needed 128917504 bytes)
160511 17:12:21 [ERROR] mysqld: Out of memory (Needed 96681984 bytes)
160511 17:12:21 [ERROR] mysqld: Out of memory (Needed 72499200 bytes)
My site is on Wordpress and is hosted on a VPS server. The traffic is not much but the database connect error is displayed many times, and then I had to restart MySQL.
I've checked the MySQL error file log. Here is a certain portion of the log.
140310 01:13:26 mysqld_safe mysqld from pid file /var/lib/mysql/server.gosoftnep.com.pid ended
140310 01:13:26 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140310 1:13:26 [Note] Plugin 'FEDERATED' is disabled.
140310 1:13:26 InnoDB: The InnoDB memory heap is disabled
140310 1:13:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140310 1:13:26 InnoDB: Compressed tables use zlib 1.2.3
140310 1:13:26 InnoDB: Using Linux native AIO
140310 1:13:26 InnoDB: Initializing buffer pool, size = 128.0M
140310 1:13:26 InnoDB: Completed initialization of buffer pool
140310 1:13:26 InnoDB: highest supported file format is Barracuda.
140310 1:13:26 InnoDB: Waiting for the background threads to start
140310 1:13:27 InnoDB: 5.5.36 started; log sequence number 12082242998
140310 1:13:27 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140310 1:13:27 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140310 1:13:27 [Note] Server socket created on IP: '0.0.0.0'.
140310 1:13:27 [Note] Event Scheduler: Loaded 0 events
140310 1:13:27 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.36-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
140310 01:13:32 mysqld_safe A mysqld process already exists
140310 5:52:48 [Warning] IP address '58.118.152.8' could not be resolved: Temporary failure in name resolution
140310 12:27:37 mysqld_safe Number of processes running now: 0
140310 12:27:38 mysqld_safe mysqld restarted
140310 12:27:44 [Note] Plugin 'FEDERATED' is disabled.
140310 12:27:45 InnoDB: The InnoDB memory heap is disabled
140310 12:27:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140310 12:27:45 InnoDB: Compressed tables use zlib 1.2.3
140310 12:27:45 InnoDB: Using Linux native AIO
140310 12:27:47 InnoDB: Initializing buffer pool, size = 128.0M
140310 12:27:49 InnoDB: Completed initialization of buffer pool
140310 12:27:50 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 12354557593
140310 12:27:52 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 12354588661
140310 12:28:05 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 96 97 98 99
InnoDB: Apply batch completed
140310 12:28:07 InnoDB: Waiting for the background threads to start
140310 12:28:08 InnoDB: 5.5.36 started; log sequence number 12354588661
140310 12:28:08 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140310 12:28:08 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140310 12:28:08 [Note] Server socket created on IP: '0.0.0.0'.
140310 12:28:12 [Note] Event Scheduler: Loaded 0 events
140310 12:28:12 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.36-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
140311 11:51:59 [Warning] IP address '61.160.249.239' could not be resolved: Name or service not known
140312 9:23:21 [Warning] IP address '183.60.107.205' could not be resolved: Name or service not known
140313 0:33:47 [Warning] IP address '221.228.231.59' could not be resolved: Name or service not known
140313 7:33:05 [Warning] IP address '61.147.103.160' could not be resolved: Name or service not known
140313 20:42:42 [Warning] IP address '124.89.32.242' could not be resolved: Name or service not known
140313 23:33:38 mysqld_safe Number of processes running now: 0
140313 23:33:38 mysqld_safe mysqld restarted
140313 23:34:09 [Note] Plugin 'FEDERATED' is disabled.
140313 23:34:14 InnoDB: The InnoDB memory heap is disabled
140313 23:34:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140313 23:34:14 InnoDB: Compressed tables use zlib 1.2.3
140313 23:34:14 InnoDB: Using Linux native AIO
140313 23:34:17 InnoDB: Initializing buffer pool, size = 128.0M
140313 23:34:20 InnoDB: Completed initialization of buffer pool
140313 23:34:30 mysqld_safe mysqld from pid file /var/lib/mysql/server.gosoftnep.com.pid ended
140314 02:55:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140314 2:55:10 [Note] Plugin 'FEDERATED' is disabled.
140314 2:55:10 InnoDB: The InnoDB memory heap is disabled
140314 2:55:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140314 2:55:10 InnoDB: Compressed tables use zlib 1.2.3
140314 2:55:10 InnoDB: Using Linux native AIO
140314 2:55:10 InnoDB: Initializing buffer pool, size = 128.0M
140314 2:55:10 InnoDB: Completed initialization of buffer pool
140314 2:55:10 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 14587500130
140314 2:55:10 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 14587535674
140314 2:55:11 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 96 97 98 99
InnoDB: Apply batch completed
140314 2:55:11 InnoDB: Waiting for the background threads to start
140314 2:55:12 InnoDB: 5.5.36 started; log sequence number 14587535674
140314 2:55:12 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140314 2:55:12 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140314 2:55:12 [Note] Server socket created on IP: '0.0.0.0'.
140314 2:55:12 [Note] Event Scheduler: Loaded 0 events
140314 2:55:12 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.36-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
I do not understand anything about this. Could anyone explain the issue to me or suggest a fix?
I am having some problems with MySQL - the service has stopped and will not restart.
I have an XAMPP stack running MediaWiki which is what uses the MySQL database. The server itself is a VM running Windows 2003 SP2 with 512MB RAM.
Below is an extract from the mysql_error.log
121120 16:11:46 [Note] Plugin 'FEDERATED' is disabled.
121120 16:11:46 InnoDB: The InnoDB memory heap is disabled
121120 16:11:46 InnoDB: Mutexes and rw_locks use Windows interlocked functions
121120 16:11:46 InnoDB: Compressed tables use zlib 1.2.3
121120 16:11:46 InnoDB: Initializing buffer pool, size = 16.0M
121120 16:11:46 InnoDB: Completed initialization of buffer pool
121120 16:11:46 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 28821623
121120 16:11:47 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 28825154
121120 16:11:47 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 96 97 98 99
InnoDB: Apply batch completed
121120 16:11:48 InnoDB: Waiting for the background threads to start
121120 16:11:49 InnoDB: 1.1.8 started; log sequence number 28825154
121120 16:11:49 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
121120 16:11:49 [Note] - '0.0.0.0' resolves to '0.0.0.0';
121120 16:11:49 [Note] Server socket created on IP: '0.0.0.0'.
121120 16:11:49 [Note] Event Scheduler: Loaded 0 events
121120 16:11:49 [Note] d:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.25a' socket: '' port: 3306 MySQL Community Server (GPL)
121120 16:16:41 [Note] Plugin 'FEDERATED' is disabled.
121120 16:16:41 InnoDB: The InnoDB memory heap is disabled
121120 16:16:41 InnoDB: Mutexes and rw_locks use Windows interlocked functions
121120 16:16:41 InnoDB: Compressed tables use zlib 1.2.3
121120 16:16:41 InnoDB: Initializing buffer pool, size = 16.0M
121120 16:16:41 InnoDB: Completed initialization of buffer pool
121120 16:16:41 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!
121120 16:16:41 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...
121120 16:16:42 InnoDB: Waiting for the background threads to start
121120 16:16:43 InnoDB: 1.1.8 started; log sequence number 28841927
121120 16:16:43 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
121120 16:16:43 [Note] - '0.0.0.0' resolves to '0.0.0.0';
121120 16:16:43 [Note] Server socket created on IP: '0.0.0.0'.
121120 16:16:43 [Note] Event Scheduler: Loaded 0 events
121120 16:16:43 [Note] d:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.25a' socket: '' port: 3306 MySQL Community Server (GPL)
Fixes Attempted:
Tried starting from services - error 1067 - "The Process Terminated unexpectedly"
Tried restarting the server itself - no good
Tried moving the ib_logfile0 and ib_logfile1 files from directory and restarting server no good
Tried killing the PID of MySQL from command prompt in case it was still running but it was not running.
If anybody could point me in the right direction it would be much appreciated.
NB> I am also trying to get the RAM of the server increased in case that is the issue. At the moment of the 512MB only about 90MB is free.
thanks
Dwayne