php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #32176 (OS 10054)An existing connection was forcibly closed by the remote host. : cor
Submitted: 2005-03-03 16:17 UTC Modified: 2005-03-28 01:00 UTC
Votes:16
Avg. Score:4.1 ± 0.9
Reproduced:15 of 15 (100.0%)
Same Version:4 (26.7%)
Same OS:5 (33.3%)
From: webmaster at sanders-consultation-group-plu Assigned:
Status: No Feedback Package: Apache2 related
PHP Version: 5.0.3 OS: Windows 2000 Pro
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2005-03-03 16:17 UTC] webmaster at sanders-consultation-group-plu
Description:
------------
Just trying to establish that bug #25570 seems to still be alive and well in PHP 5.0.3, as I get the same errors messages that seem to be associated with this previous "closed" bug, though I am running on a different OS. Locahost set-up is Apache 2.0.52, and PHP 5.0.3. The full error is just as the post title, or as follows:

(OS 10054)An existing connection was forcibly closed by the remote host.  : core_output_filter: writing data to the network

I found the 25570 bug while googling for the error message, so hopefully, I am posting this to the correct error. I would have posted it to the 25570 bug, but it states that closed bugs will not be updated and posting to them will just be deleted. Didn't know what else to do in order to try and bring this to someone's attention. My appologies if I've gone about this the wrong way.

Reproduce code:
---------------
Not sure, just getting the same error messages as previously associated with bug #25570.

Expected result:
----------------
N/A

Actual result:
--------------
N/A

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-03-07 03:29 UTC] webmaster at sanders-consultation-group-plu
Sorry Sniper, that's not it. It's already been added to my httpd.conf, and the problem still persists.
 [2005-03-09 00:57 UTC] sniper@php.net
Try without those <IfDefine AEX> tags around it..

 [2005-03-09 04:10 UTC] webmaster at sanders-consultation-group-plu
Done Sniper, restarted the server, and still the following:

[Tue Mar 08 21:02:17 2005] [info] (OS 10054)An existing connection was forcibly closed by the remote host.  : core_output_filter: writing data to the network
[Tue Mar 08 20:59:21 2005] [info] (OS 10054)An existing connection was forcibly closed by the remote host.  : core_output_filter: writing data to the network
[Tue Mar 08 20:59:21 2005] [info] (OS 10054)An existing connection was forcibly closed by the remote host.  : core_output_filter: writing data to the network
[Tue Mar 08 20:57:20 2005] [info] (OS 10054)An existing connection was forcibly closed by the remote host.  : core_output_filter: writing data to the network
[Tue Mar 08 20:57:20 2005] [info] (OS 10054)An existing connection was forcibly closed by the remote host.  : core_output_filter: writing data to the network
[Tue Mar 08 20:56:59 2005] [info] (OS 10054)An existing connection was forcibly closed by the remote host.  : core_output_filter: writing data to the network
[Tue Mar 08 20:56:58 2005] [info] (OS 10054)An existing connection was forcibly closed by the remote host.  : core_output_filter: writing data to the network
[Tue Mar 08 20:54:51 2005] [info] (OS 10054)An existing connection was forcibly closed by the remote host.  : core_output_filter: writing data to the network
[Tue Mar 08 20:54:29 2005] [info] (OS 10054)An existing connection was forcibly closed by the remote host.  : core_output_filter: writing data to the network
[Tue Mar 08 20:50:41 2005] [info] (OS 10054)An existing connection was forcibly closed by the remote host.  : core_output_filter: writing data to the network
[Tue Mar 08 20:50:41 2005] [info] (OS 10054)An existing connection was forcibly closed by the remote host.  : core_output_filter: writing data to the network

Next question or suggestion? Thanks for the suggestion.
 [2005-03-09 04:13 UTC] webmaster at sanders-consultation-group-plu
Thought maybe some of this might help...just trying to help identify what's still causing this problem.

Server software environment:

Apache version 2.0.52 
MySQL version 4.1.10
PostgreSQL version 8.0.0
Openssl version 0.9.7e
Slimftpd version 3.16
Xmail version 1.21
Perl version 5.8.6
PHP version 5.0.3 readme 
Python version 2.3.4
 [2005-03-09 21:38 UTC] sniper@php.net
Please try using this CVS snapshot:

  http://snaps.php.net/php5-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php5-win32-latest.zip

It was said in the bug #25570 that this should be fixed in CVS..

 [2005-03-10 20:58 UTC] webmaster at sanders-consultation-group-plu
Thanks Sniper, I'll work on that CVS update here over the weekend. Things are a bit hectic to do it today. Thanks for the help. I'll report back once it's completed.
 [2005-03-12 14:46 UTC] sniper@php.net
Waiting for feedback..(please don't reply before you have tried the snapshot)
 [2005-03-20 11:13 UTC] jorton@php.net
Exactly what problem are you reporting?  Just that this message is logged to the error_log when a client aborts a connection (and so, may happen a lot)?  That is expected behaviour.
 [2005-03-28 01:00 UTC] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
 
PHP Copyright © 2001-2020 The PHP Group
All rights reserved.
Last updated: Tue Sep 29 15:01:25 2020 UTC