• 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.

Error with Apache? All of my sites and Panel are down

Daniel_Maris

New Pleskian
I think my server underwent a DDoS attack a couple weekends ago. Anywho, I get over 300 CRON emails with this error in it, they were supposed to be sent over the several weeks, I Hard-rebooted my server and it then finally sent all those emails at once. Running Debian 7.8. The email said this:
Email Heading:
Cron <root@raptor2720> [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime)

Email Body: find: invalid predicate `-ignore_readdir_race'


I try command line:

ROOT: sudo /etc/init.d/psa start

[FAILing psa... [....] Starting Plesk engine pool manager: sw-engine-fpm failed!

done

Starting xinetd service... done

Starting sw-cp-server service... failed

Starting mysql service... done

Starting bind9 service... done

Starting postgresql service... not installed

Starting spamassassin service... not installed

Plesk: Starting Mail Server... already started

Service /etc/init.d/apache2 failed to start

Service /etc/init.d/apache2 failed to start

Service /etc/init.d/apache2 failed to start

Service /etc/init.d/apache2 failed to start

[FAILing psa... [....] Starting Plesk engine pool manager: sw-engine-fpm failed!

done

Starting drwebd service... done

I have no idea what I should do to fix this issue but help would be great, all my sites were knocked out.

Thanks


 
Any results of troubleshooting? Do you have any related error messages in /var/log/sw-cp-server/error_log and /var/log/sw-cp-server/sw-engine.log at least? Is it VPS? Have you tried bootstrapper repair procedure?
 
Back
Top