Recent content by jola

This solved the problem and "systemctl --failed" now finally does not show a failed state for php-fpm. Thanks!

I have investigated this further and it seems as if the OS php-fpm service is started by Apache and nginx: This could be the reaseon why "systemctl disable php-fpm" does not help Is this normal, I would expect apache/nginx to instead start the php-fpm version that I have active in Plesk...

I'm setting up a new Plesk server and when I searched for potential problems I discovered that the php-fpm from the OS vendors gets a failed state: The Plesk php-fpm83 is running well, but the OS fails. I do not think the OS is needed and I tried to disable the OS php-fpm by running...

I'm responding to myself here. Apparently it is not good to both have the firewalld service and the Plesk Firewall active at the same time, see for example (Plesk for Linux) The Plesk Firewall. However, only one of my two servers that had problems with the firewall actually had the firewalld...

I have not done anything with firewalld as far as I can remember. However, I seem to have this service running on my servers: Should firewalld not be running at all on my servers?

Thanks, I will continue to monitor these servers closely. It is difficult to debug something when it is working again. I have tried to look in the logs in /var/log/sw-cp-server but I could not find anything that could explain this. Do you have any recommendation on which logs I should look at...

Thanks for your feedback. I have bunch of Plesk services active that does use the Firewall, like fail2ban and ModSecurity with the Atomic advanced ruleset. I do not think I have done anything outside of this to manipulate iptables. I have a few of my own Firewall rules to block out problematic...

Two of my Plesk based web-servers have recently had problems with the Plesk Firewall. For some strange reason the firewalls have stopped working. It is difficult to notice when this happens. Fortunately I have an ISP that sends me a warning email if I have an open Port 111 to the Portmapper...

Yes, that works great, and shows all database, here is the output (where I removed some database names that I do not want to be public): Plesk support is now on this. I hope they can help. First they claimed it was a network restriction from my ISP, but I think we have confirmed now that that...

I contacted Plesk support. I hope they can find the problem. Right now my case is in "AI Triage"... don't know how long it will stay there until a real person looks at it. I hope they do not try to reach me via my normal email address, since that is on one of the sites on the broken server :-/

When I look on log-lines earlier in the log. when my server was working well, it looks as if that was also running in safe mode, here is a part from a week ago:

Here comes the last 100 lines: Note that I have two versions of this virtual server, one on my real production server and one on a backup server. I am not able to get Plesk up and running on any one of them now :-(

I changed an IP number and a domain-related name part, but here is the output excluding that: Here is that: For your information. This is a virtual kvm based server running Centos 7.9 ELS with the latest Plesk Obsidian.

Here comes the content of my files in my.cnf.d: Here comes the last log-lines after a reboot:

Here comes the output, where I removed my real domain name: