您的位置:首页 > 数据库 > MySQL

mysql表损坏后自己修复自动重启,cache不够影响mysql内存初始化

2014-04-23 09:27 519 查看
具体日志:

140422 15:46:40 [ERROR] /usr/local/mysql/bin/mysqld: Table './calllogs0/call_log0' is marked as crashed and should be repaired

140422 15:46:40 [Warning] Checking table:   './calllogs0/call_log0'

140422 16:11:27 mysqld_safe Number of processes running now: 0

140422 16:11:27 mysqld_safe mysqld restarted

140422 16:11:27 [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.

140422 16:11:28 InnoDB: The InnoDB memory heap is disabled

140422 16:11:28 InnoDB: Mutexes and rw_locks use GCC atomic builtins

140422 16:11:28 InnoDB: Compressed tables use zlib 1.2.3

140422 16:11:28 InnoDB: Initializing buffer pool, size = 2.0G

InnoDB: mmap(2197815296 bytes) failed; errno 12

140422 16:11:28 InnoDB: Completed initialization of buffer pool

140422 16:11:28 InnoDB: Fatal error: cannot allocate memory for the buffer pool

140422 16:11:28 [ERROR] Plugin 'InnoDB' init function returned error.

140422 16:11:28 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

140422 16:11:28 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306

140422 16:11:28 [Note]   - '0.0.0.0' resolves to '0.0.0.0';

140422 16:11:28 [Note] Server socket created on IP: '0.0.0.0'.
内容来自用户分享和网络整理,不保证内容的准确性,如有侵权内容,可联系管理员处理 点击这里给我发消息
标签: