LinuxHostingSupport

If the mail handlers in Plesk are corrupt, you will be unable to remove the email account OR a domain from the Plesk control panel and will result in the following error

—————————————–

mailmng failed: Some errors occured. See log for details
0: class.MailManager.php:242
MailManager::execWithException(string ‘smart_exec’, string ‘mailmng’, array, array, string ‘lst’)
1: class.MailManager.php:274
MailManager->callMailManager(string ‘remove-mailname’, array)
2: class.MailManager.php:354
MailManager->removeMailname(string ‘domain.tld’, string ’emailid’)

—————————————–

The one of the following 3 methods can be used to resolve the issue:

1) To remove and re-create the mail handlers using the ‘mchk’ script and then deleting the email account from Plesk. For detailed steps, click here

2) To remove the email account via SSH.

# /usr/local/psa/bin/mail --remove email@domain.tld

3) If the above 2 methods doesn’t work, remove the email account from the Plesk database manually (backup the ‘psa’ database first). 

Let’s use the email ID as “xyz@abc.com” as an example here (of-course, it should be replaced with the actual values in your queries).

Connect to the psa database from SSH:

# mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa

Retrieve the domain ID of abc.com

mysql> select id from domains where name="abc.com";

Now, first we will delete the password of the email account from the ‘accounts’ table by executing the below query:

mysql> delete from accounts where id in (select mail.id from \

mail INNER JOIN domains ON mail.dom_id=domains.id where \

domains.name="abc.com" AND mail.mail_name="xyz");

Now, delete the email name ‘xyz’ from the ‘mail’ table (replace ‘ID’ with the id retrieved from the first query)

mysql> delete from mail where dom_id='ID' AND mail_name='xyz';

Once done, restart the Mysql service and you will be able to remove the email account from the Plesk control panel.

Following is the list of path to different log files on a Plesk server.

Plesk Installation Logs:

/tmp/autoinstaller3.log

Plesk Upgrade Logs including other applications:

/tmp/psa-<app-name>...log

Plesk Access and Error Logs:

/usr/local/psa/admin/logs/httpsd_access_log 

/var/log/sw-cp-server/error_log

Plesk Migration Logs:

/usr/local/psa/PMM/logs/migration.log

WatchDog Logs on Plesk:

/usr/local/psa/var/modules/watchdog/log/monit.log

Apache Web Server Logs on Plesk:

/var/log/httpd/access_log 

/var/log/httpd/error_log

Apache Suexec Logs on Plesk:

/var/log/httpd/suexec_log

Access and Error Logs of a Website (account):

/var/www/vhosts/domain.tld/statistics/logs/access_log 

/var/www/vhosts/domain.tld/statistics/logs/error_log

Mysql Logs on Plesk:

/var/lib/mysql/server.hostname.err  (unless defined in /etc/my.cnf)

Named (Bind) Logs on Plesk:

/var/log/messages

Mail (Qmail and Postfix) Logs on Plesk:

/usr/local/psa/var/log/maillog

Ftp Logs on Plesk:

/var/log/messages

Server Logs on Plesk:

/var/log/messages

Horde Logs:

/var/log/psa-horde/psa-horde.log

Cronjob Logs:

/var/log/cron

SSH Logs:

/var/log/secure

Mailman Logs:

/var/log/mailman/

Tomcat Logs:

/var/log/tomcat5/catalina.out

Sometimes an error message “Unable to create PHostingManager object:Unable to set current ip address” appears in Plesk while managing a domain from Plesk -> Domains section. The complete error is as follows:

"Unable to create PHostingManager object:
Unable to set current ip address:
IP address is missing"

This problem appears when an IP assigned to a domain is not assigned to the ‘Owner’ of the domain. To fix the issue, login to Plesk and assign the IP to the owner:

Plesk --> 'Settings' --> "IP Addresses" -->  click the number 
 under the 'Users' coloumn in front of the IP address -->
 Assign the IP to the owner.

This will update the ‘psa’ database and allow the user to manage the domain from Plesk.

You see a “Unable to install the psa-backup-manager” error while installing Plesk control panel on a Linux server and it is because of the incomplete db4 packages needed for embedded database support for various applications. The complete error message looks like:

Determining the packages that need to be installed. ERROR: Unable to
install the "psa-backup-manager-9.x.x-cos5.buildxxxxxxx.00.i586"
package. Not all packages were installed.

Solution:

Check if the required db4 packages are installed by executing:

# rpm -qa | grep db4

It will list the db4 packages. If the db4-devel and db4-utils are missing from the above output, install the packages using yum

# yum install db4-utils
# yum install db4-devel

That’s it. You can start the Plesk installation once again and it will install the psa-backup-manager successfully.

Plesk uses a ‘psa’ database to store all the data and values. This data can be easily retrieved at any point of time using the Mysql queries.

How to access the Plesk ‘psa’ database in Linux?
There are 2 ways, one via SSH (Linux command line) and the other from the Plesk control panel.

Method 1)

SSH to your server as root and execute the following command. The /etc/psa/.psa.shadow file contains the Plesk admin password.

# mysql -uadmin -p`cat /etc/psa/.psa.shadow`

You will be connected to the Mysql server. To use psa database, execute

mysql> use psa;

To view all the psa database tables:

mysql> show tables;

Method 2)

Login to the Plesk control panel as user admin

Goto Settings -> Database Hosting Preferences -> click OK -> 

Local MySQL server -> Databases tab -> click Webadmin.

Once you click “Webadmin”, phpMyAdmin will open in a new window from where you can access all the databases including the ‘psa’ database. Make sure pop-ups are enabled in your browser.