May 30, 20188 yr May 29 18:58:19 Tower nginx: 2018/05/29 18:58:19 [error] 2945#2945: *368203 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.1.193, server: , request: "POST /webGui/include/DeviceList.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Main" May 29 18:58:19 Tower php-fpm[2919]: [WARNING] [pool www] child 24185 exited on signal 7 (SIGBUS) after 201.121514 seconds from start May 29 19:36:33 Tower nginx: 2018/05/29 19:36:33 [error] 2945#2945: *379713 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.1.193, server: , request: "POST /webGui/include/DeviceList.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Main" May 29 19:36:33 Tower php-fpm[2919]: [WARNING] [pool www] child 2998 exited on signal 7 (SIGBUS) after 109.067894 seconds from start May 30 03:04:35 Tower nginx: 2018/05/30 03:04:35 [error] 2945#2945: *478509 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.1.193, server: , request: "POST /webGui/include/DeviceList.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Main" May 30 03:04:35 Tower php-fpm[2919]: [WARNING] [pool www] child 19305 exited on signal 7 (SIGBUS) after 137.091318 seconds from start I get these showing up several times a week in my syslog. Nothing ever seems broken so I'm not sure if this is something I need to worry about or not. Anyone know what would be causing this? No other warnings/errors accompany these. Edited May 30, 20188 yr by Leondre
Archived
This topic is now archived and is closed to further replies.