请大神帮忙看看这到底咋回事,预缓存问题。
不能不说lnmp环境性能的确出众,我是从wdcp转到lnmp的,一用就舍不得丢了。不过有个问题 就是预缓存。我用的是wordpress 插件wp-super-cache的预缓存功能。
环境:之前在Linode vpsCentOS 6.5 64位 wdcp环境, wordpress插件wp-super-cache的预缓存功能一切正常。
现在转到阿里云ecs CentOS 6.5 64位 军哥lnmp一键包环境,其它都正常 就wp-super-cache的预缓存不正常。
现象: 比如指定120分钟预缓存一次网站全部内容,时间到了后缓存页面开始工作。问题来了,只缓存几十个页面后自动停止了,一直显示定在那里不缓存了。只有等下一次的120分钟到来,又开始接着上次的id缓存剩下的页面,又缓存几十个页面又停止了。
请问这是这么回事,是不是lnmp环境里 哪里的设置需要修改??
[ 本帖最后由 gamer 于 2016-2-28 17:41 编辑 ] 不清楚具体原因,你php是什么版本
开慢日志和php错误日志看看 现在用的 php 4.4.40以前用的是5.3的
错误日志 好像就一个 nginx_error.log 25日的
2016/02/25 14:21:29 13105#0: *1616 connect() to unix:/tmp/php-cgi.sock failed (2: No such file or directory) while connecting to upstream, client: 60.210.10.50, server: www.yydxh.net, request: "HEAD / HTTP/1.1", upstream: "fastcgi://unix:/tmp/php-cgi.sock:", host: "www.yydxh.net"
回复 3# 的帖子
这个不是php-fpm的错误日志,这是nginx日志,只是说了php-fpm可能挂掉了军哥 帮忙看看 这是php-fpm错误日志1
NOTICE: fpm is running, pid 5298NOTICE: ready to handle connections
NOTICE: Finishing ...
NOTICE: exiting, bye-bye!
NOTICE: fpm is running, pid 9609
NOTICE: ready to handle connections
NOTICE: Terminating ...
NOTICE: exiting, bye-bye!
NOTICE: fpm is running, pid 946
NOTICE: ready to handle connections
NOTICE: Finishing ...
NOTICE: exiting, bye-bye!
NOTICE: fpm is running, pid 1624
NOTICE: ready to handle connections
军哥 帮忙看看 这是php-fpm错误日志2
WARNING: child 8449, script '/home/wwwroot/www.yydxh.net/wp-cron.php' (request: "POST /wp-cron.php") execution timed out (122.673179 sec), terminatingWARNING: child 8449 exited on signal 15 (SIGTERM) after 1326.200194 seconds from start
NOTICE: child 9638 started
WARNING: child 9913, script '/home/wwwroot/www.yydxh.net/wp-cron.php' (request: "POST /wp-cron.php") execution timed out (124.558860 sec), terminating
WARNING: child 9913 exited on signal 15 (SIGTERM) after 1380.012407 seconds from start
NOTICE: child 10837 started
WARNING: child 10837, script '/home/wwwroot/www.yydxh.net/wp-cron.php' (request: "POST /wp-cron.php") execution timed out (121.162037 sec), terminating
WARNING: child 10837 exited on signal 15 (SIGTERM) after 3633.405515 seconds from start
NOTICE: child 12410 started
NOTICE: Finishing ...
NOTICE: exiting, bye-bye!
NOTICE: fpm is running, pid 17243
NOTICE: ready to handle connections
NOTICE: Terminating ...
NOTICE: exiting, bye-bye!
NOTICE: fpm is running, pid 945
NOTICE: ready to handle connections
WARNING: seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 0 idle, and 5 total children
WARNING: seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 16 children, there are 0 idle, and 6 total children
NOTICE: Terminating ...
NOTICE: exiting, bye-bye!
NOTICE: fpm is running, pid 945
NOTICE: ready to handle connections
WARNING: child 1433, script '/home/wwwroot/www.yydxh.net/wp-cron.php' (request: "POST /wp-cron.php") execution timed out (124.962445 sec), terminating
WARNING: child 1433 exited on signal 15 (SIGTERM) after 1762.695950 seconds from start
NOTICE: child 2912 started
NOTICE: Terminating ...
NOTICE: exiting, bye-bye!
NOTICE: fpm is running, pid 945
NOTICE: ready to handle connections
WARNING: child 947, script '/home/wwwroot/www.yydxh.net/wp-cron.php' (request: "POST /wp-cron.php") execution timed out (107.222601 sec), terminating
WARNING: child 947 exited on signal 15 (SIGTERM) after 300.009709 seconds from start
NOTICE: child 1876 started
WARNING: child 1828, script '/home/wwwroot/www.yydxh.net/wp-cron.php' (request: "POST /wp-cron.php") execution timed out (107.134330 sec), terminating
WARNING: child 1828 exited on signal 15 (SIGTERM) after 3474.163169 seconds from start
NOTICE: child 3819 started
WARNING: child 1876, script '/home/wwwroot/www.yydxh.net/wp-cron.php' (request: "POST /wp-cron.php") execution timed out (113.054784 sec), terminating
WARNING: child 1876 exited on signal 15 (SIGTERM) after 3500.070658 seconds from start
NOTICE: child 3926 started
WARNING: child 6008, script '/home/wwwroot/www.yydxh.net/wp-cron.php' (request: "POST /wp-cron.php") execution timed out (104.414525 sec), terminating
WARNING: child 6008 exited on signal 15 (SIGTERM) after 2684.491998 seconds from start
NOTICE: child 7671 started
WARNING: seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 0 idle, and 9 total children
WARNING: server reached pm.max_children setting (10), consider raising it
WARNING: child 9504 exited on signal 11 (SIGSEGV) after 5271.317220 seconds from start
NOTICE: child 12444 started
WARNING: child 12444 exited on signal 11 (SIGSEGV) after 2.261552 seconds from start
NOTICE: child 12445 started
WARNING: child 9485 exited on signal 11 (SIGSEGV) after 5541.724221 seconds from start
NOTICE: child 12594 started
WARNING: child 9516 exited on signal 11 (SIGSEGV) after 5540.616623 seconds from start
NOTICE: child 12597 started
WARNING: child 12594 exited on signal 11 (SIGSEGV) after 3.097226 seconds from start
NOTICE: child 12598 started
WARNING: child 8572 exited on signal 11 (SIGSEGV) after 8217.406244 seconds from start
NOTICE: child 13279 started
WARNING: child 8610 exited on signal 11 (SIGSEGV) after 8156.393404 seconds from start
NOTICE: child 13280 started
WARNING: child 9510 exited on signal 11 (SIGSEGV) after 7527.129145 seconds from start
NOTICE: child 13760 started
WARNING: child 12598 exited on signal 11 (SIGSEGV) after 4804.210650 seconds from start
NOTICE: child 14976 started
WARNING: child 12445 exited on signal 11 (SIGSEGV) after 5074.475226 seconds from start
NOTICE: child 14977 started
军哥 我看了看php-fpm.conf里的设置 是不是跟这里面的设置有关?
pm.max_children = 10是不是跟这个子进程数量有关?设小了??
回复 6# 的帖子
上面日志只有wp-cron执行超时的信息,可以增加超时时间或设为0不限制试试,置顶帖502排查解决方法里有具体修改方法 谢了 军哥我试试
页:
[1]