From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | 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:01:46 |
Message-ID: | 1529607706.3218.2.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2018-06-21 19:02:03 | Re: Unknown Process DETAIL: Failed process was running: LISTEN dirty |
Previous Message | Jorge Daniel | 2018-06-21 18:32:02 | Unknown Process DETAIL: Failed process was running: LISTEN dirty |