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
Same Apache modules on different Linux distributions have different names.
Resolution
Ignore the warning if the module is from this list. It's either already installed under a different name or was removed from the newer Apache version.
| 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? |
Note: for other modules refer to this instruction if a manually installed module is missing from the destination server.
Comments
7 comments
Ivan Postnikov The list of "missing" extensions when migrating from Plesk 18.0.35/Ubuntu 16.04 to Plesk 18.0.36/Ubuntu 20.04 is even bigger: aclr, actions, alias, authn_file, authz_host, authz_user, bw, env, mime, remoteip, security2, ssl, unique_id. Interestingly, most of these extensions do exist on the target server and are activated. Seems like another bugfix that is required (which hopefully is faster than some of the others)
Hello @b_q
Thank you for reporting.
We'll test this internally.
Hello @b_q
The behavior was reproduced in a test environment.
Bug with ID PMT-4972 was created to resolve the issue you've reported.
Always surprising to see such issues with "standard" OSes where I would have expected more thorough testing...
Hi,
Is it okay to ignore the the following warning then ?
The following Apache modules are not installed on the destination server: aclr, actions, alias, authn_file, authz_host, authz_user, autoindex, dir, env, log_config, mime, mime_magic, negotiation, remoteip, security2, setenvif, ssl, unique_id.
Thank you
Hello Shaaz Sher Jung
Yes
Dear Ivan Postnikov
Hello.
I am migrating from Ubuntu 18.04 to Ubuntu 20.04 and getting the following
The following Apache modules are not installed on the destination server: aclr, actions, alias, authn_file, authz_host, authz_user, env, mime, php7.2, php7.3, php7.4, remoteip, ssl, unique_id
From the above conversation I assume that its safe to ignore?
Please sign in to leave a comment.