如題。
煩死了，WP Super Cache，Memcached 都設定了。。新站根本沒流量，網站掛在那里就自然奔潰了，求大佬幫我看看謝謝。二進制日志已經關了。性能都設定的合理的。以下是剛剛崩潰的mysql報錯日志
Key caches:
default
Buffer_size: 67108864
Block_size: 1024
Division_limit: 100
Age_limit: 300
blocks used: 14
not flushed: 0
w_requests: 326
writes: 174
r_requests: 3672
reads: 12
handler status:
read_key: 37591
read_next: 17554
read_rnd 3908
read_first: 219
write: 11527
delete 1
update: 3727
Table status:
Opened tables: 58
Open tables: 51
Open files: 27
Open streams: 0
Alarm status:
Active alarms: 0
Max used alarms: 0
Next alarm time: 0
Memory status:
Non-mmapped space allocated from system: 36569088
Number of free chunks: 345
Number of fastbin blocks: 55
Number of mmapped regions: 16
Space in mmapped regions: 145997824
Maximum total allocated space: 0
Space available in freed fastbin blocks: 3680
Total allocated space: 12922496
Total free space: 23646592
Top-most, releasable space: 3766864
Estimated memory (with thread stack): 182566912
Events status:
LLA = Last Locked At LUA = Last Unlocked At
WOC = Waiting On Condition DL = Data Locked
Event scheduler status:
State : INITIALIZED
Thread id : 0
LLA : n/a:0
LUA : n/a:0
WOC : NO
Workers : 0
Executed : 0
Data locked: NO
Event queue status:
Element count : 0
Data locked : NO
Attempting lock : NO
LLA : init_queue:139
LUA : init_queue:149
WOC : NO
Next activation : never
200503 18:28:04 [Note] Plugin 'FEDERATED' is disabled.
200503 18:28:04 InnoDB: The InnoDB memory heap is disabled
200503 18:28:04 InnoDB: Mutexes and rw_locks use GCC atomic builtins
200503 18:28:04 InnoDB: Compressed tables use zlib 1.2.11
200503 18:28:04 InnoDB: Using Linux native AIO
200503 18:28:04 InnoDB: Initializing buffer pool, size = 256.0M
InnoDB: mmap(274726912 bytes) failed; errno 12
200503 18:28:04 InnoDB: Completed initialization of buffer pool
200503 18:28:04 InnoDB: Fatal error: cannot allocate memory for the buffer pool
200503 18:28:04 [ERROR] Plugin 'InnoDB' init function returned error.
200503 18:28:04 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
200503 18:28:04 [ERROR] Unknown/unsupported storage engine: InnoDB
200503 18:28:04 [ERROR] Aborting
200503 18:28:04 [Note] /wwwrver/mysql/bin/mysqld: Shutdown complete
200503 19:14:46 [Note] Plugin 'FEDERATED' is disabled.
200503 19:14:46 InnoDB: The InnoDB memory heap is disabled
200503 19:14:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins
200503 19:14:46 InnoDB: Compressed tables use zlib 1.2.11
200503 19:14:46 InnoDB: Using Linux native AIO
200503 19:14:46 InnoDB: Initializing buffer pool, size = 256.0M
200503 19:14:46 InnoDB: Completed initialization of buffer pool
200503 19:14:46 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 173949303
200503 19:14:46 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 175137706
200503 19:14:46 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 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
200503 19:14:46 InnoDB: Waiting for the background threads to start
200503 19:14:47 InnoDB: 5.5.62 started; log sequence number 175137706
200503 19:14:47 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
200503 19:14:47 [Note] - '0.0.0.0' resolves to '0.0.0.0';
200503 19:14:47 [Note] Server socket created on IP: '0.0.0.0'.
200503 19:14:47 [Note] Event Scheduler: Loaded 0 events
200503 19:14:47 [Note] /wwwrver/mysql/bin/mysqld: ready for connections.
Version: '5.5.62-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution
轉載請註明出處，本文鏈接：https://www.uj5u.com/shujuku/36271.html
標籤：疑難問題
上一篇：基于時滯動力學
下一篇：SQL兩個表查詢計算生成另一個表