pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedpostgres started without auto vaccum
11+ messages / 7 participants
[nested] [flat]
* postgres started without auto vaccum
@ 2018-02-16 05:54 Azimuddin Mohammed <azimeiu@gmail.com>
2018-02-16 06:21 ` Re: postgres started without auto vaccum Andreas Kretschmer <andreas@a-kretschmer.de>
2018-02-16 07:32 ` Re: postgres started without auto vaccum pradeep <pradeep.kumar.pc@gmail.com>
2018-02-16 13:54 ` Re: postgres started without auto vaccum Adrian Klaver <adrian.klaver@aklaver.com>
2018-02-16 19:08 ` Re: postgres started without auto vaccum Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 4 replies; 11+ messages in thread
From: Azimuddin Mohammed @ 2018-02-16 05:54 UTC (permalink / raw)
To: Postgres General <pgsql-general@postgresql.org>; pgsql-admin; pgsql-admin@lists.postgresql.org
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!
--
Regards,
Azim
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgres started without auto vaccum
2018-02-16 05:54 postgres started without auto vaccum Azimuddin Mohammed <azimeiu@gmail.com>
@ 2018-02-16 06:21 ` Andreas Kretschmer <andreas@a-kretschmer.de>
2018-02-16 06:23 ` Re: postgres started without auto vaccum Azimuddin Mohammed <azimeiu@gmail.com>
2018-02-16 06:45 ` Re: postgres started without auto vaccum Pradeep Kumar <pradeep.kumar.pc@gmail.com>
3 siblings, 2 replies; 11+ messages in thread
From: Andreas Kretschmer @ 2018-02-16 06:21 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org,Azimuddin Mohammed <azimeiu@gmail.com>; Postgres General <pgsql-general@postgresql.org>; pgsql-admin; pgsql-admin@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgres started without auto vaccum
2018-02-16 05:54 postgres started without auto vaccum Azimuddin Mohammed <azimeiu@gmail.com>
2018-02-16 06:21 ` Re: postgres started without auto vaccum Andreas Kretschmer <andreas@a-kretschmer.de>
@ 2018-02-16 06:23 ` Azimuddin Mohammed <azimeiu@gmail.com>
2018-02-16 06:37 ` Re: postgres started without auto vaccum Andreas Kretschmer <andreas@a-kretschmer.de>
1 sibling, 1 reply; 11+ messages in thread
From: Azimuddin Mohammed @ 2018-02-16 06:23 UTC (permalink / raw)
To: Andreas Kretschmer <andreas@a-kretschmer.de>; +Cc: pgsql-general@lists.postgresql.org, Postgres General <pgsql-general@postgresql.org>; pgsql-admin; pgsql-admin@lists.postgresql.org
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:
> 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
>
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgres started without auto vaccum
2018-02-16 05:54 postgres started without auto vaccum Azimuddin Mohammed <azimeiu@gmail.com>
2018-02-16 06:21 ` Re: postgres started without auto vaccum Andreas Kretschmer <andreas@a-kretschmer.de>
2018-02-16 06:23 ` Re: postgres started without auto vaccum Azimuddin Mohammed <azimeiu@gmail.com>
@ 2018-02-16 06:37 ` Andreas Kretschmer <andreas@a-kretschmer.de>
0 siblings, 0 replies; 11+ messages in thread
From: Andreas Kretschmer @ 2018-02-16 06:37 UTC (permalink / raw)
To: Azimuddin Mohammed <azimeiu@gmail.com>; +Cc: pgsql-general@lists.postgresql.org, Postgres General <pgsql-general@postgresql.org>; pgsql-admin; pgsql-admin@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgres started without auto vaccum
2018-02-16 05:54 postgres started without auto vaccum Azimuddin Mohammed <azimeiu@gmail.com>
2018-02-16 06:21 ` Re: postgres started without auto vaccum Andreas Kretschmer <andreas@a-kretschmer.de>
@ 2018-02-16 06:45 ` Pradeep Kumar <pradeep.kumar.pc@gmail.com>
1 sibling, 0 replies; 11+ messages in thread
From: Pradeep Kumar @ 2018-02-16 06:45 UTC (permalink / raw)
To: Andreas Kretschmer <andreas@a-kretschmer.de>; +Cc: pgsql-general@lists.postgresql.org, Azimuddin Mohammed <azimeiu@gmail.com>; Postgres General <pgsql-general@postgresql.org>; pgsql-admin; pgsql-admin@lists.postgresql.org
https://bugzilla.redhat.com/show_bug.cgi?id=849428
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&...;
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&...;
<#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
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgres started without auto vaccum
2018-02-16 05:54 postgres started without auto vaccum Azimuddin Mohammed <azimeiu@gmail.com>
@ 2018-02-16 07:32 ` pradeep <pradeep.kumar.pc@gmail.com>
3 siblings, 0 replies; 11+ messages in thread
From: pradeep @ 2018-02-16 07:32 UTC (permalink / raw)
To: pgsql-admin
please see
https://bugzilla.redhat.com/show_bug.cgi?id=849428
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgres started without auto vaccum
2018-02-16 05:54 postgres started without auto vaccum Azimuddin Mohammed <azimeiu@gmail.com>
@ 2018-02-16 13:54 ` Adrian Klaver <adrian.klaver@aklaver.com>
2018-02-16 17:21 ` Re: postgres started without auto vaccum Azimuddin Mohammed <azimeiu@gmail.com>
3 siblings, 1 reply; 11+ messages in thread
From: Adrian Klaver @ 2018-02-16 13:54 UTC (permalink / raw)
To: Azimuddin Mohammed <azimeiu@gmail.com>; Postgres General <pgsql-general@postgresql.org>; pgsql-admin; pgsql-admin@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgres started without auto vaccum
2018-02-16 05:54 postgres started without auto vaccum Azimuddin Mohammed <azimeiu@gmail.com>
2018-02-16 13:54 ` Re: postgres started without auto vaccum Adrian Klaver <adrian.klaver@aklaver.com>
@ 2018-02-16 17:21 ` Azimuddin Mohammed <azimeiu@gmail.com>
2018-02-16 17:37 ` Re: postgres started without auto vaccum Melvin Davidson <melvin6925@gmail.com>
2018-02-16 17:42 ` Re: postgres started without auto vaccum Adrian Klaver <adrian.klaver@aklaver.com>
0 siblings, 2 replies; 11+ messages in thread
From: Azimuddin Mohammed @ 2018-02-16 17:21 UTC (permalink / raw)
To: Adrian Klaver <adrian.klaver@aklaver.com>; +Cc: Postgres General <pgsql-general@postgresql.org>; pgsql-admin; pgsql-admin@lists.postgresql.org
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
>
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgres started without auto vaccum
2018-02-16 05:54 postgres started without auto vaccum Azimuddin Mohammed <azimeiu@gmail.com>
2018-02-16 13:54 ` Re: postgres started without auto vaccum Adrian Klaver <adrian.klaver@aklaver.com>
2018-02-16 17:21 ` Re: postgres started without auto vaccum Azimuddin Mohammed <azimeiu@gmail.com>
@ 2018-02-16 17:37 ` Melvin Davidson <melvin6925@gmail.com>
1 sibling, 0 replies; 11+ messages in thread
From: Melvin Davidson @ 2018-02-16 17:37 UTC (permalink / raw)
To: Azimuddin Mohammed <azimeiu@gmail.com>; +Cc: Adrian Klaver <adrian.klaver@aklaver.com>; Postgres General <pgsql-general@postgresql.org>; pgsql-admin; pgsql-admin@lists.postgresql.org
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.
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgres started without auto vaccum
2018-02-16 05:54 postgres started without auto vaccum Azimuddin Mohammed <azimeiu@gmail.com>
2018-02-16 13:54 ` Re: postgres started without auto vaccum Adrian Klaver <adrian.klaver@aklaver.com>
2018-02-16 17:21 ` Re: postgres started without auto vaccum Azimuddin Mohammed <azimeiu@gmail.com>
@ 2018-02-16 17:42 ` Adrian Klaver <adrian.klaver@aklaver.com>
1 sibling, 0 replies; 11+ messages in thread
From: Adrian Klaver @ 2018-02-16 17:42 UTC (permalink / raw)
To: Azimuddin Mohammed <azimeiu@gmail.com>; +Cc: Postgres General <pgsql-general@postgresql.org>; pgsql-admin; pgsql-admin@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgres started without auto vaccum
2018-02-16 05:54 postgres started without auto vaccum Azimuddin Mohammed <azimeiu@gmail.com>
@ 2018-02-16 19:08 ` Laurenz Albe <laurenz.albe@cybertec.at>
3 siblings, 0 replies; 11+ messages in thread
From: Laurenz Albe @ 2018-02-16 19:08 UTC (permalink / raw)
To: Azimuddin Mohammed <azimeiu@gmail.com>; Postgres General <pgsql-general@postgresql.org>; pgsql-admin; pgsql-admin@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 11+ messages in thread
end of thread, other threads:[~2018-02-16 19:08 UTC | newest]
Thread overview: 11+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-02-16 05:54 postgres started without auto vaccum Azimuddin Mohammed <azimeiu@gmail.com>
2018-02-16 06:21 ` Andreas Kretschmer <andreas@a-kretschmer.de>
2018-02-16 06:23 ` Azimuddin Mohammed <azimeiu@gmail.com>
2018-02-16 06:37 ` Andreas Kretschmer <andreas@a-kretschmer.de>
2018-02-16 06:45 ` Pradeep Kumar <pradeep.kumar.pc@gmail.com>
2018-02-16 07:32 ` pradeep <pradeep.kumar.pc@gmail.com>
2018-02-16 13:54 ` Adrian Klaver <adrian.klaver@aklaver.com>
2018-02-16 17:21 ` Azimuddin Mohammed <azimeiu@gmail.com>
2018-02-16 17:37 ` Melvin Davidson <melvin6925@gmail.com>
2018-02-16 17:42 ` Adrian Klaver <adrian.klaver@aklaver.com>
2018-02-16 19:08 ` Laurenz Albe <laurenz.albe@cybertec.at>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox