From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | lizenko79(at)gmail(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #14720: getsockopt(TCP_KEEPALIVE) failed: Option not supported by protocol |
Date: | 2017-06-27 19:17:32 |
Message-ID: | 20170627191732.bqh677xgt5bbdo7t@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
lizenko79(at)gmail(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 14720
> Logged by: Andrey Lizenko
> Email address: lizenko79(at)gmail(dot)com
> PostgreSQL version: 9.6.3
> Operating system: Solaris 11.3
> Description:
>
> I've got the following message running PostgreSQL 9.6.3 on Solaris 11.3
> (both latest stable).
>
> > getsockopt(TCP_KEEPALIVE) failed: Option not supported by protocol
>
> Unfortunately, I can not reproduce it with libpq c code examples, but at
> least I can see it while using pgAdmin 3 , pgAdmin 4 and zabbix monitoring
> extension libzbxpgsql.
>
> In getsockopt manual only SO_KEEPALIVE mentioned.
It sounds like your system defines the TCP_KEEPALIVE symbol at compile
time but the kernel doesn't know it; maybe the package was compiled in a
system where the kernel does support that option, and you're running it
in one that doesn't?
Are you getting the message in the client side or server side? If the
latter, you should just set tcp_keepalives_idle to 0 in postgresql.conf.
If the former, I think the only option is to fix the libpq compile.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Garton | 2017-06-27 19:52:49 | Re: BUG #14719: Logical replication unexpected behaviour when target table has missing columns |
Previous Message | Greg Stark | 2017-06-27 16:50:54 | Re: Bus error in formatting.c NUM_numpart_to_char (9.4.12, 9.6.3, sparc) |