Re: autoovacuum launcher process

Hi Vanish,
Thank you for your reply,
Do you think timescaledb is causing this problem? I can't see any log about
Timescaledb before the problem, but there are many logs after that.

2021-09-10 01:00:32.691 156668 FATAL: cannot read pg_class without
having selected a database
2021-09-10 01:00:33.356 110257 LOG: autovacuum launcher process (PID
156668) exited with exit code 1
...

2021-09-10 01:02:27.810 146444 LOG: *TimescaleDB* background worker
limit of 8 exceeded
2021-09-10 01:02:27.810 146444 HINT: Consider increasing *timescaledb*
.max_background_workers.

Avinash Vallarapu <avinash(dot)vallarapu(at)gmail(dot)com>, 13 Eyl 2021 Pzt, 14:39
tarihinde şunu yazdı:

> Hi,
>
> On Mon., Sep. 13, 2021, 2:04 a.m. liam saffioti, <liam(dot)saffiotti(at)gmail(dot)com>
> wrote:
>
>> Ok, my extensions list is;
>> hypopg
>> pg_buffercache
>> pg_partman
>> pg_stat_kcache
>> pg_stat_statements
>> timescaledb
>>
> Reason I asked this question is, I see the pg_class specific error
> messages you see in logs with timescaledb.
>
>> powa
>> postgres_fdw
>> btree_gin
>> btree_gist
>> plpythonu
>> uuid-ossp
>> plpgsql
>>
>> >> It would also be wise to look at dmesg or /var/log/messages and see if
>> there is anything interesting around what could have terminated one of the
>> processes.
>>
>> I looked /var/log/messages, I suspected OOM killer, but there is no any
>> log about it, or "terminate" etc.
>>
>>
>> Sep 10 01:00:41 pg_rhel02 patroni: 2021-09-10 01:00:41,186 INFO: Lock
>> owner: pg_rhel02; I am pg_rhel02
>> Sep 10 01:00:41 pg_rhel02 patroni: 2021-09-10 01:00:41,667 INFO:
>> establishing a new patroni connection to the postgres cluster
>> Sep 10 01:00:44 pg_rhel02 patroni: 2021-09-10 01:00:44,708 WARNING: Retry
>> got exception: 'connection problems'
>> Sep 10 01:00:45 pg_rhel02 journal: Suppressed 89852 messages from
>> /system.slice/auditd.service
>> Sep 10 01:00:47 pg_rhel02 patroni: localhost:5432 - no response
>> Sep 10 01:00:47 pg_rhel02 patroni: 2021-09-10 01:00:47,764 INFO: Error
>> communicating with PostgreSQL. Will try again later
>> Sep 10 01:00:51 pg_rhel02 patroni: 2021-09-10 01:00:51,186 INFO: Lock
>> owner: pg_rhel02; I am pg_rhel02
>> Sep 10 01:00:51 pg_rhel02 patroni: 2021-09-10 01:00:51,186 INFO:
>> establishing a new patroni connection to the postgres cluster
>> Sep 10 01:00:54 pg_rhel02 patroni: 2021-09-10 01:00:54,832 INFO:
>> establishing a new patroni connection to the postgres cluster
>> Sep 10 01:00:57 pg_rhel02 patroni: 2021-09-10 01:00:57,837 WARNING: Retry
>> got exception: 'connection problems'
>> Sep 10 01:01:00 pg_rhel02 patroni: localhost:5432 - no response
>>
>>
>> Avinash Vallarapu <avinash(dot)vallarapu(at)gmail(dot)com>, 13 Eyl 2021 Pzt, 07:12
>> tarihinde şunu yazdı:
>>
>>> Hi Liam,
>>>
>>> On Mon, Sep 13, 2021 at 12:52 AM liam saffioti <liam(dot)saffiotti(at)gmail(dot)com>
>>> wrote:
>>>
>>>> Hello again,
>>>> I grepped the db log with PID 156668, the result is below;
>>>>
>>>> # more pg_cluster-Fri.log | grep 156668
>>>> 2021-09-10 01:00:32.691 156668 FATAL: cannot read pg_class
>>>> without having selected a database
>>>>
>>> Though it sounds like an unrelated question, what is the unique list of
>>> extensions you got in all your database(s) ?
>>>
>>> \dx
>>>
>>> 2021-09-10 01:00:33.356 110257 LOG: autovacuum launcher process
>>>> (PID 156668) exited with exit code 1
>>>>
>>> It would also be wise to look at dmesg or /var/log/messages and see if
>>> there is anything interesting around what could have terminated one of the
>>> processes.
>>>
>>>>
>>>> sincerely,
>>>> Liam
>>>>
>>>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 12 Eyl 2021 Paz, 17:12 tarihinde şunu
>>>> yazdı:
>>>>
>>>>> liam saffioti <liam(dot)saffiotti(at)gmail(dot)com> writes:
>>>>> > 2021-09-10 01:00:33.356 110257 LOG: autovacuum launcher
>>>>> process (PID
>>>>> > 156668) exited with exit code 1
>>>>>
>>>>> The interesting log entry(s) would be before this one. You sure PID
>>>>> 156668 didn't log anything before dying?
>>>>>
>>>>> regards, tom lane
>>>>>
>>>>
>>>
>>> --
>>> Regards,
>>> Avinash Vallarapu
>>> CEO
>>> MigOps, Inc.
>>>
>>
>