Record once to solve the problem of inaccessibility of WDCP panel and website

This problem was solved by an old netizen of Snail last week who encountered a problem and contacted him for help. According to the initial description, it is mentioned that the WDCP panel environment panel cannot be logged in, and the website cannot be accessed. It is true that there are still many WDCP panel users, but from the document updates in recent years, the software upgrade is indeed slower than that of ordinary panels, but it is still good. Since it has been done for a long time, the general problems encountered can still be solved from Find the solution in the documentation.

Because the problems encountered may be different each time, we can only conduct actual analysis and solutions based on different problems. Snail has encountered similar problems before, and since it is a MYSQL database problem, it can be solved by restarting it. This is not the case, let me record it.

First, check the hard disk condition

I casually checked the hard drive and found that the nearly 200GB hard drive was full. According to the description, it was a newly installed CMS program. I didn’t ask about the specific program. Based on our habits, we can guess that the disk must be full due to logs.

Second, check the WDCP panel log directory

Because I am relatively familiar with WDCP, go directly to the NGINX log directory/www/wdlinux/nginx-1.8.1/logs, and then you can see the system log. The above screenshot was taken by me later. I forgot to take the screenshot at the time. I saw that the access.log log is more than 100 GB in size. And it continues to increase after refreshing.

Third, solve the log problem

Delete the log directly here, and then restart NGINX and MYSQL. Everything is normal, and the panel and website can be opened normally. But the log continues to increase after refreshing. Here you need to go to the panel background to turn off the log.

When logging in to the background, we can see that the system log is turned off, but it seems that the path is not like this. What we need to solve is the access.log file. Find here the previously recorded article "Delete WDCP website logs and system Nginx or Apache log files".

sed -i \\’/log_format/aaccess_log off;\\’ /www/wdlinux/nginx/conf/nginx.conf

After closing the generation, we also need to restart NGINX

/etc/init.d/nginxd restart

Then you can see that the log file does not seem to be increasing rapidly.

Recommended site search: foreign PHP space, Korean virtual host independent IP virtual host, overseas host, domain name price, how to buy virtual host, Ministry of Industry and Information Technology domain name registration, personal domain name registration, US host rental, domain name price,