• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

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