From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Julie Nishimura <juliezain(at)hotmail(dot)com> |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: postgresql 9.4 restart |
Date: | 2019-05-08 19:07:50 |
Message-ID: | b5beb46e-0274-e481-6dd2-b29ae65dbb77@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/8/19 11:00 AM, Julie Nishimura wrote:
> Hello,
> Our staging 9.4 postgresql has been running couple of weeks with no
> problem, but yesterday we saw this error from one of our services that
> connects to the staging DBs:
>
> FATAL: terminating connection due to
> administrator command; nested exception is
> org.postgresql.util.PSQLException: FATAL: terminating connection due to
> administrator command”,
Distro and version?
Well it originated in Java code if that helps?
Anything in the Postgres logs just prior to 'FATAL: terminating
connection ...' that might be relevant?
Do the system logs showing anything relevant e.g. the OOM killer
stopping Postgres?
>
> Then I could see that postgresql got restarted, based on the output of
> "select pg_postmaster_start_time()"
>
> We are running postgresql on
> Linux xxx-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64
> x86_64 x86_64 GNU/Linux
>
> How I can find out what cause the restart? Any ideas are welcome. Thanks!
>
> -Julie N
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-05-08 19:42:32 | Re: Postgres Database Hacked |
Previous Message | Tom Lane | 2019-05-08 18:12:56 | Re: Query on pg_stat_activity table got stuck |