Website periodic Error 500

The website server is developed in nginx and php. The website has encountered a 500 error every weekend, and the nginx error log is not recorded. Generally, it appears when the POST form is submitted, and access to other pages is normal. Note: There is no difference between weekend visits and normal visits, and the probability of 500 errors is relatively small at ordinary times... the website server is developed in nginx and php. The website has encountered a 500 error every weekend, and the nginx error log is not recorded. Generally, it appears when the POST form is submitted, and access to other pages is normal.
Note: There is no difference between weekend visits and normal visits, and the probability of 500 errors is relatively low. It is mainly concentrated on weekends. Now, the error 500 is reported over the weekend, but it does not last forever. What is the reason?

Reply content:

The website server is developed in nginx and php. The website has encountered a 500 error every weekend, and the nginx error log is not recorded. Generally, it appears when the POST form is submitted, and access to other pages is normal.
Note: There is no difference between weekend visits and normal visits, and the probability of 500 errors is relatively low. It is mainly concentrated on weekends. Now, the error 500 is reported over the weekend, but it does not last forever. What is the reason?

Adjusting the nginx error log level can help analysis.

Error_log levels are divided into debug, info, notice, warn, error, and crit. The default levels are crit. The format defined after the log name is as follows:
Error_log/your/path/error. log crit;
Crit records the least, while debug records the most.

If the error_log level is the default crit and the Error 500 is displayed, the log does not record meaningful information. It is recommended to adjust the error_log level, for example, error, and more error log records.

If the traffic volume is small, you need to consider the code problem. We recommend that you record the log in the post location, such as the operation SQL statement executed by the post data, and troubleshoot the problem based on the logs.