From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | Jorge Daniel <elgaita(at)hotmail(dot)com>, "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:05:58 |
Message-ID: | CAKFQuwaZ=oX_2SYETdvHa39y1-V56LfaXwf2u5zxxbUwmghUCg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thursday, June 21, 2018, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2018-06-22 08:11:23 | Re: Fwd: Problem with a "complex" upsert |
Previous Message | David G. Johnston | 2018-06-21 19:02:03 | Re: Unknown Process DETAIL: Failed process was running: LISTEN dirty |