• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue 18.0.47 update #5 caused server to become unreachable

dakkafex

New Pleskian
Server operating system version
AlmaLinux 8.6
Plesk version and microupdate number
18.0.47 Update #5
18.0.47 update #5 caused multiple of our servers to become unreachable.
It could also not be pinged and it was unreachable by ssh, the only thing that fixed was manually restarting the VPS instances.

I have tried digging through the logs, but I didn't see anything that looked like something that would prevent the server from starting.

Does anyone know what could have caused this? or what should I be looking for in the logs specifically.
 
Looks like a Fail2Ban ban. Do you see the server's own IP address or 127.0.0.1 in /var/log/fail2ban.log?
 
You you see your own ADSL public IP in that log?
The point is that ping and SSH are two different things. If SSH crashes, the network interface itself and the kernel will still live.
What shows up in /var/log/messages at the time when the crash occured?
 
Back
Top