Examples of MySQL startup failure caused by/var/log/pacct files: pacctmysql

Examples of MySQL startup failure caused by/var/log/pacct files: pacctmysql

Without warning, MySQL went on strike. After the mysql. server startup script is used, the mysqld process ends without any prompts.

Set mysql. in the server, $ bindir/mysqld_safe -- datadir = $ datadir -- pid-file = $ server_pid_file>/dev/null 2> & 1 is run after the output redirection is removed. An error is returned: file size limit exceedednohup ......

In this case, the file is too large. However, you can view the database files and log files in the mysql data directory. the maximum size is several hundred megabytes. Ulimit-a does not limit the file size.

After N minutes of being depressed, I decided to use find/-size + 2048000 k to find the suspicious files on the entire hard disk. The result is: the large file/var/log/pacct is larger than 2 GB. Obviously, this is the log file generated after SA activates accton and is not rolled back. Otherwise, clear/var/log/pacct and start MySQL again. everything is back to normal!

What I don't understand is why the mysql STARTUP script is affected by the log statistics of such an irrelevant process, which causes the mysqld process to be completely unable to start. It is estimated that the mysql. server/mysqld_safe script logic is still a problem ..