Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1emgT2-0006Zl-Qp for pgsql-admin@arkaria.postgresql.org; Fri, 16 Feb 2018 13:54:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1emgT0-0005RP-6n for pgsql-admin@arkaria.postgresql.org; Fri, 16 Feb 2018 13:54:22 +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 1emgSz-0005R9-CJ for pgsql-admin@lists.postgresql.org; Fri, 16 Feb 2018 13:54:22 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1emgSw-0001z6-6V for pgsql-admin@lists.postgresql.org; Fri, 16 Feb 2018 13:54:20 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B01DE20C91; Fri, 16 Feb 2018 08:54:16 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Fri, 16 Feb 2018 08:54:16 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=HyPNg819nGzcfbqC7gfnrZU6Vj+85 qZzjAezNEpR4U0=; b=dctkB5leVn296jZPmwB0mTsXkstJYO+jlFWOusxVGpdDI YV4AZE1ZAZvvKLn+FIWAXekuFd38RSbJYR9s+4itnObFa1Ui946ptgN4EDfYTHkk VvXt0eekYjFXzRhnKMUvqSYiW3Rozsm0DlzmHUt1G0Dy9J9oX8xf8pWOKwZ6FY/c EOIwBYBb5MdHCTluHBJxdDjmqoCorWQuhlFuFhOjUSEixDt7ot1J1K5r652DJCH9 3x7OTEhlVsiy+a94Mvh9wlkrFrHGPopiWtmzCz4oskP0AZ6Ua2xJOwcqwqG1FLDp BFWRDi6tA5v3pHqi94qew5wLNXeICU/RMpPtAmnfw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=HyPNg8 19nGzcfbqC7gfnrZU6Vj+85qZzjAezNEpR4U0=; b=c1ilnuocWtpCq0IqOGvMGP eGLOmC4fTdUtbUvTV9MVSuC9P7mgvbqCXsGL2AAjTpYclmSp1aUZCwrsDguC2jbI CAs7V35AjXV6O9mErw7EMchxW6w6CMh2rJnGqkEvcVNzdZTCfmEmNVr9VdwS9bdj h3+J6CQ+An/fjUaz28S5P7SqDVK5RnaXAN1CvHoZTJlS32Js27Hvjzb4pT+6HKXh ++4C71X4tvd/yFcevrMDyg/m4Cqpj6/116tf2MkY8VxslneL6KkqBi6UNzqbiDCw dXWXgSTBZnloWvzDpGI14cquchtH2Ldii5jkqlqcz/ScEEoiH+38mpqysMbJn1Aw == X-ME-Sender: Received: from [192.168.1.3] (71-212-36-41.tukw.qwest.net [71.212.36.41]) by mail.messagingengine.com (Postfix) with ESMTPA id F0CA77E34D; Fri, 16 Feb 2018 08:54:15 -0500 (EST) Subject: Re: postgres started without auto vaccum To: Azimuddin Mohammed , Postgres General , pgsql-admin@postgresql.org, pgsql-admin@lists.postgresql.org References: From: Adrian Klaver Message-ID: <1bfb2bdd-2606-bd26-5cb9-13827e94ce1c@aklaver.com> Date: Fri, 16 Feb 2018 05:54:14 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 02/15/2018 09:54 PM, Azimuddin Mohammed wrote: > Hello All, > I am getting below Warning messages in logs after starting postgres, can > some please help me here > > LOG: could not bind socket for statistics collector: Cannot assign > requested address > > LOG: disabling statistics collector for lack of working socket > > WARNING: autovacuum not started because of misconfiguration > > HINT : Enable the "track_counts" option. > > MultiXact member wraparound protections are now enabled > > > I tried enabling track_counts but it did not help. Did you restart the server after making the change? Did Postgres start without the warnings previous to this? > > > Any guidance is much appreciated here. > > > Thanks in Advance! > > > > -- > > Regards, > Azim > -- Adrian Klaver adrian.klaver@aklaver.com