I often collect one or two pages and then stop.
The complete solution is as follows:
The setting of max_execution_time = 0 in php.ini only works for PHP itself <br>The parameter that needs to be modified in php-fpm mode is php-fpm.conf (the configuration file in ubuntu is /etc/php5/fpm/pool .d/www.conf) request_terminate_timeout = 0<br>safe_mode configuration has been canceled in PHP5.4, no need to configure<br>
It stopped reporting 502 errors and started reporting 504 errors. I continued to search for online support, but no relevant information was found, only that there might be a problem with the nginx container. In fact, the 504 error is mainly caused by nginx timeout. Just modify its configuration file
Edit /etc/nginx/nginx.conf and add the following code in the http section, If you have these settings, change the corresponding values<br>...<br>
http{ ... fastcgi_connect_timeout 1800; fastcgi_send_timeout 1800; fastcgi_read_timeout 1800; fastcgi_buffer_size 1024k; fastcgi_buffers 32 1024k; fastcgi_busy_buffers_size 2048k; fastcgi_temp_file_write_size 2048k; ...
This is the solution For the problem of error reporting, the batch collection source method is used, and the manual update and collection of 20 pages * 25 articles = 500 articles are executed normally, which takes 2 hours.
The above is the detailed content of How to solve the problem of continuous collection in wp-autopost. For more information, please follow other related articles on the PHP Chinese website!