G J Piper
Regular Pleskian
I woke to see that Fail2Ban had crashed and won't restart, start, stop, or respond to anything.
I went in and "killall fail2ban-client" but that didn't help.
"plesk repair -all" apparently can't get past "Repairing web server configuration" (sits there forever)
There are no huge log files.
Disk is at only 33% capacity.
Trying to reboot the system but it is taking a long time to shut down...
(15 min already just sitting at "The system is going down for reboot NOW!")
Server is still serving websites somehow...
Forced the container to restart from Parallels Virtual Automation panel.
Any ideas?
Running Onyx 7.5.3#20, CentOS 6.9 (all components updated)
I went in and "killall fail2ban-client" but that didn't help.
"plesk repair -all" apparently can't get past "Repairing web server configuration" (sits there forever)
There are no huge log files.
Disk is at only 33% capacity.
Trying to reboot the system but it is taking a long time to shut down...
(15 min already just sitting at "The system is going down for reboot NOW!")
Server is still serving websites somehow...
Forced the container to restart from Parallels Virtual Automation panel.
Any ideas?
Running Onyx 7.5.3#20, CentOS 6.9 (all components updated)