From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Jorge Daniel <elgaita(at)hotmail(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Unknown Process DETAIL: Failed process was running: LISTEN dirty |
Date: | 2018-06-21 19:02:03 |
Message-ID: | CAKFQuwZ_RhqukuV+YrhXTBhgo_6nE4qwM=FJxgY2VZw5-bDDdw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thursday, June 21, 2018, Jorge Daniel <elgaita(at)hotmail(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2018-06-21 19:05:58 | Re: Unknown Process DETAIL: Failed process was running: LISTEN dirty |
Previous Message | Laurenz Albe | 2018-06-21 19:01:46 | Re: Unknown Process DETAIL: Failed process was running: LISTEN dirty |