| From: | Arthur Nascimento <tureba(at)gmail(dot)com> |
|---|---|
| To: | dylangregory612(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16542: High CPU Usage |
| Date: | 2020-07-15 12:52:37 |
| Message-ID: | CALVFHFb_jD21JBKYRh=NLzkRtBSRLUkJNGY0d1g=bV6bhOqZ=A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On Wed, 15 Jul 2020 at 04:16, PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> high and we don't know why it's being maxed out. You can view the HTOP
> results here: https://imgur.com/a/FxByiyX
See the process name eNdXFW? Even though it's running as the postgres
user, it's not a PostgreSQL process.
You've probably been hacked and the machine is mining bitcoins for
somebody else.
So review your security measures, make sure your backups are up to
date and secure, create a new machine from the backup and retire this
one asap.
Tureba - Arthur Nascimento
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2020-07-15 16:26:53 | Re: BUG #16419: wrong parsing BC year in to_date() function |
| Previous Message | Marco Lechner | 2020-07-15 10:34:58 | AW: BUG #16543: Package conflicts due to missing llvm-toolset-7-clang >= 4.0.1 and proj70 >= 7.0.1 |