dasaweb
New Pleskian
Hi,
I'm using Plesk Onyx (Version 17.0.17 Update #15) on an Ubuntu 14.04.5 LTS. If I change anything in the Plesk setting that needs a restart of the Apache webserver the Apache crashes. Or to be more precisely: I see in the Apache error log that the webserver can be shuted down, but it is not restarted. I can start the webserver by typing "/etc/init.d/apache2 start" as root, no problem. And in that moment the changes in the Plesk backend are successfully finished.
Looking at https://mydomain:8443/admin/services/list I see that the service "Apache (Webserver)" is never running, although he is running (all the websites are running, "/etc/init.d/apache2 status" says "running"). If I try to click to the "Start service" button nothing happens, no matter the webservice is started in the shell or not.
Any ideas? This sounds like a not so important issue, but the consequences are for example that everyone changings someting via Plesk need to restart the server as root, which is not possible. Not to mention crashing cronjobs and so on...
Thank's for your help!
Daniel
I'm using Plesk Onyx (Version 17.0.17 Update #15) on an Ubuntu 14.04.5 LTS. If I change anything in the Plesk setting that needs a restart of the Apache webserver the Apache crashes. Or to be more precisely: I see in the Apache error log that the webserver can be shuted down, but it is not restarted. I can start the webserver by typing "/etc/init.d/apache2 start" as root, no problem. And in that moment the changes in the Plesk backend are successfully finished.
Looking at https://mydomain:8443/admin/services/list I see that the service "Apache (Webserver)" is never running, although he is running (all the websites are running, "/etc/init.d/apache2 status" says "running"). If I try to click to the "Start service" button nothing happens, no matter the webservice is started in the shell or not.
Any ideas? This sounds like a not so important issue, but the consequences are for example that everyone changings someting via Plesk need to restart the server as root, which is not possible. Not to mention crashing cronjobs and so on...
Thank's for your help!
Daniel