From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | "sivapostgres(at)yahoo(dot)com" <sivapostgres(at)yahoo(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Issue in PG start |
Date: | 2021-05-09 16:43:26 |
Message-ID: | 56ce5050-8273-be1c-f51f-a3ae46177cdd@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/8/21 7:32 PM, sivapostgres(at)yahoo(dot)com wrote:
> Yesterday's log file. Till we shut down the windows the message was:
> 2021-05-08 19:03:32.151 IST [10376] FATAL: the database system is
> starting up
> 2021-05-08 19:03:42.210 IST [7568] FATAL: the database system is
> starting up
Comments in line below.
>
>
> Today morning log file, I tried to start the service [ after setting the
> startup type to Manual ] twice
> ***********************************
> 2021-05-09 07:43:02.122 IST [16776] LOG: test message did not get
> through on socket for statistics collector
Something is blocking the socket.
Do you have anti-virus software on this machine?
> 2021-05-09 07:43:02.122 IST [16776] LOG: trying another address for the
> statistics collector
> 2021-05-09 07:43:02.624 IST [16776] LOG: test message did not get
> through on socket for statistics collector
> 2021-05-09 07:43:02.624 IST [16776] LOG: disabling statistics collector
> for lack of working socket
> 2021-05-09 07:43:02.624 IST [16776] WARNING: autovacuum not started
> because of misconfiguration
> 2021-05-09 07:43:02.624 IST [16776] HINT: Enable the "track_counts" option.
You should take care of this by following the HINT.
> 2021-05-09 07:43:02.685 IST [17144] LOG: database system was
> interrupted; last known up at 2021-05-07 18:46:00 IST
> 2021-05-09 07:43:04.489 IST [17196] FATAL: the database system is
> starting up
...
> 2021-05-09 07:45:14.796 IST [17144] LOG: database system was not
> properly shut down; automatic recovery in progress
> 2021-05-09 07:45:14.864 IST [17144] LOG: redo starts at 2/88985C80
> 2021-05-09 07:45:14.866 IST [17144] LOG: invalid record length at
> 2/889872B8: wanted 24, got 0
> 2021-05-09 07:45:14.866 IST [17144] LOG: redo done at 2/88987280
> 2021-05-09 07:45:14.866 IST [17144] LOG: last completed transaction was
> at log time 2021-05-07 18:48:44.227574+05:30
> 2021-05-09 07:45:15.046 IST [16776] LOG: database system is ready to
> accept connections
> 2021-05-09 07:50:17.295 IST [17204] ERROR: canceling statement due to
> user request
So did you or someone else do the above and the below manually or was
this coming from the system?
> 2021-05-09 07:50:17.300 IST [16776] LOG: received fast shutdown request
> 2021-05-09 07:50:17.322 IST [4408] LOG: could not receive data from
> client: An existing connection was forcibly closed by the remote host.
Are you connecting to database from outside the machine and if so is
that from a local network or a remote one?
>
> 2021-05-09 07:50:17.412 IST [16776] LOG: aborting any active transactions
> 2021-05-09 07:50:17.419 IST [16776] LOG: background worker "logical
> replication launcher" (PID 17204) exited with exit code 1
> 2021-05-09 07:50:17.548 IST [11032] LOG: shutting down
> 2021-05-09 07:50:17.607 IST [16776] LOG: database system is shut down
> **********************************************
See more below.
>
> Log file after a re-start
> ***************************************
> 2021-05-09 07:52:40.341 IST [13220] LOG: test message did not get
> through on socket for statistics collector
> 2021-05-09 07:52:40.342 IST [13220] LOG: trying another address for the
> statistics collector
> 2021-05-09 07:52:40.844 IST [13220] LOG: test message did not get
> through on socket for statistics collector
> 2021-05-09 07:52:40.844 IST [13220] LOG: disabling statistics collector
> for lack of working socket
> 2021-05-09 07:52:40.845 IST [13220] WARNING: autovacuum not started
> because of misconfiguration
> 2021-05-09 07:52:40.845 IST [13220] HINT: Enable the "track_counts" option.
> 2021-05-09 07:52:40.904 IST [13860] LOG: database system was shut down
> at 2021-05-09 07:50:17 IST
> 2021-05-09 07:52:41.122 IST [13220] LOG: database system is ready to
> accept connections
> 2021-05-09 07:55:23.628 IST [11188] LOG: using stale statistics instead
> of current ones because stats collector is not responding
> *****************************************
>
> Not sure what happened, it's working now. Any idea of what happened and
> what should we do to prevent re-occurance ?
It's up but not really working. Both the statistics collector and the
autovacuum processes are down. They are both important for the operation
of the database.
>
> Happiness Always
> BKR Sivaprakash
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | rob stan | 2021-05-09 21:20:01 | Setting wal_keep_segments parameter |
Previous Message | Ron | 2021-05-09 03:35:01 | Re: Issue in PG start |