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

Services Management not working after 7.5 Upgrade

M

mac0310

Guest
Just completed an upgrade from 7.1.6 to 7.5.0 and the services under Services Management don't work. I get the following error when trying to restart Apache -

Unable to make action: Unable to manage service by websrvmng: websrvmng: Service httpd failed to restart: Operation not permitted
0: /usr/local/psa/admin/htdocs/server/restart_services.php:2 psaerror(string "Unable to make action: Unable to manage service by websrvmng: websrvmng: Service httpd failed to restart: Operation not permitted")

When the server boots it does not start Apache, I had to ssh in to start it manually.

Are there problems with the 7.5.0 upgrade?
 
What OS are you using? Things are working fine (in terms of service management) for me under RH 7.3.
 
Version psa v7.5.0_build75041208.19 os_RedHat el3
OS Linux 2.4.21-4.0.1.ELsmp

Same error. Did some troubleshooting, and found that it was httpd looking for a conf file that was non-existant. FOund this out by issuing the "/sbin/service httpd restart" command in SSH.

recreated the conf file (blank), and wham, httpd restarted just fine through both SSH and Plesk.
 
Reply

Version psa v7.5.0_build75041208.20 os_FedoraCore 2
OS Linux 2.6.9-1.6_FC2

I had the same result after I manually restarted httpd. Things seem to be working okay now.
 
Back
Top