Fedora 11 BugZilla出現(xiàn)max_allowed_packet is readonly
Jun 07, 2016 pm 04:55 PMFedora 11上安裝BugZilla出現(xiàn) max_allowed_packet is read-only問題的解決方法問題描述:當(dāng)我運(yùn)行已經(jīng)安裝完所有的perl模塊以及M
Fedora 11上安裝BugZilla出現(xiàn) max_allowed_packet is read-only問題的解決方法
問題描述:
當(dāng)我運(yùn)行已經(jīng)安裝完所有的perl模塊以及MySQL數(shù)據(jù)庫后,./checksetup.pl時錯誤提示如下:
DBD::mysql::db do failed: SESSION variable 'max_allowed_packet' is read-only. Use SET GLOBAL to assign the value [for Statement "SET SESSION max_allowed_packet = 3276750"] at Bugzilla/DB/Mysql.pm line 113
?
Bugzilla::DB::Mysql::new('Bugzilla::DB::Mysql', 'bugs', 'bugs', 'localhost', 'bugs', 0, '') called at Bugzilla/DB.pm line 111
Bugzilla::DB::_connect('mysql', 'localhost', 'bugs', 0, '', 'bugs', 'bugs') called at Bugzilla/DB.pm line 96
Bugzilla::DB::connect_main() called at Bugzilla.pm line 317
Bugzilla::dbh('Bugzilla') called at ./checksetup.pl line 142
解決方法:
一、關(guān)閉selinux
因?yàn)樽詮腒ernel 2.6開始,就有了SElinux(Security Enhance linux)安全加強(qiáng)的Linux. RHEL 4就有了SElinux的實(shí)現(xiàn)。Fedora11里當(dāng)然也會
有SElinux,雖然安全,如果不滿足其策略,它會阻止很多操作。所以干脆把它關(guān)掉。
編輯/etc/selinux/config文件
1.vi /etc/selinux/config
2.將SELINUX=enforcing改為SELINUX=disabled
3.:wq(保存退出)
4.reboot(重啟)
二、注釋對max_allow_packet的修改語句。
max_allow_packet本身的含義是客戶端與服務(wù)器端交互數(shù)據(jù)最大值。默認(rèn)是1G。
我在查閱Mysql menu時,有這樣一句話:
On the client side, max_allowed_packet has a default of 1GB. ..... Beginning with MySQL 5.0.3, it also has a read-only
session scope
意思就是說max_allowed_packet has a default of 1GB.自從MySQL 5.0.3開始,,這個參數(shù)就被設(shè)置為只讀了。而Fedora 11默認(rèn)安裝的是MySQL
5.1.3。而Bugzilla/DB/Mysql.pm的還想修改max_allowed_packet=300M,這個是不行。
[for Statement "SET SESSION max_allowed_packet = 3276750"] at Bugzilla/DB/Mysql.pm line 113
所以按照提示我找到了Bugzilla/DB/Mysql.pm line 113行:
$self->do("SET SESSION max_allowed_packet = $max_allowed_packet");
并把這樣注釋掉,也就是在這行前面加上#。形式如下:
#$self->do("SET SESSION max_allowed_packet = $max_allowed_packet");
三、運(yùn)行./checksetup.pl
大功告成。

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

GTID (Global Transaction Identifier) ??solves the complexity of replication and failover in MySQL databases by assigning a unique identity to each transaction. 1. It simplifies replication management, automatically handles log files and locations, allowing slave servers to request transactions based on the last executed GTID. 2. Ensure consistency across servers, ensure that each transaction is applied only once on each server, and avoid data inconsistency. 3. Improve troubleshooting efficiency. GTID includes server UUID and serial number, which is convenient for tracking transaction flow and accurately locate problems. These three core advantages make MySQL replication more robust and easy to manage, significantly improving system reliability and data integrity.

MySQL main library failover mainly includes four steps. 1. Fault detection: Regularly check the main library process, connection status and simple query to determine whether it is downtime, set up a retry mechanism to avoid misjudgment, and can use tools such as MHA, Orchestrator or Keepalived to assist in detection; 2. Select the new main library: select the most suitable slave library to replace it according to the data synchronization progress (Seconds_Behind_Master), binlog data integrity, network delay and load conditions, and perform data compensation or manual intervention if necessary; 3. Switch topology: Point other slave libraries to the new master library, execute RESETMASTER or enable GTID, update the VIP, DNS or proxy configuration to

The steps to connect to the MySQL database are as follows: 1. Use the basic command format mysql-u username-p-h host address to connect, enter the username and password to log in; 2. If you need to directly enter the specified database, you can add the database name after the command, such as mysql-uroot-pmyproject; 3. If the port is not the default 3306, you need to add the -P parameter to specify the port number, such as mysql-uroot-p-h192.168.1.100-P3307; In addition, if you encounter a password error, you can re-enter it. If the connection fails, check the network, firewall or permission settings. If the client is missing, you can install mysql-client on Linux through the package manager. Master these commands

InnoDB is MySQL's default storage engine because it outperforms other engines such as MyISAM in terms of reliability, concurrency performance and crash recovery. 1. It supports transaction processing, follows ACID principles, ensures data integrity, and is suitable for key data scenarios such as financial records or user accounts; 2. It adopts row-level locks instead of table-level locks to improve performance and throughput in high concurrent write environments; 3. It has a crash recovery mechanism and automatic repair function, and supports foreign key constraints to ensure data consistency and reference integrity, and prevent isolated records and data inconsistencies.

IndexesinMySQLimprovequeryspeedbyenablingfasterdataretrieval.1.Theyreducedatascanned,allowingMySQLtoquicklylocaterelevantrowsinWHEREorORDERBYclauses,especiallyimportantforlargeorfrequentlyqueriedtables.2.Theyspeedupjoinsandsorting,makingJOINoperation

MySQL's default transaction isolation level is RepeatableRead, which prevents dirty reads and non-repeatable reads through MVCC and gap locks, and avoids phantom reading in most cases; other major levels include read uncommitted (ReadUncommitted), allowing dirty reads but the fastest performance, 1. Read Committed (ReadCommitted) ensures that the submitted data is read but may encounter non-repeatable reads and phantom readings, 2. RepeatableRead default level ensures that multiple reads within the transaction are consistent, 3. Serialization (Serializable) the highest level, prevents other transactions from modifying data through locks, ensuring data integrity but sacrificing performance;

MySQL transactions follow ACID characteristics to ensure the reliability and consistency of database transactions. First, atomicity ensures that transactions are executed as an indivisible whole, either all succeed or all fail to roll back. For example, withdrawals and deposits must be completed or not occur at the same time in the transfer operation; second, consistency ensures that transactions transition the database from one valid state to another, and maintains the correct data logic through mechanisms such as constraints and triggers; third, isolation controls the visibility of multiple transactions when concurrent execution, prevents dirty reading, non-repeatable reading and fantasy reading. MySQL supports ReadUncommitted and ReadCommi.

To add MySQL's bin directory to the system PATH, it needs to be configured according to the different operating systems. 1. Windows system: Find the bin folder in the MySQL installation directory (the default path is usually C:\ProgramFiles\MySQL\MySQLServerX.X\bin), right-click "This Computer" → "Properties" → "Advanced System Settings" → "Environment Variables", select Path in "System Variables" and edit it, add the MySQLbin path, save it and restart the command prompt and enter mysql--version verification; 2.macOS and Linux systems: Bash users edit ~/.bashrc or ~/.bash_
