Plesk Post-Upgrade Checker

Created:

2016-11-16 13:15:57 UTC

Modified:

2017-04-24 11:18:09 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Plesk Post-Upgrade Checker

Applicable to:

  • Plesk

DESCRIPTION

Due to the changes in the business model of the Plesk 10.x release, not all previous account settings will be transferable from previous Plesk releases. Some business schemas will be lost for hosters and their clients. Attached is a script that allows you to check the environment after upgrade or migration. It checks for business logic issues, and it works for both Linux and Windows. You may launch this tool after finishing the upgrade procedure to get a report on any potential problems. Based on the report, a hoster can quickly find and fix any post-upgrade problems. We will continue working on the script to include all known issues.

Note that we also have a pre-upgrade script. Detailed information on this script can be found in this article: The tool to identify business logic issues before upgrade or migration to Plesk 10.x version .

HOW TO USE

Unix:

# php -d safe_mode=Off plesk103_postupgrade_checker.php <plesk-admin-password>

Windows:

"%plesk_bin%\\php.exe" -d safe_mode=Off plesk103_postupgrade_checker.php <plesk-admin-password>

Note: plesk103_postupgrade_checker.php is the post-upgrade script after upgrade or migration only to Plesk 10.3 version.

REPORT CONTENT CLARIFICATION

Diagnosed Situation Report Message
Virtuozzo Containers
· During Plesk operation, resource limits of Virtuozzo Container can become exhausted. Some limits set by Virtuozzo Container are exceeded. Please check the article #213398789 for more details.
DNS
· DNS server works for local port 53. Unable to connect to localhost at port 53 (DNS).
· DNS master records are resolvable to IP addresses. Unable to resolve DNS zone: <DNS ZONE NAME>.
Plesk database inconsistency
· Client or reseller can't log in to Control Panel. Client or reseller with login <login> has no corresponding record in `smb_users` table. Some clients or resellers have no corresponding records in `smb_users` table; they may have Control Panel login problems. Please check #213398789 for more details.
· Inconsistency in `smb_settings` table could lead to errors during backup or migration. There some settings missing in the `smb_settings` table of `psa` database. Please check #213366509 for more details.
HTTP
· HTTP server doesn't listen on corresponding port. Unable to connect to localhost at port <HTTP port number> (HTTP). Please check that HTTP server is running.
SMTP
· SMTP server doesn't listen on corresponding port. Unable to connect to localhost at port 25 (SMTP). Please check that SMTP server is running.
POP3
· POP3 server doesn't listen on corresponding port. Unable to connect to localhost at port 110 (POP3). Please check that POP3 server is running.
Database servers
· Database server doesn't listen on corresponding port. Supports MySQL and PostgreSQL. Unable to connect to DB server <HOST> at port <PORT>. Please check that this DB server is running and accessible.
IMAP4
· IMAP4 server doesn't listen on corresponding port. Unable to connect to localhost at port <IMAP4 port number> (IMAP4). Please check that IMAP4 server is running.
IP addresses
· The list of applications cannot be displayed if the corresponding record is absent in IP\\_addresses table. Unable to find "main" IP address in the psa database. Please check for more details.
· SSO startup script has wrong execution priority after upgrade. SSO startup script has wrong execution priority. Please check #213914785 for more details.

Have more questions? Submit a request
Please sign in to leave a comment.