From: Tom Lane <tgl@sss.pgh.pa.us>
To: Lynn Carol Johnson <lcj34@cornell.edu>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: Postgres dying after many failed logins
Date: Mon, 08 Nov 2021 10:00:44 -0500
Message-ID: <890133.1636383644@sss.pgh.pa.us> (raw)
In-Reply-To: <58143128-71A6-4C51-9BCD-35105A385FA8@cornell.edu>
References: <58143128-71A6-4C51-9BCD-35105A385FA8@cornell.edu>
Lynn Carol Johnson <lcj34@cornell.edu> writes:
> My question: Is this expected behavior, ie that the server will
> shutdown after hours of failed attempts?
There is nothing built-in that would cause that, and frankly I doubt
that there is any direct connection. It could be that the AWS environment
imposes some resource limit (i.e., total number of child processes
spawned) that the postmaster is eventually hitting because of the
hack attempts. However, if that's true, I wouldn't really expect it to
manifest as anything as polite as a SIGTERM signal. So I think there
is something else going on. You need to look for what in your environment
could send the postmaster a SIGTERM. Can you correlate the shutdown with
anything? One thing I'm wondering is if it matches the time of shutdown
of whatever you're launching the postmaster with.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, lcj34@cornell.edu, pgsql-admin@lists.postgresql.org
Subject: Re: Postgres dying after many failed logins
In-Reply-To: <890133.1636383644@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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