From: | Willy-Bas Loos <willybas(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | "setsockopt(TCP_KEEPCNT) failed: Invalid argument" on Debian Lenny |
Date: | 2009-12-11 09:06:48 |
Message-ID: | 1dd6057e0912110106i5960300buf034b49f53d4262b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
I get lots of errors in my logs saying:
LOG: setsockopt(TCP_KEEPCNT) failed: Invalid argument
The corresponding value in postgresql.conf is:
tcp_keepalives_count = 200 # TCP_KEEPCNT;
# 0 selects the system default
I intend to keep that connection alive for 200*75 seconds.
Does anyone know the max for tcp_keepalives_count?
==in man 7 tcp (debian lenny)==
tcp_keepalive_intvl (integer; default: 75)
The number of seconds between TCP keep-alive probes.
tcp_keepalive_probes (integer; default: 9)
The maximum number of TCP keep-alive probes to send
before giving up and killing the connection if no response is obtained
from the other end.
tcp_keepalive_time (integer; default: 7200)
The number of seconds a connection needs to be
idle before TCP begins sending out keep-alive probes. Keep-alives are
only sent when the SO_KEEPALIVE socket
option is enabled. The default value is 7200 seconds (2
hours). An idle connection is terminated after approximately an
additional 11 minutes (9 probes an
interval of 75 seconds apart) when keep-alive is enabled.
Cheers,
WBL
--
"Patriotism is the conviction that your country is superior to all
others because you were born in it." -- George Bernard Shaw
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2009-12-11 09:08:13 | Re: Postgres.exe Process taking too much memory and CPU usage - making the system extremely slow. |
Previous Message | Massa, Harald Armin | 2009-12-11 09:02:25 | Re: Postgres.exe Process taking too much memory and CPU usage - making the system extremely slow. |