On Linux install mysql5.7.20 run after a period of time will stop, look at the log is'/var/run/mysqld/mysqld. Pid 'file, the file is in memory, recently didn't restart the server, why can not find a file, how should if correct? Configure the parameters of the path in the file below? Whether can change the path parameter?

CodePudding user response:

In:/etc/my CNF
But LZ server disk write full?

CodePudding user response:

Not to say that the file can not find, is the time to generate the file write wrong, look at the/var/run/mysqld is this directory exists, start the mysql user have permissions to write

CodePudding user response:

reference 1st floor splendid_java response:

in general:/etc/my CNF
But LZ server disk write full?

You said is where configuration file path?

CodePudding user response:

CKC quote 2 floor response:

does not mean that the file can't find, is the time to generate the file write wrong, look at the/var/run/mysqld is this directory exists, start the mysql user have permissions to write

Mysql to express stop reason lies in the/var/run/mysqld the file path does not exist, so every time I restart to create this path and empowerment, and then after a period of time this file will be forced disappearances, lead to mysql to stop

CodePudding user response:

This file is deleted and cannot lead to stop the mysql service

CodePudding user response:

Check the directory exists, used by the mysql account if there is a permission

CodePudding user response:

reference 5 floor rucypli reply:

this file to be deleted and cannot lead to stop the mysql service

But on the log said cannot be started, but couldn't find the file, is stopped, because can't find the file

CodePudding user response:

refer to 6th floor ZJCXC response:

check the directory exists, if used mysql account have permission

Directory, run for a period of time will disappear automatically, and then restart and empowerment will recreate the file at a time

CodePudding user response:

Install a monitoring software to monitor

CodePudding user response:

. Pid file is typically process lock handle, this file is locked, after the process starts with the root accounts forcibly remove lead to process the status of the unpredictable, so if. Pid file does not exist, may lead to crush the process or restart,
Recommend creating mysqld directory, and sets the permissions at the mysqld - r - r - r -, see if you can avoid the directory to be deleted,

CodePudding user response:

references to the tenth floor kampoo response:

pid file lock handle is typically process, this file is locked, after the process starts with the root accounts forcibly remove can lead to unpredictable process status, so if. Pid file does not exist, may lead to crush the process or restart,
Recommend creating mysqld directory, and sets the permissions at the mysqld - r - r - r -, see if you can avoid the directory to be deleted,

Mysql service is only need to perform this file? Don't need to read and write?

CodePudding user response:

This file is when to start write mysqd PID in, so I must be able to when I started writing (there is no automatic creation), after the success is no matter

CodePudding user response:

11 references cuicuicui1222222222 response:

when the mysql service is only need to perform this file? Don't need to read and write?

Not the file permissions, refers to the directory/var/run/mysqld access, read, write, and execute,