You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2008/10/10 17:24:45 UTC
DO NOT REPLY [Bug 45986] New: [info]...Invalid argument:
core_output_filter: writing data to the network
https://issues.apache.org/bugzilla/show_bug.cgi?id=45986
Summary: [info]...Invalid argument: core_output_filter: writing
data to the network
Product: Apache httpd-2
Version: 2.0.63
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Core
AssignedTo: bugs@httpd.apache.org
ReportedBy: danielt@consol.de
Hello,
today, I was debugging a CGI application, which after logging in, writes
some HTML data to the document root and redirects the client to it.
But the redirection was not successful, the request was answered with a
closed connection. The entire response was missing.
Since this runs on a clustered environment (DocumentRoot is shared over
NFS), I thought this was an NFS problem, because I could receive the
content on the second server. Long story short, I was off the track.
After I set the LogLevel to debug the following message appeared in the
ErrorLog:
[info] [client 160.xx.xx.xx] (22)Invalid argument: core_output_filter:
writing data to the network
I grepped the httpd source for this message to get an idea what's going
on here and found the FAQ entry. EnableSendfile Off, everything is fine
now.
But I really think that this should be at least an error instead of an
info. httpd was not able to send the response, this is worse than "file
not found" which is logged as an error.
Here is the patch:
--- server/core.c.orig 2006-07-12 09:40:55.000000000 +0200
+++ server/core.c 2008-10-10 17:21:36.000000000 +0200
@@ -4327,7 +4327,7 @@
}
if (rv != APR_SUCCESS) {
- ap_log_cerror(APLOG_MARK, APLOG_INFO, rv, c,
+ ap_log_cerror(APLOG_MARK, APLOG_ERR, rv, c,
"core_output_filter: writing data to the network");
if (more)
Regards,
Danijel
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 45986] [info]...Invalid argument:
core_output_filter: writing data to the network
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45986
--- Comment #1 from Eric Covener <co...@gmail.com> 2008-10-10 08:47:45 PST ---
I'd rather see it trap the specific errno, because this looks like the same
path as a host of normal client issues which I don't agree should be loglevel
error.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 45986] [info]...Invalid argument:
core_output_filter: writing data to the network
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45986
--- Comment #3 from Eric Covener <co...@gmail.com> 2008-10-22 06:45:29 PST ---
(In reply to comment #2)
> Hm, I see the problem. I agree with Marc.
> This are the errors sendfile could raise. At least an error should be
> logged, if sendfile raises EIO, ENOMEN or EINVAL
This log message is not sendfile-specific, though.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 45986] [info]...Invalid argument:
core_output_filter: writing data to the network
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45986
--- Comment #2 from Danijel Tasov <da...@consol.de> 2008-10-21 12:15:47 PST ---
Hm, I see the problem. I agree with Marc.
EAGAIN Non-blocking I/O has been selected using O_NONBLOCK and the
write would block.
EBADF The input file was not opened for reading or the output file was
not opened for writing.
EFAULT Bad address.
EINVAL Descriptor is not valid or locked, or an mmap(2)-like operation
is not available for in_fd.
EIO Unspecified error while reading from in_fd.
ENOMEM Insufficient memory to read from in_fd.
This are the errors sendfile could raise. At least an error should be
logged, if sendfile raises EIO, ENOMEN or EINVAL
I'm not sure about about EFAULT, EBADF and EGAIN.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org