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.

mysql error
#1
mysql error
My server went down.After i rebooted it it was fine.This happened in 14:52.In the mysql error log i got this:
150508 14:52:04 [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.
150508 14:52:04 [Note] Plugin 'FEDERATED' is disabled.
150508 14:52:04 InnoDB: The InnoDB memory heap is disabled
150508 14:52:04 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150508 14:52:04 InnoDB: Compressed tables use zlib 1.2.8
150508 14:52:04 InnoDB: Using Linux native AIO
150508 14:52:04 InnoDB: Initializing buffer pool, size = 128.0M
150508 14:52:04 InnoDB: Completed initialization of buffer pool
150508 14:52:04 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 7376111212
150508 14:52:04 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 7376600313
150508 14:52:04 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 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 96 97 98 99
InnoDB: Apply batch completed
150508 14:52:05 InnoDB: Waiting for the background threads to start
150508 14:52:06 InnoDB: 5.5.41 started; log sequence number 7376600313
150508 14:52:06 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
150508 14:52:06 [Note] - '127.0.0.1' resolves to '127.0.0.1';
150508 14:52:06 [Note] Server socket created on IP: '127.0.0.1'.
150508 14:52:06 [Note] Event Scheduler: Loaded 0 events
150508 14:52:06 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.41-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
150508 14:52:06 [ERROR] /usr/sbin/mysqld: Table './zoom23_newsfor/wp_posts' is marked as crashed and should be repaired
150508 14:52:06 [Warning] Checking table: './zoom23_newsfor/wp_posts'
150508 14:52:07 [ERROR] /usr/sbin/mysqld: Table './zoom23_newsfor/wp_options' is marked as crashed and should be repaired
150508 14:52:07 [Warning] Checking table: './zoom23_newsfor/wp_options'
150508 14:52:09 [ERROR] /usr/sbin/mysqld: Table './zoom23_newsfor/wp_terms' is marked as crashed and should be repaired
150508 14:52:09 [Warning] Checking table: './zoom23_newsfor/wp_terms'
150508 14:52:09 [ERROR] /usr/sbin/mysqld: Table './zoom23_newsfor/wp_term_taxonomy' is marked as crashed and should be repaired
150508 14:52:09 [Warning] Checking table: './zoom23_newsfor/wp_term_taxonomy'
150508 14:52:09 [ERROR] /usr/sbin/mysqld: Table './zoom23_newsfor/wp_term_relationships' is marked as crashed and should be repaired
150508 14:52:09 [Warning] Checking table: './zoom23_newsfor/wp_term_relationships'
150508 14:52: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.
150508 14:52:13 [Note] Plugin 'FEDERATED' is disabled.
150508 14:52:13 InnoDB: The InnoDB memory heap is disabled
150508 14:52:13 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150508 14:52:13 InnoDB: Compressed tables use zlib 1.2.8
150508 14:52:13 InnoDB: Using Linux native AIO
150508 14:52:13 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
150508 14:52:13 InnoDB: Completed initialization of buffer pool
150508 14:52:13 InnoDB: Fatal error: cannot allocate memory for the buffer pool
150508 14:52:13 [ERROR] Plugin 'InnoDB' init function returned error.
150508 14:52:13 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
150508 14:52:13 [ERROR] Unknown/unsupported storage engine: InnoDB
150508 14:52:13 [ERROR] Aborting

150508 14:52:13 [Note] /usr/sbin/mysqld: Shutdown complete

150508 14:52:14 [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.
150508 14:52:14 [Note] Plugin 'FEDERATED' is disabled.
150508 14:52:14 InnoDB: The InnoDB memory heap is disabled
150508 14:52:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150508 14:52:14 InnoDB: Compressed tables use zlib 1.2.8
150508 14:52:14 InnoDB: Using Linux native AIO
150508 14:52:14 InnoDB: Initializing buffer pool, size = 128.0M
My apache log file:
[Sun May 03 06:35:02.791614 2015] [:notice] [pid 1152] mod_bw : Memory Allocated 0 bytes (each conf takes 48 bytes)
[Sun May 03 06:35:02.791670 2015] [:notice] [pid 1152] mod_bw : Version 0.92 - Initialized [0 Confs]
[Sun May 03 06:35:02.936588 2015] [mpm_prefork:notice] [pid 1152] AH00163: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
[Sun May 03 06:35:02.936647 2015] [core:notice] [pid 1152] AH00094: Command line: '/usr/sbin/apache2'
[Mon May 04 17:06:21.189107 2015] [core:notice] [pid 1152] AH00051: child pid 2860 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Fri May 08 14:51:59.645972 2015] [mpm_prefork:error] [pid 1152] (12)Cannot allocate memory: AH00159: fork: Unable to fork new process
[crit] Memory allocation failed, aborting process.
[crit] Memory allocation failed, aborting process.
[Fri May 08 14:52:09.657513 2015] [mpm_prefork:error] [pid 1152] (12)Cannot allocate memory: AH00159: fork: Unable to fork new process
[Fri May 08 14:52:19.751063 2015] [core:notice] [pid 1152] AH00052: child pid 30311 exit signal Segmentation fault (11)
[Fri May 08 14:52:19.751466 2015] [core:notice] [pid 1152] AH00051: child pid 30313 exit signal Aborted (6), possible coredump in /etc/apache2
[Fri May 08 14:52:19.751503 2015] [core:notice] [pid 1152] AH00052: child pid 30451 exit signal Aborted (6)
[Fri May 08 18:02:20.482067 2015] [mpm_prefork:notice] [pid 1152] AH00169: caught SIGTERM, shutting down
[Fri May 08 18:02:33.778432 2015] [:notice] [pid 1148] mod_bw : Memory Allocated 0 bytes (each conf takes 48 bytes)
[Fri May 08 18:02:33.778733 2015] [:notice] [pid 1148] mod_bw : Version 0.92 - Initialized [0 Confs]
[Fri May 08 18:02:33.936210 2015] [mpm_prefork:notice] [pid 1148] AH00163: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
[Fri May 08 18:02:33.936291 2015] [core:notice] [pid 1148] AH00094: Command line: '/usr/sbin/apache2'
Reply
Thanks given by:
#2
RE: mysql error
Hello zoom23,
Check this: http://www.webtrafficexchange.com/solved...uffer-pool this is the most common cause of MySQL crash.

Reading your log (thank you for posting it Smile ) you can verifiy it is a memory issue:
Code:
150508 14:52:13 InnoDB: Fatal error: cannot allocate memory for the buffer pool

Also read this post http://forums.sentora.org/showthread.php...525&page=2 as the user had the same issue.


Hope this helps Smile
My Sentora Resources
[Module] Mail Quota Count | Vagrant Box with Sentora

[Image: vanguardly-logo-micro.png]
Graphic and Web Design. Development.
www.vanguardly.com


Reply
Thanks given by: zoom23
#3
RE: mysql error
I see also you have tables to fix with WP:

Quote:150508 14:52:06 [ERROR] /usr/sbin/mysqld: Table './zoom23_newsfor/wp_posts' is marked as crashed and should be repaired
150508 14:52:06 [Warning] Checking table: './zoom23_newsfor/wp_posts'
150508 14:52:07 [ERROR] /usr/sbin/mysqld: Table './zoom23_newsfor/wp_options' is marked as crashed and should be repaired
150508 14:52:07 [Warning] Checking table: './zoom23_newsfor/wp_options'
150508 14:52:09 [ERROR] /usr/sbin/mysqld: Table './zoom23_newsfor/wp_terms' is marked as crashed and should be repaired
150508 14:52:09 [Warning] Checking table: './zoom23_newsfor/wp_terms'
150508 14:52:09 [ERROR] /usr/sbin/mysqld: Table './zoom23_newsfor/wp_term_taxonomy' is marked as crashed and should be repaired
150508 14:52:09 [Warning] Checking table: './zoom23_newsfor/wp_term_taxonomy'
150508 14:52:09 [ERROR] /usr/sbin/mysqld: Table './zoom23_newsfor/wp_term_relationships' is marked as crashed and should be repaired
150508 14:52:09 [Warning] Checking table: './zoom23_newsfor/wp_term_relationships'


InnoDB engine is not starting too. Check ram use & try fixing the tables.

Also check disk space.

M B
No support using PM (Auto adding to IGNORE list!), use the forum. 
How to ask

10$ free to start your VPS
Reply
Thanks given by: zoom23
#4
RE: mysql error
Me.B you always see a lot more than me Tongue and thats good Smile I just need to pay more attention Smile
My Sentora Resources
[Module] Mail Quota Count | Vagrant Box with Sentora

[Image: vanguardly-logo-micro.png]
Graphic and Web Design. Development.
www.vanguardly.com


Reply
Thanks given by:


Possibly Related Threads…
Thread Author Replies Views Last Post
Repo update error hostingms 3 6 ,606 02-14-2024, 09:20 AM
Last Post: TGates
apt-get install mod_ssl ERROR CMs222 9 27 ,816 11-11-2022, 09:14 PM
Last Post: zustudios
Sentora debug and error files johnnyp 0 1 ,518 10-27-2022, 06:16 PM
Last Post: johnnyp

Forum Jump:


Users browsing this thread: 1 Guest(s)