# Error message confirmation

**URL:** <https://www.ruby-forum.com/t/error-message-confirmation/195683>\
**Category:** NGINX\
**Created:** [September 28, 2010, 5:12am UTC](https://www.ruby-forum.com/t/error-message-confirmation/195683 "2010-09-28T05:12:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mat\_h](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/67e7ee/32.png) [@mat\_h](https://www.ruby-forum.com/u/mat_h)\
**Post date:** [September 28, 2010, 5:12am UTC](https://www.ruby-forum.com/t/error-message-confirmation/195683/1 "2010-09-28T05:12:43Z")

</div>

Is this correct. The error message: upstream prematurely closed  
connection while reading response header from upstream, client

means that the fastcgi server process closed the connection before it  
was supposed to (pointing at an error in php-fpm)

---

<div class="post-metadata">

**Author:** ![mat\_h](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/67e7ee/32.png) [@mat\_h](https://www.ruby-forum.com/u/mat_h)\
**Post date:** [September 28, 2010, 8:31am UTC](https://www.ruby-forum.com/t/error-message-confirmation/195683/2 "2010-09-28T08:31:04Z")

</div>

On Tue, Sep 28, 2010 at 01:11:50PM +1000, mat h wrote:

> Is this correct. The error message: upstream prematurely closed  
> connection while reading response header from upstream, client
> 
> means that the fastcgi server process closed the connection before it  
> was supposed to (pointing at an error in php-fpm)

Yes.

–  
Igor S.

> **[Igor Sysoev](http://sysoev.ru/en/)**

---

<div class="post-metadata">

**Author:** ![mat\_h](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/67e7ee/32.png) [@mat\_h](https://www.ruby-forum.com/u/mat_h)\
**Post date:** [September 28, 2010, 8:35am UTC](https://www.ruby-forum.com/t/error-message-confirmation/195683/3 "2010-09-28T08:35:45Z")

</div>

Thanks, looks like the php-fpm dynamic process manager still isnt  
stable. Just a FYI to all nginx and php-fpm users.