Replies: 5 comments
-
My docker-compose at the moment |
Beta Was this translation helpful? Give feedback.
-
The second server, also running the latest Postgres, has the same process, but in the form of I've already read about it somewhere. |
Beta Was this translation helpful? Give feedback.
-
|
I am wondering if it is the same as #1307 |
Beta Was this translation helpful? Give feedback.
-
|
I understand that the problem is partly on my end because I'm providing bad authorization data, which allows one to easily access the PostgreSQL port and download malware. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, this is definitely a compromised instance - I recommend taking it offline ASAP, restoring from a pre-compromise backup, and locking it down suitably (not exposing the ports to the internet, strong credentials, etc). |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I reinstalled my VDS machine twice because there was a problem with the "rediserver" process running inside the Postgres container (see below).
The process is completely hogging all system resources.
I installed Docker from the official documentation on the official Docker website.
I have no idea what this process is or what to do with it.
I'll include all the useful information I've dug up below.
I'm not an advanced Docker user or a DevOps administrator.
I tracked the process by its PID via systemd
When you try to kill him, he rises in two new copies.
In addition to the rediserver process, there is some suspicious sh script running, but (can be seen in the screenshot from the systemctl command)
I'm not sure if it is related to the problem.
Please help if possible, I will be very grateful to the community
Beta Was this translation helpful? Give feedback.
All reactions