Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
silenceheaven Posted April 23, 2018 Posted April 23, 2018 Every hour the entire board goes out with this error message and only this: upstream sent unexpected FastCGI record: 3 while reading response header from upstream, client: xxxxx [info] 274#274: *326933 client 212.228.25.73 closed keepalive connection And I'm not sure exactly why this is happening, or if anyone has run into this issue before. I've disabled any custom extensions but I am unable to resolve this issue.
silenceheaven Posted April 23, 2018 Author Posted April 23, 2018 I can provide configs and whatnot, but I can't find any info about this error. All other PHP-FPM pools are fine, it's just the ipboard one and only started occuring with 4.3
silenceheaven Posted April 23, 2018 Author Posted April 23, 2018 ALLEGEDLY http://www.php.net/function.fastcgi-finish-request Quote There are some pitfalls you should be aware of when using this function.The script will still occupy a FPM process after fastcgi_finish_request(). So using it excessively for long running tasks may occupy all your FPM threads up to pm.max_children. This will lead to gateway errors on the webserver. Another important thing is session handling. Sessions are locked as long as they're active (see the documentation for session_write_close()). This means subsequent requests will block until the session is closed. You should therefore call session_write_close() as soon as possible (even before fastcgi_finish_request()) to allow subsequent requests and a good user experience. This also applies for all other locking techniques as flock or database locks for example. As long as a lock is active subsequent requests might bock. I'm gonna comment it out in \IPS\Output and see if that resolves the issue. I am also using sockets instead of TCP listeners so I don't have the FastCGI keep_conn enabled at all, so the bug that I'm seeing was apparently a big ago shouldn't apply. It's also on PHP 7.2 with Nginx 1.14.0
silenceheaven Posted April 24, 2018 Author Posted April 24, 2018 Nope did not work. Also I have this error in php-fpm.log [23-Apr-2018 19:28:40] WARNING: [pool ipboard] child 11098 exited with code 70 after 56.400945 seconds from start [23-Apr-2018 19:28:40] NOTICE: [pool ipboard] child 11231 started [23-Apr-2018 19:28:40] WARNING: [pool ipboard] child 11099 exited with code 70 after 56.554083 seconds from start [23-Apr-2018 19:28:40] NOTICE: [pool ipboard] child 11232 started [23-Apr-2018 19:28:41] WARNING: [pool ipboard] child 11100 exited with code 70 after 56.648342 seconds from start [23-Apr-2018 19:28:41] NOTICE: [pool ipboard] child 11233 started [23-Apr-2018 19:28:41] WARNING: [pool ipboard] child 11101 exited with code 70 after 56.035649 seconds from start [23-Apr-2018 19:28:41] NOTICE: [pool ipboard] child 11234 started [23-Apr-2018 19:28:42] WARNING: [pool ipboard] child 11102 exited with code 70 after 55.797305 seconds from start [23-Apr-2018 19:28:42] NOTICE: [pool ipboard] child 11235 started [23-Apr-2018 19:28:42] WARNING: [pool ipboard] child 11103 exited with code 70 after 55.698672 seconds from start [23-Apr-2018 19:28:42] NOTICE: [pool ipboard] child 11236 started [23-Apr-2018 19:28:42] WARNING: [pool ipboard] child 11104 exited with code 70 after 55.219465 seconds from start [23-Apr-2018 19:28:42] NOTICE: [pool ipboard] child 11237 started [23-Apr-2018 19:28:43] WARNING: [pool ipboard] child 11105 exited with code 70 after 54.812406 seconds from start [23-Apr-2018 19:28:43] NOTICE: [pool ipboard] child 11238 started [23-Apr-2018 19:28:43] WARNING: [pool ipboard] child 11106 exited with code 70 after 54.407450 seconds from start [23-Apr-2018 19:28:43] NOTICE: [pool ipboard] child 11239 started [23-Apr-2018 19:28:43] WARNING: [pool ipboard] child 11107 exited with code 70 after 54.552490 seconds from start [23-Apr-2018 19:28:43] NOTICE: [pool ipboard] child 11240 started [23-Apr-2018 19:28:44] WARNING: [pool ipboard] child 11108 exited with code 70 after 54.488029 seconds from start [23-Apr-2018 19:28:44] NOTICE: [pool ipboard] child 11241 started [23-Apr-2018 19:28:44] WARNING: [pool ipboard] child 11109 exited with code 70 after 54.765693 seconds from start [23-Apr-2018 19:28:44] NOTICE: [pool ipboard] child 11242 started [23-Apr-2018 19:28:45] WARNING: [pool ipboard] child 11110 exited with code 70 after 54.813411 seconds from start [23-Apr-2018 19:28:45] NOTICE: [pool ipboard] child 11243 started [23-Apr-2018 19:28:46] WARNING: [pool ipboard] child 11111 exited with code 70 after 55.674683 seconds from start [23-Apr-2018 19:28:46] NOTICE: [pool ipboard] child 11245 started [23-Apr-2018 19:28:47] WARNING: [pool ipboard] child 11112 exited with code 70 after 55.759578 seconds from start [23-Apr-2018 19:28:47] NOTICE: [pool ipboard] child 11246 started [23-Apr-2018 19:28:47] WARNING: [pool ipboard] child 11113 exited with code 70 after 55.742473 seconds from start [23-Apr-2018 19:28:47] NOTICE: [pool ipboard] child 11247 started [23-Apr-2018 19:28:47] WARNING: [pool ipboard] child 11114 exited with code 70 after 55.590480 seconds from start [23-Apr-2018 19:28:47] NOTICE: [pool ipboard] child 11248 started [23-Apr-2018 19:28:47] WARNING: [pool ipboard] child 11115 exited with code 70 after 55.835772 seconds from start [23-Apr-2018 19:28:47] NOTICE: [pool ipboard] child 11249 started [23-Apr-2018 19:28:48] WARNING: [pool ipboard] child 11116 exited with code 70 after 55.981720 seconds from start [23-Apr-2018 19:28:48] NOTICE: [pool ipboard] child 11250 started [23-Apr-2018 19:28:48] WARNING: [pool ipboard] child 11117 exited with code 70 after 56.001510 seconds from start There are thousands of these.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.