简体   繁体   English

MySQL服务器无法在PowerPC架构上启动

[英]MySQL Server Fails to Start on PowerPC Architecture

I downloaded the source code of MySQL-5.5.34 and compiled it according to the instructions. 我下载了MySQL-5.5.34的源代码,并根据说明进行了编译。 Then in the /usr/local/mysql/bin folder I did ./mysqld_safe --user=root & The mysql server started and closed immediately. 然后在/ usr / local / mysql / bin文件夹中执行./mysqld_safe --user = root和 mysql服务器立即启动并关闭。

The /usr/local/mysql/data/p2020rdb.err reads /usr/local/mysql/data/p2020rdb.err读取

mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 
The InnoDB memory heap is disabled 
Mutexes and rw_locks use GCC atomic builtins 
Compressed tables use zlib 1.2.8 
    . 
    . 
    . 
    . 
File './mysql-bin.000011' not found ( Errcode: 2) 
Failed to open log (file './mysql-bin.000011', errno 2) 
Could not open log file 
Can't init tc log 
Aborting 

InnoDB: Starting Shutdown + 
InnoDB: Shutdown completed: log sequence number 

I will greatly appreciate any help on this problem. 对于这个问题的任何帮助,我将不胜感激。

Basically, MySQL is looking in the mysql-bin.index file and it cannot find the log files that are listed within the index. 基本上,MySQL在mysql-bin.index文件中查找,并且找不到在索引中列出的日志文件。 This will keep MySQL from starting, but the fix is quick and easy. 这将阻止MySQL的启动,但是修复很容易。 You have two options: 您有两种选择:

  1. Edit the index file You can edit the mysql-bin.index file in a text editor of your choice and remove the references to any logs which don't exist on the filesystem any longer. 编辑索引文件您可以在mysql-bin.index的文本编辑器中编辑mysql-bin.index文件,并删除对文件系统上不再存在的任何日志的引用。 Once you're done, save the index file and start MySQL. 完成后,保存索引文件并启动MySQL。

  2. Take away the index file Move or delete the index file and start MySQL. 带走索引文件移动或删除索引文件并启动MySQL。 This will cause MySQL to reset its binary log numbering scheme, so if this is important to you, you may want to choose the previous option. 这将导致MySQL重置其二进制日志编号方案,因此,如果这对您很重要,则可能需要选择上一个选项。

So how do you prevent this from happening? 那么如何防止这种情况发生呢? Use the PURGE MASTER LOGS statement and allow MySQL to delete its logs on its own terms. 使用PURGE MASTER LOGS语句,并允许MySQL根据自己的条件删除其日志。 If you're concerned about log files piling up, adjust the expire_logs_days variable in your /etc/my.cnf. 如果您担心日志文件堆积,请在/etc/my.cnf.调整expire_logs_days变量/etc/my.cnf.

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM