View previous topic :: View next topic |
Author |
Message |
bkonia -
Joined: 25 Jun 2005 Posts: 4
|
Posted: Sat Feb 23, 2008 12:40 am Post subject: Broken Pipe |
|
|
My fastcgi.log contains tons of "broken pipe" errors. Here's a sample:
22/Feb/2008:12:17:20 -0500 SUID: 201 PUID: 201 RUID: 0 URI: Reading 0 bytes failed = Broken pipe
22/Feb/2008:12:17:20 -0500 SUID: 201 PUID: 201 RUID: 0 URI: timeout-header2!
22/Feb/2008:12:22:20 -0500 SUID: 202 PUID: 202 RUID: 0 URI: Reading 0 bytes failed = Broken pipe
22/Feb/2008:12:22:20 -0500 SUID: 202 PUID: 202 RUID: 0 URI: timeout-header2!
22/Feb/2008:12:33:02 -0500 SUID: 204 PUID: 204 RUID: 0 URI: Reading 0 bytes failed = Broken pipe
22/Feb/2008:12:33:02 -0500 SUID: 204 PUID: 204 RUID: 0 URI: timeout-header2!
22/Feb/2008:13:07:06 -0500 SUID: 205 PUID: 205 RUID: 0 URI: Reading 0 bytes failed = Broken pipe
22/Feb/2008:13:07:06 -0500 SUID: 205 PUID: 205 RUID: 0 URI: timeout-header2!
22/Feb/2008:13:52:19 -0500 SUID: 206 PUID: 206 RUID: 0 URI: Reading 0 bytes failed = Broken pipe
22/Feb/2008:13:52:19 -0500 SUID: 206 PUID: 206 RUID: 0 URI: timeout-header2!
22/Feb/2008:14:37:30 -0500 SUID: 207 PUID: 207 RUID: 0 URI: Reading 0 bytes failed = Broken pipe
22/Feb/2008:14:37:30 -0500 SUID: 207 PUID: 207 RUID: 0 URI: timeout-header2!
22/Feb/2008:14:37:31 -0500 SUID: 208 PUID: 208 RUID: 0 URI: Reading 0 bytes failed = Broken pipe
22/Feb/2008:14:37:31 -0500 SUID: 208 PUID: 208 RUID: 0 URI: timeout-header2!
22/Feb/2008:15:23:17 -0500 SUID: 206 PUID: 206 RUID: 1 URI: /user_account.php Reading 8 bytes failed = Broken pipe
22/Feb/2008:18:21:37 -0500 SUID: 6 PUID: 6 RUID: 0 URI: Reading 0 bytes failed = Broken pipe
22/Feb/2008:18:21:37 -0500 SUID: 6 PUID: 6 RUID: 0 URI: timeout-header2!
22/Feb/2008:18:27:11 -0500 SUID: 7 PUID: 7 RUID: 0 URI: Reading 0 bytes failed = Broken pipe
22/Feb/2008:18:27:11 -0500 SUID: 7 PUID: 7 RUID: 0 URI: timeout-header2!
22/Feb/2008:17:07:31 -0500 SUID: 2 PUID: 2 RUID: 0 URI: Reading 0 bytes failed = Broken pipe
22/Feb/2008:17:07:31 -0500 SUID: 2 PUID: 2 RUID: 0 URI: timeout-header2!
22/Feb/2008:17:32:19 -0500 SUID: 3 PUID: 3 RUID: 0 URI: Reading 0 bytes failed = Broken pipe
22/Feb/2008:17:32:19 -0500 SUID: 3 PUID: 3 RUID: 0 URI: timeout-header2!
22/Feb/2008:17:57:20 -0500 SUID: 4 PUID: 4 RUID: 0 URI: Reading 0 bytes failed = Broken pipe
22/Feb/2008:17:57:20 -0500 SUID: 4 PUID: 4 RUID: 0 URI: timeout-header2!
22/Feb/2008:18:17:19 -0500 SUID: 5 PUID: 5 RUID: 0 URI: Reading 0 bytes failed = Broken pipe
22/Feb/2008:18:17:19 -0500 SUID: 5 PUID: 5 RUID: 0 URI: timeout-header2!
The site appears to work OK, but I'm concerned about these errors and it makes me wonder if they are causing degraded performance for users of the site. This is running on Linux with PHP 5.2.5. _________________ Brad S Konia |
|
Back to top |
|
|
aprelium -
Joined: 22 Mar 2002 Posts: 6800
|
|
Back to top |
|
|
bkonia -
Joined: 25 Jun 2005 Posts: 4
|
Posted: Mon Feb 25, 2008 7:26 pm Post subject: |
|
|
Thank you for the response. I understand that the error message is bogus, but it is filling up my fastcgi.log and this makes it more difficult to spot other errors that may be legitimate.
In the other thread that you referenced, you mentioned that you would offer an option to filter this error message in the next release. Since that response was posted more than a year ago, I'm wondering if this option will be offered anytime soon.
Thanks! _________________ Brad S Konia |
|
Back to top |
|
|
aprelium -
Joined: 22 Mar 2002 Posts: 6800
|
Posted: Wed Mar 19, 2008 5:50 pm Post subject: |
|
|
bkonia wrote: | Since that response was posted more than a year ago, I'm wondering if this option will be offered anytime soon. |
You're right. We are working on integrating it in the next version since the same problem continues to occur with the new PHP versions. _________________ Support Team
Aprelium - http://www.aprelium.com |
|
Back to top |
|
|
|