[alert] 17289#0: open socket #14 left in 39 connection

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[alert] 17289#0: open socket #14 left in 39 connection

Jeroen Steggink - CMS
Hello,
 
I have installed Nginx 0.6.35 and got the following error:
 
[alert] 17289#0: open socket #14 left in 39 connection
 
After this error, the server crashed. At the time the server was under a high load with high disk I/O.
 
This is what 'nginx -V' returns:
 
nginx version: nginx/0.6.35
built by gcc 4.1.2 20080704 (Red Hat 4.1.2-44)
configure arguments: --with-cpu-opt=amd64 --without-http_autoindex_module --without-http_fastcgi_module --without-http_proxy_module --with-http_ssl_module --with-http_stub_status_module --without-http_ssi_module --without-http_userid_module --add-module=/root/nginx-geoip-0.1 --with-md5=/usr/lib64 --with-sha1=/usr/lib64 --prefix=/opt/nginx --sbin-path=/usr/sbin/nginx --conf-path=/etc/nginx/nginx.conf --pid-path=/var/run/nginx.pid --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --user=www --group=www
 
What could be the problem?
 
Kind regards,
 
Jeroen
Reply | Threaded
Open this post in threaded view
|

RE: [alert] 17289#0: open socket #14 left in 39 connection

Jim O

Actual test reply

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Jeroen Steggink - CMS
Sent: Monday, March 16, 2009 8:36 AM
To: [hidden email]
Subject: [alert] 17289#0: open socket #14 left in 39 connection

 

Hello,

 

I have installed Nginx 0.6.35 and got the following error:

 

[alert] 17289#0: open socket #14 left in 39 connection

 

After this error, the server crashed. At the time the server was under a high load with high disk I/O.

 

This is what 'nginx -V' returns:

 

nginx version: nginx/0.6.35
built by gcc 4.1.2 20080704 (Red Hat 4.1.2-44)
configure arguments: --with-cpu-opt=amd64 --without-http_autoindex_module --without-http_fastcgi_module --without-http_proxy_module --with-http_ssl_module --with-http_stub_status_module --without-http_ssi_module --without-http_userid_module --add-module=/root/nginx-geoip-0.1 --with-md5=/usr/lib64 --with-sha1=/usr/lib64 --prefix=/opt/nginx --sbin-path=/usr/sbin/nginx --conf-path=/etc/nginx/nginx.conf --pid-path=/var/run/nginx.pid --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --user=www --group=www

 

What could be the problem?

 

Kind regards,

 

Jeroen

Reply | Threaded
Open this post in threaded view
|

Re: [alert] 17289#0: open socket #14 left in 39 connection

Neelesh Gurjar
In reply to this post by Jeroen Steggink - CMS
I faced same problem in the begining. However it got resolved after setting following parameters properly:

user, worker_processes, worker_connections, keepalive_timeout, tcp_nopush, tcp_nodelay

Please post your ngix.conf to get the better idea.

Regards
NeeleshG


On Mon, Mar 16, 2009 at 6:06 PM, Jeroen Steggink - CMS <[hidden email]> wrote:
Hello,
 
I have installed Nginx 0.6.35 and got the following error:
 
[alert] 17289#0: open socket #14 left in 39 connection
 
After this error, the server crashed. At the time the server was under a high load with high disk I/O.
 
This is what 'nginx -V' returns:
 
nginx version: nginx/0.6.35
built by gcc 4.1.2 20080704 (Red Hat 4.1.2-44)
configure arguments: --with-cpu-opt=amd64 --without-http_autoindex_module --without-http_fastcgi_module --without-http_proxy_module --with-http_ssl_module --with-http_stub_status_module --without-http_ssi_module --without-http_userid_module --add-module=/root/nginx-geoip-0.1 --with-md5=/usr/lib64 --with-sha1=/usr/lib64 --prefix=/opt/nginx --sbin-path=/usr/sbin/nginx --conf-path=/etc/nginx/nginx.conf --pid-path=/var/run/nginx.pid --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --user=www --group=www
 
What could be the problem?
 
Kind regards,
 
Jeroen



--
Regards
NeeleshG

LINUX is basically a simple operating system, but you have to be a genius to understand the simplicity
Reply | Threaded
Open this post in threaded view
|

RE: [alert] 17289#0: open socket #14 left in 39 connection

Jeroen Steggink - CMS
Hi NeeleshG,
 
These are the relevant settings:
 
user              www www;
worker_processes  2;
 
events {
    worker_connections  1024;
}
## Size Limits
client_body_buffer_size   8k;
client_header_buffer_size 1k;
client_max_body_size      1k;
large_client_header_buffers 1 1k;
    
## Timeouts
client_body_timeout   5;
client_header_timeout 5;
keepalive_timeout     5 5;
send_timeout          5;
   
## General Options
ignore_invalid_headers   on;
limit_zone gulag $binary_remote_addr 1m;
recursive_error_pages    on;
sendfile                 on;
server_name_in_redirect off;
server_tokens           off; # hides version numbers    
   
## TCP options 
tcp_nodelay on;
tcp_nopush  on;
 
Cheers,
 
Jeroen


From: [hidden email] [mailto:[hidden email]] On Behalf Of Neelesh Gurjar
Sent: maandag 16 maart 2009 17:31
To: [hidden email]
Subject: Re: [alert] 17289#0: open socket #14 left in 39 connection

I faced same problem in the begining. However it got resolved after setting following parameters properly:

user, worker_processes, worker_connections, keepalive_timeout, tcp_nopush, tcp_nodelay

Please post your ngix.conf to get the better idea.

Regards
NeeleshG


On Mon, Mar 16, 2009 at 6:06 PM, Jeroen Steggink - CMS <[hidden email]> wrote:
Hello,
 
I have installed Nginx 0.6.35 and got the following error:
 
[alert] 17289#0: open socket #14 left in 39 connection
 
After this error, the server crashed. At the time the server was under a high load with high disk I/O.
 
This is what 'nginx -V' returns:
 
nginx version: nginx/0.6.35
built by gcc 4.1.2 20080704 (Red Hat 4.1.2-44)
configure arguments: --with-cpu-opt=amd64 --without-http_autoindex_module --without-http_fastcgi_module --without-http_proxy_module --with-http_ssl_module --with-http_stub_status_module --without-http_ssi_module --without-http_userid_module --add-module=/root/nginx-geoip-0.1 --with-md5=/usr/lib64 --with-sha1=/usr/lib64 --prefix=/opt/nginx --sbin-path=/usr/sbin/nginx --conf-path=/etc/nginx/nginx.conf --pid-path=/var/run/nginx.pid --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --user=www --group=www
 
What could be the problem?
 
Kind regards,
 
Jeroen



--
Regards
NeeleshG

LINUX is basically a simple operating system, but you have to be a genius to understand the simplicity
Reply | Threaded
Open this post in threaded view
|

Re: [alert] 17289#0: open socket #14 left in 39 connection

Neelesh Gurjar
Hi Jeroen,

A. Can you try following changes in your ngix.conf ?

1. Comment following lines:
client_body_buffer_size   8k;
client_header_buffer_size 1k;
client_max_body_size      1k;
large_client_header_buffers 1 1k;
   
client_body_timeout   5;
client_header_timeout 5;

2. Change following settings:
user       www
worker_connections  2048;

3. Enable logging error & access both logs

B. Are you using php+fastcgi? If yes then please see that whether it is running & configured with ngix properly or not?

Hope it will help you.

Regards
NeeleshG

On Mon, Mar 16, 2009 at 10:30 PM, Jeroen Steggink - CMS <[hidden email]> wrote:
Hi NeeleshG,
 
These are the relevant settings:
 
user              www www;
worker_processes  2;
 
events {
    worker_connections  1024;
}
## Size Limits
client_body_buffer_size   8k;
client_header_buffer_size 1k;
client_max_body_size      1k;
large_client_header_buffers 1 1k;
    
## Timeouts
client_body_timeout   5;
client_header_timeout 5;
keepalive_timeout     5 5;
send_timeout          5;
   
## General Options
ignore_invalid_headers   on;
limit_zone gulag $binary_remote_addr 1m;
recursive_error_pages    on;
sendfile                 on;
server_name_in_redirect off;
server_tokens           off; # hides version numbers    
   
## TCP options 
tcp_nodelay on;
tcp_nopush  on;
 
Cheers,
 
Jeroen


From: [hidden email] [mailto:[hidden email]] On Behalf Of Neelesh Gurjar
Sent: maandag 16 maart 2009 17:31
To: [hidden email]
Subject: Re: [alert] 17289#0: open socket #14 left in 39 connection

I faced same problem in the begining. However it got resolved after setting following parameters properly:

user, worker_processes, worker_connections, keepalive_timeout, tcp_nopush, tcp_nodelay

Please post your ngix.conf to get the better idea.

Regards
NeeleshG


On Mon, Mar 16, 2009 at 6:06 PM, Jeroen Steggink - CMS <[hidden email]> wrote:
Hello,
 
I have installed Nginx 0.6.35 and got the following error:
 
[alert] 17289#0: open socket #14 left in 39 connection
 
After this error, the server crashed. At the time the server was under a high load with high disk I/O.
 
This is what 'nginx -V' returns:
 
nginx version: nginx/0.6.35
built by gcc 4.1.2 20080704 (Red Hat 4.1.2-44)
configure arguments: --with-cpu-opt=amd64 --without-http_autoindex_module --without-http_fastcgi_module --without-http_proxy_module --with-http_ssl_module --with-http_stub_status_module --without-http_ssi_module --without-http_userid_module --add-module=/root/nginx-geoip-0.1 --with-md5=/usr/lib64 --with-sha1=/usr/lib64 --prefix=/opt/nginx --sbin-path=/usr/sbin/nginx --conf-path=/etc/nginx/nginx.conf --pid-path=/var/run/nginx.pid --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --user=www --group=www
 
What could be the problem?
 
Kind regards,
 
Jeroen



--
Regards
NeeleshG

LINUX is basically a simple operating system, but you have to be a genius to understand the simplicity



--
Regards
NeeleshG

LINUX is basically a simple operating system, but you have to be a genius to understand the simplicity
Reply | Threaded
Open this post in threaded view
|

RE: [alert] 17289#0: open socket #14 left in 39 connection

Jeroen Steggink - CMS
Hi NeeleshG,
 
A.
1. I have commented out the buffer and timeout lines.
2. Changed the user and worker_connections
3. Logging was already enabled.
 
B.
I'm just using it for static files.
 
It's working properly. It was working properly before as well. However, when I was generating a file of 10 GB on the same disk where the 'document root' is, that's when Nginx crashed.
I'll let you know if the new configuration works.
 
Cheers,
 
Jeroen
 


From: [hidden email] [mailto:[hidden email]] On Behalf Of Neelesh Gurjar
Sent: dinsdag 17 maart 2009 2:47
To: [hidden email]
Subject: Re: [alert] 17289#0: open socket #14 left in 39 connection

Hi Jeroen,

A. Can you try following changes in your ngix.conf ?

1. Comment following lines:
client_body_buffer_size   8k;
client_header_buffer_size 1k;
client_max_body_size      1k;
large_client_header_buffers 1 1k;
   
client_body_timeout   5;
client_header_timeout 5;

2. Change following settings:
user       www
worker_connections  2048;

3. Enable logging error & access both logs

B. Are you using php+fastcgi? If yes then please see that whether it is running & configured with ngix properly or not?

Hope it will help you.

Regards
NeeleshG

On Mon, Mar 16, 2009 at 10:30 PM, Jeroen Steggink - CMS <[hidden email]> wrote:
Hi NeeleshG,
 
These are the relevant settings:
 
user              www www;
worker_processes  2;
 
events {
    worker_connections  1024;
}
## Size Limits
client_body_buffer_size   8k;
client_header_buffer_size 1k;
client_max_body_size      1k;
large_client_header_buffers 1 1k;
    
## Timeouts
client_body_timeout   5;
client_header_timeout 5;
keepalive_timeout     5 5;
send_timeout          5;
   
## General Options
ignore_invalid_headers   on;
limit_zone gulag $binary_remote_addr 1m;
recursive_error_pages    on;
sendfile                 on;
server_name_in_redirect off;
server_tokens           off; # hides version numbers    
   
## TCP options 
tcp_nodelay on;
tcp_nopush  on;
 
Cheers,
 
Jeroen


From: [hidden email] [mailto:[hidden email]] On Behalf Of Neelesh Gurjar
Sent: maandag 16 maart 2009 17:31
To: [hidden email]
Subject: Re: [alert] 17289#0: open socket #14 left in 39 connection

I faced same problem in the begining. However it got resolved after setting following parameters properly:

user, worker_processes, worker_connections, keepalive_timeout, tcp_nopush, tcp_nodelay

Please post your ngix.conf to get the better idea.

Regards
NeeleshG


On Mon, Mar 16, 2009 at 6:06 PM, Jeroen Steggink - CMS <[hidden email]> wrote:
Hello,
 
I have installed Nginx 0.6.35 and got the following error:
 
[alert] 17289#0: open socket #14 left in 39 connection
 
After this error, the server crashed. At the time the server was under a high load with high disk I/O.
 
This is what 'nginx -V' returns:
 
nginx version: nginx/0.6.35
built by gcc 4.1.2 20080704 (Red Hat 4.1.2-44)
configure arguments: --with-cpu-opt=amd64 --without-http_autoindex_module --without-http_fastcgi_module --without-http_proxy_module --with-http_ssl_module --with-http_stub_status_module --without-http_ssi_module --without-http_userid_module --add-module=/root/nginx-geoip-0.1 --with-md5=/usr/lib64 --with-sha1=/usr/lib64 --prefix=/opt/nginx --sbin-path=/usr/sbin/nginx --conf-path=/etc/nginx/nginx.conf --pid-path=/var/run/nginx.pid --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --user=www --group=www
 
What could be the problem?
 
Kind regards,
 
Jeroen



--
Regards
NeeleshG

LINUX is basically a simple operating system, but you have to be a genius to understand the simplicity



--
Regards
NeeleshG

LINUX is basically a simple operating system, but you have to be a genius to understand the simplicity