postgres started without auto vaccum

On 16 February 2018 06:54:43 CET, Azimuddin Mohammed <azimeiu@gmail.com> 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.

Any guidance is much appreciated here.

Thanks in Advance!

Which operating system? Please disable all firewalls and try it again.

Regards, Andreas.

--
2ndQuadrant - The PostgreSQL Support Company

Its on rhel 7.3 , i cant disable firewal, its on one of my company dev
server.

On Feb 16, 2018 12:21 AM, "Andreas Kretschmer" <andreas@a-kretschmer.de>
wrote:

Am 16.02.2018 um 07:23 schrieb Azimuddin Mohammed:

Its on rhel 7.3 , i cant disable firewal, its on one of my company dev
server.

On Feb 16, 2018 12:21 AM, "Andreas Kretschmer"
<andreas@a-kretschmer.de <mailto:andreas@a-kretschmer.de>> wrote:

On 16 February 2018 06:54:43 CET, Azimuddin Mohammed
<azimeiu@gmail.com <mailto:azimeiu@gmail.com>> 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

the stats collector is using UDP sockets, maybe your firewall is
blocking that.

Regards, Andreas

--
2ndQuadrant - The PostgreSQL Support Company.
www.2ndQuadrant.com

https://bugzilla.redhat.com/show_bug.cgi?id=849428

<https://www.avast.com/sig-email?utm_medium=email&amp;utm_source=link&amp;utm_campaign=sig-email&amp;utm_content=webmail&gt;
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&amp;utm_source=link&amp;utm_campaign=sig-email&amp;utm_content=webmail&gt;
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Fri, Feb 16, 2018 at 11:51 AM, Andreas Kretschmer <
andreas@a-kretschmer.de> wrote:

On 16 February 2018 06:54:43 CET, Azimuddin Mohammed <azimeiu@gmail.com>
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.

Any guidance is much appreciated here.

Thanks in Advance!

Which operating system? Please disable all firewalls and try it again.

Regards, Andreas.

--
2ndQuadrant - The PostgreSQL Support Company

--
Pradeep

please see

https://bugzilla.redhat.com/show_bug.cgi?id=849428

--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html

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

Yes, I did. The first start happened without any issues. But the next
restart i see the errors.

On Feb 16, 2018 7:54 AM, "Adrian Klaver" <adrian.klaver@aklaver.com> wrote:

On Fri, Feb 16, 2018 at 12:21 PM, Azimuddin Mohammed <azimeiu@gmail.com>
wrote:

Yes, I did. The first start happened without any issues. But the next
restart i see the errors.

On Feb 16, 2018 7:54 AM, "Adrian Klaver" <adrian.klaver@aklaver.com>
wrote:

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

*Check that file postmaster.pid does NOT exist in the postgres data
directory AFTER you stop postgres.*

*If it does, delete it, then attempt to restart.*

*If that file is detected on a start, then postgres thinks there is already
another postmaster running.*

--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.

On 02/16/2018 09:21 AM, Azimuddin Mohammed wrote:

Yes, I did. The first start happened without any issues. But the next
restart i see the errors.

Was the first start before you removed the data/ directory or after you
restored it?

If the first start was after the restore did anything else happen
between the starts?

--
Adrian Klaver
adrian.klaver@aklaver.com

Azimuddin Mohammed wrote:

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.

Any guidance is much appreciated here.

PostgreSQL could not bind to the UDP socket it created on "localhost".

There is some network misconfiguration; have a network specialist look at it.

You must fix the problem, else PostgreSQL will be unusable.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com