failed (104: Connection reset by peer)
antoine2223
nginx-forum at nginx.us
Fri Nov 2 11:52:53 UTC 2012
hello ,
hello sir i am beginer, i haev following errors in my logs
in my error log ,
2012/11/02 12:27:26 [error] 3909#0: *1 recv() failed (104: Connection
reset by peer) while reading response header from upstream, client:
192.168.250.55, server: pharse.mediactive.fr, request: "GET / HTTP/1.1",
upstream: "fastcgi://127.0.0.1:9000", host: "pharse.mediactive.fr"
2012/11/02 12:27:26 [error] 3909#0: *1 recv() failed (104: Connection reset
by peer) while reading response header from upstream, client:
192.168.250.55, server: pharse.mediactive.fr, request: "GET / HTTP/1.1",
upstream: "fastcgi://127.0.0.1:9000", host: "pharse.mediactive.fr"
2012/11/02 12:27:26 [error] 3909#0: *1 recv() failed (104: Connection reset
by peer) while reading response header from upstream, client:
192.168.250.55, server: pharse.mediactive.fr, request: "GET / HTTP/1.1",
upstream: "fastcgi://127.0.0.1:9000", host: "pharse.mediactive.fr"
2012/11/02 12:27:44 [error] 3909#0: *7 recv() failed (104: Connection reset
by peer) while reading response header from upstream, client:
192.168.251.75, server: pharse.mediactive.fr, request: "GET / HTTP/1.1",
upstream: "fastcgi://127.0.0.1:9000", host: "pharse.mediactive.fr"
can you please help me out to rectify the error ?
my ngnnix conf
server {
listen 80;
server_name pharse.mediactive.fr;
root /var/www/Phraseanet/www;
index index.php;
include rewrite_rules.inc;
access_log /var/log/nginx/pharse/access.log;
error_log /var/log/nginx/pharse/error.log;
rewrite_log on;
# PHP scripts -> PHP-FPM server listening on 127.0.0.1:9000
location ~ \.php(/|$) {
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME
$document_root$fastcgi_script_name;
}
# configuration pour les sous definitions
location /files { # Point de montage 'X-Accel-Redirect'
internal;
alias /var/www/Phraseanet/datas; # Chemin d'acces pour
'X-Accel-Redirect'
}
# configuration pour les fichiers de quarantaine
location /lazaret {
internal;
alias /var/www/Phraseanet/tmp/lazaret;
}
# configuration pour les telechargements
location /download {
internal;
alias /var/www/Phraseanet/tmp/download;
}
}
~
my php-fm files look like this .
; Time limit for child processes to wait for a reaction on signals from
master.
; Available units: s(econds), m(inutes), h(ours), or d(ays)
; Default Unit: seconds
; Default Value: 0
;process_control_timeout = 0
; The maximum number of processes FPM will fork. This has been design to
control
; the global number of processes when using dynamic PM within a lot of
pools.
; Use it with caution.
; Note: A value of 0 indicates no limit
; Default Value: 0
; process.max = 128
; Send FPM to background. Set to 'no' to keep FPM in foreground for
debugging.
; Default Value: yes
;daemonize = yes
; Set open file descriptor rlimit for the master process.
; Default Value: system defined value
;rlimit_files = 1024
; Set max core size rlimit for the master process.
; Possible Values: 'unlimited' or an integer greater or equal to 0
; Default Value: system defined value
;rlimit_core = 0
; Specify the event mechanism FPM will use. The following is available:
; - select (any POSIX os)
; - poll (any POSIX os)
; - epoll (linux >= 2.5.44)
; - kqueue (FreeBSD >= 4.1, OpenBSD >= 2.9, NetBSD >= 2.0)
; - /dev/poll (Solaris >= 7)
; - port (Solaris >= 10)
; Default Value: not set (auto detection)
; events.mechanism = epoll
;;;;;;;;;;;;;;;;;;;;
; Pool Definitions ;
;;;;;;;;;;;;;;;;;;;;
; Multiple pools of child processes may be started with different listening
; ports and different management options. The name of the pool will be
; used in logs and stats. There is no limitation on the number of pools
which
; FPM can handle. Your system will tell you anyway :)
; To configure the pools it is recommended to have one .conf file per
; pool in the following directory:
include=/etc/php5/fpm/pool.d/*.conf
request_terminate_timeout=30s
~
please do help me i ma blocked
Posted at Nginx Forum: http://forum.nginx.org/read.php?2,232452,232452#msg-232452
More information about the nginx
mailing list