Re: Terminating connection because of crash of another server process

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Deo Felix <deofelix9(at)gmail(dot)com>, Deepak Goel <deicool(at)gmail(dot)com>
Cc: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Terminating connection because of crash of another server process
Date: 2023-09-29 09:27:33
Message-ID: 428f8ffe02b21f97f48887a2c6c97dd893cdbd8f.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Fri, 2023-09-29 at 11:21 +0300, Deo Felix wrote:
> Please find the screenshot of  error from the log file  postgresqlerror.png

It is really amazing how much effort you make *not* to share
any relevant information with us. But there is finally some
interesting message hidden in your image:

server process (PID 14257) was terminated by signal 9: Killed

Since I don't expect that random users on your server machine
go around "kill -9"-ing PostgreSQL processes, it is very likely
that PostgreSQL is crashed by the Linux out-of-memory killer.

You should disable memory overcommit, see
https://www.postgresql.org/docs/current/kernel-resources.html#LINUX-MEMORY-OVERCOMMIT

Then you will start getting "out of memory" errors instead of
crashes. To combat these, reduce the memory usage parameters,
mostly "work_mem", or reduce the number of active database sessions
by using a connection pool.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message bitcoin wallet 2023-09-30 18:55:11 Re: Backup solution over unreliable network
Previous Message Deepak Goel 2023-09-29 08:41:05 Re: Terminating connection because of crash of another server process