pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedMemory Issues.
3+ messages / 3 participants
[nested] [flat]
* Memory Issues.
@ 2020-12-22 07:32 Sreejith P <sreejith@lifetrenz.com>
0 siblings, 1 reply; 3+ messages in thread
From: Sreejith P @ 2020-12-22 07:32 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Dear All,
Am getting this issue very frequently.
Can some one help.
2020-12-21 23:59:32.869 +04 [16097] rptDBA@Ast-ReportDB LOG: could not receive data from client: Connection timed out
2020-12-22 01:12:53.939 +04 [11961] rptDBA@Ast-ReportDB LOG: could not receive data from client: Connection reset by peer
2020-12-22 01:23:08.832 +04 [30360] LOG: server process (PID 17872) was terminated by signal 9: Killed
2020-12-22 01:23:08.832 +04 [30360] DETAIL: Failed process was running: autovacuum: ANALYZE public.lt_encounter
2020-12-22 01:23:08.926 +04 [30360] LOG: terminating any other active server processes
2020-12-22 01:23:08.927 +04 [14266] rptDBA@Ast-ReportDB WARNING: terminating connection because of crash of another server process
2020-12-22 01:23:08.927 +04 [14266] rptDBA@Ast-ReportDB DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2020-12-22 01:23:08.927 +04 [14266] rptDBA@Ast-ReportDB HINT: In a moment you should be able to reconnect to the database and repeat your command.
2020-12-22 01:23:08.927 +04 [14254] rptDBA@Ast-ReportDB WARNING: terminating connection because of crash of another server process
2020-12-22 01:23:08.927 +04 [14254] rptDBA@Ast-ReportDB DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2020-12-22 01:23:08.927 +04 [14254] rptDBA@Ast-ReportDB HINT: In a moment you should be able to reconnect to the database and repeat your command.
2020-12-22 01:23:08.927 +04 [6235] rptDBA@Ast-ReportDB WARNING: terminating connection because of crash of another server process
2020-12-22 01:23:08.927 +04 [6235] rptDBA@Ast-ReportDB DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2020-12-22 01:23:08.927 +04 [6235] rptDBA@Ast-ReportDB HINT: In a moment you should be able to reconnect to the database and repeat your command.
2020-12-22 01:23:08.927 +04 [30367] WARNING: terminating connection because of crash of another server process
2020-12-22 01:23:08.927 +04 [30367] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2020-12-22 01:23:08.927 +04 [30367] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2020-12-22 01:23:08.927 +04 [16838] rptDBA@Ast-ReportDB WARNING: terminating connection because of crash of another server process
2020-12-22 01:23:08.927 +04 [16838] rptDBA@Ast-ReportDB DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2020-12-22 01:23:08.927 +04 [16838] rptDBA@Ast-ReportDB HINT: In a moment you should be able to reconnect to the database and repeat your command.
2020-12-22 01:23:09.027 +04 [17854] rptDBA@Ast-ReportDB WARNING: terminating connection because of crash of another server process
2020-12-22 01:23:09.027 +04 [17854] rptDBA@Ast-ReportDB DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2020-12-22 01:23:09.027 +04 [17854] rptDBA@Ast-ReportDB HINT: In a moment you should be able to reconnect to the database and repeat your command.
Thanks
Sreejith
--
*Solutions for Care Anywhere*
*dWise HealthCare IT Solutions Pvt.
Ltd.* | www.lifetrenz.com <http://www.lifetrenz.com;
*Disclaimer*:
The
information and attachments contained in this email are intended
for
exclusive use of the addressee(s) and may contain confidential or
privileged information. If you are not the intended recipient, please
notify the sender immediately and destroy all copies of this message and
any attachments. The views expressed in this email are, unless
otherwise
stated, those of the author and not those of dWise HealthCare IT Solutions
or its management.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Memory Issues.
@ 2020-12-22 14:09 hubert depesz lubaczewski <depesz@depesz.com>
parent: Sreejith P <sreejith@lifetrenz.com>
0 siblings, 1 reply; 3+ messages in thread
From: hubert depesz lubaczewski @ 2020-12-22 14:09 UTC (permalink / raw)
To: Sreejith P <sreejith@lifetrenz.com>; +Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
On Tue, Dec 22, 2020 at 07:32:04AM +0000, Sreejith P wrote:
> Dear All,
> 2020-12-21 23:59:32.869 +04 [16097] rptDBA@Ast-ReportDB LOG: could not receive data from client: Connection timed out
> 2020-12-22 01:12:53.939 +04 [11961] rptDBA@Ast-ReportDB LOG: could not receive data from client: Connection reset by peer
> 2020-12-22 01:23:08.832 +04 [30360] LOG: server process (PID 17872) was terminated by signal 9: Killed
One of Pg processes (with PID 17872) was killed with signal 9 (sigkill).
It could be operator killing process, some automation, or so called
"oom killer".
Pg can't really do anything about being killed in this way, so you have
to track down what is issuing this kill signal, and disable it.
I'd suggest to try with system logs.
Best regards,
depesz
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Memory Issues.
@ 2020-12-22 14:50 Scott Ribe <scott_ribe@elevated-dev.com>
parent: hubert depesz lubaczewski <depesz@depesz.com>
0 siblings, 0 replies; 3+ messages in thread
From: Scott Ribe @ 2020-12-22 14:50 UTC (permalink / raw)
To: hubert depesz lubaczewski <depesz@depesz.com>; +Cc: Sreejith P <sreejith@lifetrenz.com>; pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
> On Dec 22, 2020, at 7:09 AM, hubert depesz lubaczewski <depesz@depesz.com> wrote:
>
> Pg can't really do anything about being killed in this way, so you have
> to track down what is issuing this kill signal, and disable it.
For me, a recent case was an extension we were trying out...
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2020-12-22 14:50 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-12-22 07:32 Memory Issues. Sreejith P <sreejith@lifetrenz.com>
2020-12-22 14:09 ` hubert depesz lubaczewski <depesz@depesz.com>
2020-12-22 14:50 ` Scott Ribe <scott_ribe@elevated-dev.com>
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