LinuxHostingSupport

While accessing the Plesk control panel, you may encounter an error message as follows:

ERROR: PleskFatalException StatInfo-> getProductVersion failed

OR

ERROR: PleskFatalException StatInfo-> getProductVersion failed: 

file_get_contents () failed: mktime() 

[<a href='function.mktime'>function.mktime</a>]

The “Plesk getProductVersion failed ” message states that either the Plesk version file /usr/local/psa/version is empty AND/OR the plesk version in the ‘psa.misc’ table is incorrect. This is mostly caused due to a failed Plesk upgrade OR by removing/installing some Plesk modules.

To fix the issue do the following:

1. First, check the Plesk version installed on the server

# rpm -qi psa

note down the ‘version’ and ‘release’ values (these values will be different on your server).

Version : 9.5.3 Release : cos5.build95301122.20

now, check the OS installed on the server (for example, on CentOS)

# cat /etc/redhat-release 

CentOS release 5.5 (Final)

Using the above Plesk and OS info, insert a line as follows (your values will differ) in the /usr/local/psa/version file.

9.5.3 CentOS 5 95301122.20

Save the file and restart the psa serivce.

2. If the above fix doesn’t work, do the following

Check the current value of  Plesk in the psa.misc table.

mysql> select * from psa.misc where param='version';

If the value is not 0953 (example from my server), run the mysql update query to set the proper value. You should use the value that is returned by the ‘rpm -qi psa’  command on your server.

mysql> update psa.misc set val="0953" where param="version";

Exit and restart mysql. That is it.

You may see an “Unable to exec utility packagemng” error message while accessing the Plesk control panel. The error generally occurs after performing a Plesk control panel upgrade and the complete error message looks like follows:

Components::componentUpdate() failed: Unable to exec utility 

packagemng: file does not exist or is not executable:

/usr/local/psa/admin/bin/packagemng 0: auth.php3:551

This is due to the “packagemng” file is symlinked to the “wrapper” file and the ‘wrapper’ file don’t have the executable permissions for it’s group user “psaadm”.

The permissions of ‘packagemng’ file are (symlink):

# ls -la /usr/local/psa/admin/bin/packagemng

lrwxrwxrwx 1 psaadm psaadm Jan 01 packagemng  -> ../sbin/wrapper

In my case the permissions of wrapper file were ( there was no executable permission)

# ls -la /usr/local/psa/admin/sbin/wrapper 

---s------ 1 root psaadm Jan 01 /usr/local/psa/admin/sbin/wrapper

The correct permissions of the wrapper files are ( —s–x— ) which can be set using the following command:

# chmod 4110 /usr/local/psa/admin/sbin/wrapper

so it should look like

---s--x--- 1 root psaadm 19760 Jan 01 05:20 wrapper

Once done, you should be able to access the Plesk control panel.

If you perform a Plesk upgrade, you may notice you are unable to unsuspend a domain from the Plesk control panel resulting in the following message:

Warning: The domain is still suspended for the following reason: 

Domain is temporarily suspended for backing up or restoring.

Looking at the message, it appears that a backup process is running for the domain on the Plesk server but it is not, thus making things look complicated. In such a case, unsuspend the domain on the Plesk server from shell.

SSH to the server as root and execute:

# /usr/local/psa/bin/domain -u domain.tld -status enabled

This will un-suspend/enable the domain.

Sometimes a “Segmentation fault” message appears while unsuspending the domain via SSH. It indicates that the Plesk upgrade didn’t go through successfully and there is a problem with plesk binaries. You now need to install the Plesk base packages again from Plesk –> Updates, section.

Once the update is performed, reconfigure the domain:

# /usr/local/psa/admin/sbin/websrvmng --reconfigure-vhost \
 --vhost-name=domain.tld

and enable it

# /usr/local/psa/bin/domain -u domain.tld -status enabled

This will un-suspend the domain and will leave you with a message “Object successfully enabled”.

Qmail allows a maximum of 10 local and 20 remote email deliveries/processes simultaneously by default. The concurrencylocal and concurrencyremote files are the ones which handles the concurrent local and remote email deliveries respectively.

To increase the number of email deliveres/processes, you have to increase the values in the concurrencylocal and concurrencyremote files and restart the Qmail service.

The concurrencylocal and concurrencyremote files resides in the /var/qmail/control directory. If the files are not present, you have to create them

# vi /var/qmail/control/concurrencylocal

# vi /var/qmail/control/concurrencyremote

set the required value and restart the qmail service

# service qmail restart

Once done, you can manage the Qmail mail queue using Qmhandle.

Plesk supports Qmail and Postfix mail servers, however, only one MTA (Message Transfer Agents) can be installed and used at a time. To check the current MTA in use, look at

Plesk -> Settings -> Services Management

OR you can execute the following command from SSH

# /usr/local/psa/admin/bin/mailmng --features | grep SMTP_Server 

$features['SMTP_Server'] = "QMail"; 

$features['SMTP_Server_package'] = "psa-qmail";

The above output shows that Qmail is currently your Mail server. Plesk offers an ‘autoinstaller’ script to install/upgrade various components, and is used to switch from Qmail to Postfix OR vice-versa.

Stop the SMTP service before you switch between the Mail servers, to avoid accepting of new emails and to deliver the emails that are in the mail queue.

Stop the SMTP service:

# /usr/local/psa/admin/sbin/mailmng --stop-smtpd

Switch MTA from Qmail to Postfix:

# /usr/local/psa/admin/sbin/autoinstaller --select-release-current \ 

--install-component postfix

OR switch MTA from PostFix to Qmail:

# /usr/local/psa/admin/sbin/autoinstaller --select-release-current \ 

--install-component qmail

That’s it.

Note: The change of mail server won’t change the mail format and the directory location where the messages are stored. However, the emails in the mail queue will be removed since the MTA is reconfigured.