• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Backup -> Template_Exception: Can not restart web server

HelmutF

New Pleskian
Hi!
i have big troubles making planed backups. After backup process the websites are not reachable and i got the following message:


Template_Exception: Can not restart web server: INFO: [Wed Jul 17 01:18:38 CEST 2019]: Service: apache2, Action: start Trying to start service apache2... failed Jul 17 01:18:36 vsrv018 systemd[1]: apache2.service: Failed with result 'start-limit-hit'. Jul 17 01:18:37 vsrv018 systemd[1]: apache2.service: Start request repeated too quickly. Jul 17 01:18:37 vsrv018 systemd[1]: Failed to start The Apache HTTP Server. Jul 17 01:18:37 vsrv018 systemd[1]: apache2.service: Failed with result 'start-limit-hit'. Jul 17 01:18:38 vsrv018 systemd[1]: apache2.service: Start request repeated too quickly. Jul 17 01:18:38 vsrv018 systemd[1]: Failed to start The Apache HTTP Server. Jul 17 01:18:38 vsrv018 systemd[1]: apache2.service: Failed with result 'start-limit-hit'. Jul 17 01:18:38 vsrv018 systemd[1]: apache2.service: Start request repeated too quickly. Jul 17 01:18:38 vsrv018 systemd[1]: Failed to start The Apache HTTP Server. Jul 17 01:18:38 vsrv018 systemd[1]: apache2.service: Failed with result 'start-limit-hit'. WARNING! Some problems are found during start service apache2(see log file: /var/log/plesk/rc_actions.log) Continue... /opt/psa/admin/sbin/pleskrc execution failed: Job for apache2.service failed. See "systemctl status apache2.service" and "journalctl -xe" for details. file: /opt/psa/admin/plib/Service/Driver/Web/Server/Apache.php line: 111 code: 0 Please resolve the errors in web server configuration templates and generate the file again.



Unable to generate the web server configuration file on the host <vsrv018.itserver.at> because of the following errors:

Template_Exception: Can not restart web server: INFO: [Wed Jul 17 01:18:38 CEST 2019]: Service: apache2, Action: start Trying to start service apache2... failed Jul 17 01:18:36 vsrv018 systemd[1]: apache2.service: Failed with result 'start-limit-hit'.

Jul 17 01:18:37 vsrv018 systemd[1]: apache2.service: Start request repeated too quickly.

Jul 17 01:18:37 vsrv018 systemd[1]: Failed to start The Apache HTTP Server.

Jul 17 01:18:37 vsrv018 systemd[1]: apache2.service: Failed with result 'start-limit-hit'.

Jul 17 01:18:38 vsrv018 systemd[1]: apache2.service: Start request repeated too quickly.

Jul 17 01:18:38 vsrv018 systemd[1]: Failed to start The Apache HTTP Server.

Jul 17 01:18:38 vsrv018 systemd[1]: apache2.service: Failed with result 'start-limit-hit'.

Jul 17 01:18:38 vsrv018 systemd[1]: apache2.service: Start request repeated too quickly.

Jul 17 01:18:38 vsrv018 systemd[1]: Failed to start The Apache HTTP Server.

Jul 17 01:18:38 vsrv018 systemd[1]: apache2.service: Failed with result 'start-limit-hit'.


WARNING!

Some problems are found during start service apache2(see log file: /var/log/plesk/rc_actions.log)


Continue...


/opt/psa/admin/sbin/pleskrc execution failed:

Job for apache2.service failed.

See "systemctl status apache2.service" and "journalctl -xe" for details.


file: /opt/psa/admin/plib/Service/Driver/Web/Server/Apache.php

line: 111

code: 0


Please resolve the errors in web server configuration templates and generate the file again.



After rebuilding the webconfig everthing works fine again.

Anyone has an idea?

Thanks, Helmut
 
I see that you have submitted ticket #179999 to Plesk Support. Ticket processing in progress now.
Please share the solution here when it will be resolved by Plesk Support Team.
Thanks.
 
hi!
we added

StartLimitIntervalSec=10
StartLimitBurst=10

/lib/systemd/system/apache2.service

it seems that the problem is fixed - we will monitor that for the next few days.
thanks@plesk support
Helmut
 
Back
Top