Thread: iso-8859-1 Process DETAIL: Failed process was running: LISTEN dirty
Hi guys, we're receiving this kind of Abnormal terminations :
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
Thx in advance
Jorge Daniel Fernandez
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
Re: iso-8859-1 Process DETAIL: Failed process was running: LISTEN dirty
From
"David G. Johnston"
Date:
On Thursday, June 21, 2018, Jorge Daniel <elgaita@hotmail.com> wrote:
Hi guys, we're receiving this kind of Abnormal terminations :2018-06-19 14:11:02.394 PDT rhost= app=:user=:db=:LOG: server process (PID 235545) was terminated by signal 9: Killed2018-06-19 14:11:02.394 PDT rhost= app=:user=:db=:DETAIL: Failed process was running: LISTEN dirty2018-06-19 14:11:02.394 PDT rhost= app=:user=:db=:LOG: terminating any other active server processesDoes someone has information about "LISTEN DIRTY" as failed process, I've google it but no mention of this anywhere.
Kill 9 isn't abnormal, it's user initiated (usually anyway). Someone killed an open client session that had issued the LISTEN SQL command with a user-specific channel name of "dirty".
I'm unsure under what circumstances a session would be running a listen command long enough to be killed in this manner - but it might be normal as I have little experience with listen mechanics.
David J.
Re: iso-8859-1 Process DETAIL: Failed process was running: LISTEN dirty
From
"David G. Johnston"
Date:
On Thursday, June 21, 2018, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
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.
My random guess would be someone did:
Begin;
Listen dirty;
Walks away...
Someone/thing else sees a long running transaction and kills it.
OOM is just as likely though the listen showing as running just seems odd to me.
David J.