• 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!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

plesk_apache

D

Dangerous

Guest
Every day since upgrading to 7.5.4 version of Plesk, I get the same series of emails in by inbox. Presumably from Watchdog.

[Sun, 28 Aug 2005 04:08:24 -0700] plesk_apache on [my server name]: Connection failed.
'plesk_apache' failed protocol test [HTTP] at INET[localhost:8443}

[Sun, 28 Aug 2005 04:13:30 -0700] plesk_apache on [my server name]: Execution failed.
'plesk_apache' failed to start

[Sun, 28 Aug 2005 04:33:31 -0700] plesk_apache on [my server name]: Does not exist.
'plesk_apache' process is not running

[Sun, 28 Aug 2005 04:33:34 -0700] plesk_apache on [my server name]: Execution succeeded.
'plesk_apache' started

[Sun, 28 Aug 2005 04:58:34 -0700] plesk_apache on [my server name]: Exists.
'plesk_apache' process is running with pid 28651

[Sun, 28 Aug 2005 04:58:35 -0700] plesk_apache on [my server name]: Connection passed.
'plesk_apache' connection passed

Can anyone offer any insight? What would make plesk_apache fail?

My OS is Linux ES3.
 
The Watchdog module is buggy. This has been covered in a number of other threads. It is recommended to either disable or uninstall the Watchdog module until Plesk gets it fixed.
 
Back
Top