Articles in this section

See more

Pre-migration checks show warning: The following Apache modules are not installed

Avatar
Julian Bonpland Mignaquy
Updated
Follow
Plesk for Linux kb: technical ext: migrator ABT: Group A

Applicable to:

  • Plesk for Linux

Symptoms

After starting a migration in Tools & Settings > Migration & Transfer Manager the pre-migration check shows the following warnings:

Examples:

PLESK_WARN: The following Apache modules are not installed on the destination server: <module_name>

PLESK_WARN: Apache modules are not installed on the destination server: jk, bw. Please install and enable these modules to prevent possible problems.

PLESK_WARN: Failed to synchronize subscription with plan
Migration tools tried to perform operation in 3 attempts:
Plesk error [1023]: bandwidth - Description: phosting__mod_bw_not_installed. Requested: 2097152. Allowed: -1

Cause

There are 3 general reasons why these messages are shown:

  1. Apache version differs on source and destination. Because of that module name may differ and not detected properly
  2. Also depending on OS module names may differ as well, for example on Debian 7 and Centos 6.
  3. There was some additional module installed on the source server which is not installed by default on destination.

Resolution

If additional modules were manually installed on the source server, follow these steps to add them to the target server

  1. Connect to the destination server via SSH.

  2. Install the missing module as follows depending on the OS installed:

    Note: change the "<module_name>" in the command below to the correct one.

    • For RPM-based systems:

      # yum install <module_name>

    • For Debian-based systems:

      # apt install <module_name>

    Note: Sometimes module name in the error message does not coincide with the corresponding package.
    In order to find the correct module name use the package search tool:

    • For RPM-based systems:

      # yum search <module_name> | grep -i apache

    • For Debian-based systems:

      # apt search <module_name> | grep -i apache

      Note: change the "<module_name>" in the command below to the correct one.

List of known modules for which the warning can be ignored:
Module name Explanation
authnz_ldap was used in Apache 2.2, removed in Apache 2.4
ldap was used in Apache 2.2, removed in Apache 2.4
authn_default was used in Apache 2.2, removed in Apache 2.4
authz_default was used in Apache 2.2, removed in Apache 2.4
disk_cache was used in Apache 2.2, renamed to cache_disk in Apache 2.4
cgi was used in Apache 2.2, replaced by cgid in Apache 2.4
negotiation used on deb like systems but not on RedHat based
setenvif used on deb like systems but not on RedHat based
dir used on deb like systems but not on RedHat based
autoindex used on deb like systems but not on RedHat based
perl not installed by default starting from Plesk 12.5. You will see such a message if the destination is higher than 12.5 and a source lower than 12.5
python not installed by default starting from Plesk 12.5. You will see such a message if the destination is higher than 12.5 and a source lower than 12.5
php5 not installed by default starting from Plesk 12.5. You will see such a message if the destination is higher than 12.5 and a source lower than 12.5
mod_bw if needed it can be installed in Tools & Settings > Updates and Upgrades > Add/Remove Components. Not available since Plesk 18.0.32 or in CentOS 8/RHEL 8 
mod_jk not supported by default starting from Plesk Onyx 17.8. After migrating to Plesk Onyx 17.8 or Obsidian, Apache Tomcat will be unavailable for installing and configuring via Plesk interface. Does Plesk Onyx/Obsidian support Apache Tomcat?

Comments

0 comments

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles