Vesta Control Panel - Forum

Module ruid2 already enabled
Enabling module headers.
To activate the new configuration, you need to run:
service apache2 restart
Job for apache2.service failed. See 'systemctl status apache2.service' and 'jour nalctl -xn' for details.
Error: apache2 start failed

root@g3cms03:~# systemctl status apache2.service
● apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.d/apache2)
Drop-In: /lib/systemd/system/apache2.service.d
└─forking.conf
Active: failed (Result: exit-code) since Fri 2017-05-05 11:41:46 EDT; 10min ago
Process: 21760 ExecStart=/etc/init.d/apache2 start (code=exited, status=1/FAILURE)

May 05 11:40:45 g3cms03 systemd[1]: Starting LSB: Apache2 web server...
May 05 11:41:46 g3cms03 apache2[21760]: Starting web server: apache2 failed!
May 05 11:41:46 g3cms03 apache2[21760]: The apache2 instance did not start within 20 s...g).
May 05 11:41:46 g3cms03 systemd[1]: apache2.service: control process exited, code=exit...s=1
May 05 11:41:46 g3cms03 systemd[1]: Failed to start LSB: Apache2 web server.
May 05 11:41:46 g3cms03 systemd[1]: Unit apache2.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

mehargags wrote:some VPS/Server specs would help.
Can be a template problem your provider using to deploy the server.

Debian 8.0 64-bit Minimal
40GB Space
1GB Ram
256MB VSwap