Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dPw0O-0007Gs-6v for pgsql-bugs@arkaria.postgresql.org; Tue, 27 Jun 2017 19:18:32 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dPw0N-00049M-K4 for pgsql-bugs@arkaria.postgresql.org; Tue, 27 Jun 2017 19:18:31 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dPvzc-0002nw-6A for pgsql-bugs@postgresql.org; Tue, 27 Jun 2017 19:17:44 +0000 Received: from mail-qk0-x236.google.com ([2607:f8b0:400d:c09::236]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dPvzU-0000nL-Qz for pgsql-bugs@postgresql.org; Tue, 27 Jun 2017 19:17:42 +0000 Received: by mail-qk0-x236.google.com with SMTP id r62so33721540qkf.0 for ; Tue, 27 Jun 2017 12:17:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=zma4UP4Amwkcr1lOFkQOsljcNRdg9dAZpT4ewU4R6ME=; b=tsT9rcQnew982WRzE82ZwxqhBgkw3RCaU+xbU0RNjrN+116NnqydkHtCafWBb1m8FC NqVUqlxDqvO9mi4ewMir+hDnq9O0aYk4YNugz3CkVP0ekDH9bprBOcNbBc6M5F9VtoCO zSgJCtLsynTTcBYLeDKwn8N+2icFepkT1/3DCxBNgW9QHAGXUxEJSGlR8WpLsnIQSUK0 4tSHoqLsH0PR7qpKJ0fiLYxVzEomn4SQpOoyrFuiCE1mgyPTWvx57LnYUtDlVq16/e9n Ezm68yCg2nTfarG203Y91E/K87OyarW3iXLmd3t99KFZVc29wPlPpc2pZNv4D6AGPUkK SWhQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=zma4UP4Amwkcr1lOFkQOsljcNRdg9dAZpT4ewU4R6ME=; b=p1HxjaSB5tJL4+yCFQebzdZCce3VtNI8Rwlt95PWOTyJmJLXN0BoX6eUiol6U6gqij jpJhs1ZJEpKvxl1Hr+07UUx+vta9qLmgcrNXXCPAcFfx1uVV4Nmc3XJaOvItU8QUdqiF QK0pwRDijxt8ccACnvY3sgJM/Hg5jarSC9c9U8BWuUH+u1Y8KfLRkoDE08rOgzVJPn4/ CI7gHpsXspPKgiwbZG+h8rgzVEI3Qf3b40M2s+Nr+LNaFD8bMQUPEm+Qvo5q8rAoY98Y wiLICbW6oTXHJJkXU/OyLzzMQVmpRv4/lBNYb863CfB1+P6ToudGHlpDXVswe5gq43A9 cFSg== X-Gm-Message-State: AKS2vOwwbqId4l362zo9Xam/TrOSZ39FNG4b4LMqzwkDvBxqv2srw9c1 YTff/XxuJILn9J2K X-Received: by 10.55.204.133 with SMTP id n5mr8568066qkl.135.1498591055683; Tue, 27 Jun 2017 12:17:35 -0700 (PDT) Received: from alvin.alvh.no-ip.org ([179.57.115.10]) by smtp.gmail.com with ESMTPSA id 27sm65499qty.2.2017.06.27.12.17.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Jun 2017 12:17:35 -0700 (PDT) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id CC3DCA5B; Tue, 27 Jun 2017 15:17:32 -0400 (-04) Date: Tue, 27 Jun 2017 15:17:32 -0400 From: Alvaro Herrera To: lizenko79@gmail.com Cc: pgsql-bugs@postgresql.org Subject: Re: BUG #14720: getsockopt(TCP_KEEPALIVE) failed: Option not supported by protocol Message-ID: <20170627191732.bqh677xgt5bbdo7t@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20170627163757.25161.528@wrigleys.postgresql.org> User-Agent: NeoMutt/20170306-137-4415bd-dirty (1.8.0) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-bugs Precedence: bulk Sender: pgsql-bugs-owner@postgresql.org lizenko79@gmail.com wrote: > The following bug has been logged on the website: > > Bug reference: 14720 > Logged by: Andrey Lizenko > Email address: lizenko79@gmail.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 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs