From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Jorge Daniel <elgaita@hotmail.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Unknown Process DETAIL: Failed process was running: LISTEN dirty
Date: Thu, 21 Jun 2018 21:01:46 +0200
Message-ID: <1529607706.3218.2.camel@cybertec.at> (raw)
In-Reply-To: <CP2P152MB0355C1F6EE35E1CFD4F89F8DBC760@CP2P152MB0355.LAMP152.PROD.OUTLOOK.COM>
References: <CP2P152MB0355C1F6EE35E1CFD4F89F8DBC760@CP2P152MB0355.LAMP152.PROD.OUTLOOK.COM>
Jorge Daniel wrote:
> 2018-06-19 14:11:02.394 PDT rhost= app=:user=:db=:LOG: server process (PID 235545) was terminated by signal 9: Killed
> 2018-06-19 14:11:02.394 PDT rhost= app=:user=:db=:DETAIL: Failed process was running: LISTEN dirty
> 2018-06-19 14:11:02.394 PDT rhost= app=:user=:db=:LOG: terminating any other active server processes
The "LISTEN dirty" is nice, but it has nothing to do with your problem.
If you are not aware of any programs or people at large on your
system that might "kill -9" harmless processes, you might have
fallen prey to the OOM killer.
Check your kernel log for message to confirm that.
That would mean that you have run out of memory.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, elgaita@hotmail.com
Subject: Re: Unknown Process DETAIL: Failed process was running: LISTEN dirty
In-Reply-To: <1529607706.3218.2.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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