The database utility is used to manage databases and database users in Plesk through CLI. By using this utility, you can perform the following tasks:
* creating or deleting databases
* adding and removing database users
* adding or removing database access records for database users
* editing database user credentials
* setting charset for PostgreSQL databases
Example
The following command creates database buddies on a database server accessible at the IP address and port number 192.0.2.78:3838 and prints the created Plesk database ID:
# ./database –create buddies -domain example.com -server 192.0.2.78:3838 -print-id
To create the database buddies for the domain example.com on the local MySQL server:
# ./database –create buddies -domain example.com -type mysql
Login to Horde Webmail fails in Plesk Panel Server
To solve this issue we need to verity the following.
Verify that authenticate via IMAP is possible.
# /usr/local/psa/admin/sbin/mail_auth_view
Try authorization:
If IMAP authorization failed verify that configuration of IMAP server is correct in the file.
/etc/psa-horde/imp/servers.php
Also
Verify that package courier-imap is installed and up-to-date.
# rpm -qa | grep courier-imap
Mass IP addresses change in Plesk Control Panel
Solution: Using the special utility reconfigurator.pl in Plesk
#/usr/local/psa/bin/reconfigurator.pl
Plesk reconfigurator - utility to change IP addresses used by
Plesk Server Administrator
usage:
/usr/local/psa/bin/reconfigurator.pl
If doesn’t exists - template will be created, otherwise it will be used to map IP addresses.
There is the special utility reconfigurator.pl in Plesk that allows you to change IPs in Plesk base and reconfigure domain settings with new IPs.
This utility is available in the /usr/local/psa/bin directory.
The new IP addresses must NOT exist in Server > IP Addresses list in Plesk control panel before replacement, they may be added on system level only. If IP addresses do not exist in the system, the utility will add new IPs to the system as well.
Setup Primary and Secondary (Slave) DNS server in Plesk.
Setup should allow zone transfer for the secondary DNS server in Plesk.
To allow it, secondary DNS server’s IP should be listed in NS records for all zones on Plesk server or it should be added to Access Control List (ACL).
ACL is be managed on the Server->DNS Settings->Common ACL page in Plesk CP.
In case if you wish to use non Plesk server as slave DNS, all DNS zones have to be created on the secondary DNS server in /etc/named.conf (this file location may be differ depending on OS) with ’slave’ type, for example:
zone “serverbuddies.com” {
type slave;
file “serverbuddies.com.zone”;
masters { 192.168.0.1; };
};
Restart named after that. Now slave DNS server will get zones information from Plesk (master DNS server).
Source: http://parallels.net/Plesk/
Repair and rebuild all mail configuration in plesk.
This can be done with Plesk mchk utility:
Login to the server as user root and run the mchk utility.
Example:
# /usr/local/psa/admin/sbin/mchk –with-spam
Also check for the options
# /usr/local/psa/admin/sbin/mchk –help
mchk [OPTION]
–without-spam - restore all settings except for SpamAssassin configuration
–with-spam - restore all settings
–spam-only - restore only SpamAssassin settings
This utility rebuilds in line with Plesk database Qmail control files in the /var/qmail/control, /var/qmail/users directories and mail users’ settings. Also, it sets proper ownership/permissions for all mailboxes (/var/qmail/mailnames/*).
