104: Connection reset by peer

[B.R.]

Do you have some information on the number of concurrent connections?
Since you already played with the 'max_requests' parameter too, it seems
not to be the reason of the trouble. But better be safe than sorry.

If your actual number of connections/second is greater than what the
configuration is expecting then you'll have your answer. But you don't
provide information allowing to decide on this, and it seems you tried
blind changes only.
Could you provide your input requests rate?
---
*B. R.*


On Wed, May 8, 2013 at 7:58 AM, ron ramos <nhadie at gmail.com> wrote:

> hi,
>
> i've seen that info as well  ( yes i tried searching for answers as
> mentioned )  and it did not help me unfortunately.
> i've increased from 500 to 1000 to 10000. increase children servers etc.
>
> regards,
> ron
>
>
> On Wed, May 8, 2013 at 7:42 PM, B.R. <reallfqq-nginx at yahoo.fr> wrote:
>
>> After a very long search on Google (almost 15s, including keyboard
>> input), I found astonishing help, based on the information you provided.
>>
>> About the FPM children burying, I found a resource on StackOverflow
>> linking back to the Nginx forum (ML archive):
>>
>> http://stackoverflow.com/questions/2551185/tons-of-fpm-children-bury-in-php-fpm-log-php-5-2-13php-fpm-0-5-13-nginx-0
>>
>> It seems, at first glance, that the children bury and its respawn works
>> as intended, if you reach the requests limit number. I dunno how to check
>> that is the case though. Your log entries seem to be silent about that.
>>
>> My 2 cents,
>> ---
>> *B. R.*
>>
>>
>> On Wed, May 8, 2013 at 7:29 AM, ron ramos <nhadie at gmail.com> wrote:
>>
>>>
>>> Hi All,
>>>
>>> I understand that this is a generic error, but it has been frustrating
>>> trying to solve this issue and i'm not able to find an answer anywhere.
>>> basically i have an application which is running fine using apache, but we
>>> wanted to try nginx/php5-fpm:
>>>
>>> some parts of my application has this connection reset issue, sometimes
>>> it works but inconsistent.
>>> if it does not work, i restart php5-fpm and it will work again, but
>>> after sometime it will have the same issue.
>>>
>>> i'm using:
>>>
>>> # nginx -v
>>> nginx version: nginx/1.4.0
>>>
>>> # php5-fpm -v
>>> PHP 5.4.14-1~precise+1 (fpm-fcgi) (built: Apr 11 2013 17:18:51)
>>> Copyright (c) 1997-2013 The PHP Group
>>> Zend Engine v2.4.0, Copyright (c) 1998-2013 Zend Technologies
>>>
>>> when i enable debug this is the only thing i can see;
>>>
>>> [08-May-2013 18:08:32.545758] DEBUG: pid 358359, fpm_got_signal(), line
>>> 72: received SIGCHLD
>>> [08-May-2013 18:08:32.545884] WARNING: pid 358359, fpm_children_bury(),
>>> line 252: [pool legacy] child 358423 exited with code 3 after 342.958315
>>> seconds from start
>>> [08-May-2013 18:08:32.548943] NOTICE: pid 358359, fpm_children_make(),
>>> line 421: [pool legacy] child 359398 started
>>> [08-May-2013 18:08:32.549023] DEBUG: pid 358359, fpm_event_loop(), line
>>> 411: event module triggered 1 events
>>>
>>>
>>> i have tried different config changes like using static instead of
>>> dynamic..increase max_request..increase child ...increase server..etc.
>>>
>>> one thing i really need is to identify what is causing that connection
>>> peer but logs is not really helping. i tried strace and it still did not
>>> show me anything.
>>>
>>> any other way to debug or identify what is causing this issue? totally
>>> clueless right now.
>>>
>>> thank you in advanced.
>>>
>>> Regards,
>>> Ron
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> nginx mailing list
>>> nginx at nginx.org
>>> http://mailman.nginx.org/mailman/listinfo/nginx
>>>
>>
>>
>> _______________________________________________
>> nginx mailing list
>> nginx at nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx
>>
>
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20130508/41d7758f/attachment.html>