pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedUnknown Process DETAIL: Failed process was running: LISTEN dirty
4+ messages / 3 participants
[nested] [flat]
* Unknown Process DETAIL: Failed process was running: LISTEN dirty
@ 2018-06-21 18:32 Jorge Daniel <elgaita@hotmail.com>
0 siblings, 2 replies; 4+ messages in thread
From: Jorge Daniel @ 2018-06-21 18:32 UTC (permalink / raw)
To: pgsql-admin
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
Does someone has information about "LISTEN DIRTY" as failed process, I've google it but no mention of this anywhere.
Thx in advance
Jorge Daniel Fernandez
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Unknown Process DETAIL: Failed process was running: LISTEN dirty
@ 2018-06-21 19:01 Laurenz Albe <laurenz.albe@cybertec.at>
parent: Jorge Daniel <elgaita@hotmail.com>
1 sibling, 1 reply; 4+ messages in thread
From: Laurenz Albe @ 2018-06-21 19:01 UTC (permalink / raw)
To: Jorge Daniel <elgaita@hotmail.com>; pgsql-admin
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
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Unknown Process DETAIL: Failed process was running: LISTEN dirty
@ 2018-06-21 19:02 David G. Johnston <david.g.johnston@gmail.com>
parent: Jorge Daniel <elgaita@hotmail.com>
1 sibling, 0 replies; 4+ messages in thread
From: David G. Johnston @ 2018-06-21 19:02 UTC (permalink / raw)
To: Jorge Daniel <elgaita@hotmail.com>; +Cc: pgsql-admin
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: 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
>
> Does 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.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Unknown Process DETAIL: Failed process was running: LISTEN dirty
@ 2018-06-21 19:05 David G. Johnston <david.g.johnston@gmail.com>
parent: Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 0 replies; 4+ messages in thread
From: David G. Johnston @ 2018-06-21 19:05 UTC (permalink / raw)
To: Laurenz Albe <laurenz.albe@cybertec.at>; +Cc: Jorge Daniel <elgaita@hotmail.com>; pgsql-admin
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.
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2018-06-21 19:05 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-06-21 18:32 Unknown Process DETAIL: Failed process was running: LISTEN dirty Jorge Daniel <elgaita@hotmail.com>
2018-06-21 19:01 ` Laurenz Albe <laurenz.albe@cybertec.at>
2018-06-21 19:05 ` Re: Unknown Process DETAIL: Failed process was running: LISTEN dirty David G. Johnston <david.g.johnston@gmail.com>
2018-06-21 19:02 ` Re: Unknown Process DETAIL: Failed process was running: LISTEN dirty David G. Johnston <david.g.johnston@gmail.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