php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #76849 FastCGI stopped working and was closed
Submitted: 2018-09-07 14:41 UTC Modified: 2020-02-23 04:22 UTC
From: richard dot rekos at questionmark dot com Assigned: cmb (profile)
Status: No Feedback Package: IIS related
PHP Version: Irrelevant OS: Windows 2012 R2
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
MUST BE VALID
Solve the problem:
11 - 9 = ?
Subscribe to this entry?

 
 [2018-09-07 14:41 UTC] richard dot rekos at questionmark dot com 
Description:
------------
We use a simple php script (ping.php) to serve as a health check.  After upgrading from 7.1.16 to 7.1.19, we are seeing php-cgi.exe crash multiple times a day on requests to the health check (ping.php).  We have since upgraded to 7.1.20 and the issue persists.

Test script:
---------------
<?php 

echo time();

?>


Expected result:
----------------
Returns Epoch time

Actual result:
--------------
500 Internal Server Error 

Faulting application name: php-cgi.exe, version: 7.1.20.0
Faulting module name: ntdll.dll, version: 6.3.9600.19101

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2018-09-08 03:11 UTC] requinix@php.net
-Status: Open +Status: Feedback
 [2018-09-08 03:11 UTC] requinix@php.net 
Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32

Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.
 [2018-11-18 22:34 UTC] cmb@php.net
-Status: Feedback +Status: No Feedback
 [2018-11-18 22:34 UTC] cmb@php.net 
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.
 [2019-01-02 19:12 UTC] richard dot rekos at questionmark dot com
-Status: No Feedback +Status: Closed
 [2019-01-02 19:12 UTC] richard dot rekos at questionmark dot com 
I am in the process of capturing a crash dump in a Staging environment, where this occurs less frequently. Our Data Security officers would like to know details related to the handling of crash dumps. Do you share them with any third party? Are the dump files deleted or retained?
 [2019-01-02 19:13 UTC] richard dot rekos at questionmark dot com
-Status: Closed +Status: Open
 [2019-01-02 19:13 UTC] richard dot rekos at questionmark dot com 
Have setup crash dump capture and will provide the files following the next crash.
 [2019-02-09 06:26 UTC] ab@php.net
-Status: Open +Status: Feedback
 [2019-02-09 06:26 UTC] ab@php.net 
Please do. Thanks.
 [2019-02-11 19:01 UTC] richard dot rekos at questionmark dot com
-Status: Feedback +Status: Open
 [2019-02-11 19:01 UTC] richard dot rekos at questionmark dot com 
Our Data Security officers would like to know details related to the handling of crash dumps. Do you share them with any third party? Are the dump files deleted or retained?
 [2019-02-11 19:10 UTC] ab@php.net 
Best were the dump wouldn't contain any sensitive data, then you could share publicly and possibly have more eyes on it. In any case, there is no disclosure if the dump is made available in private, though they might be shared with other devs for collaboration. As soon as a dump is not needed anymore, I delete them from my local hdd.

Before you create the dump, please be sure to fetch the debug symbols, too, as described in the links above.

Thanks.
 [2020-02-13 17:21 UTC] cmb@php.net
-Status: Open +Status: Feedback -Assigned To: +Assigned To: cmb
 [2020-02-23 04:22 UTC] php-bugs at lists dot php dot net 
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Thu Apr 18 21:01:29 2024 UTC