• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Apache not running after Dist-Upgrade to Ubuntu 16.04

jradzuweit

Basic Pleskian
Hi,
I have done a distribution upgradde from Ubuntu 14.04 to 16.04, it worked so far without major problerms except to things.

1. the file /etc/os-release still says it is a Ubuntu 14.04 instead of 16.04. The apt-get files say it has all repos switched to xenial aka Ubuntu 16.04.

2. This is a more serious problem, after the upgrade the apache does not start and the command systemctl says:

Okt 02 12:21:55 vega.radzuweit.eu apache2[3112]: * The apache2 configtest failed.
Okt 02 12:21:55 vega.radzuweit.eu apache2[3112]: Output of config test was:
Okt 02 12:21:55 vega.radzuweit.eu apache2[3112]: AH00526: Syntax error on line 240 of /etc/apache2/plesk.conf.d/ip_default/radzuweit.eu.conf:
Okt 02 12:21:55 vega.radzuweit.eu apache2[3112]: Invalid command 'DirectoryIndex', perhaps misspelled or defined by a module not included in the server configuration
Okt 02 12:21:55 vega.radzuweit.eu apache2[3112]: Action 'configtest' failed.


Any idea what to do next? The apache files where not changed and the DirectoryIndex is a common config directive in apache.
I already searched the KB and the forum here but nothing suitable found so far..

Thanx for any suggestion
Jürgen
 
Make sure that dir module is enabled in Tools&Settings-> Apache Web Server
 
... it seems that during the upgrade a link gets lost. Here a solution to get this fixed:

  1. go to /etc/apache2/mods-enabled and check if a link to ../mods-available/dir.conf and ../mods-available/dir.load exists
  2. if not create links with
>ln -s ../mods-available/dir.conf
>ln -s ../mods-available/dir.load
Apache is now running
 
Back
Top