Archive for the ‘Plesk’ category

« Older Entries
Newer Entries »

How to migrate Horde (Plesk) address, calendar and perferences.

June 18th, 2009

Sadly, migrating settings that are saved in Horde is not supported by Plesk 8 as of 8.6, and likely not in Plesk 9. However there is a way to migrate the data, however it will need to be done manually. To do so, you will need to goto the server where the information that you need to migrate is. Once there, you need to login via shell / SSH. Once logged in, we need to backup 3 things;

kronolith_events

kronolith_storage

Horde Mysql database

To do this, we need to backup the tables as such;

~# mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` horde --tables kronolith_events > kronolith_events.dump
~# mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` horde --tables kronolith_storage > kronolith_storage.dump

Then we need to backup the Horde database;

~# mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` horde > horde.old.dump
Now that we have the files, you will need to move them to the new server, either by ftp, wget, scp or however you move your files between your servers.
Now on the new server, make sure you make a backup of these files incase this fails;
~# mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` horde > horde.new.dump
~# mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` horde --tables kronolith_events > kronolith_events.dump
~# mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` horde --tables kronolith_storage > kronolith_storage.dump
Put these files in a different directory to make sure you do not get confused.
Now we can start to restore the old data by doing the following;
~# mysql -uadmin -p`cat /etc/psa/.psa.shadow` horde < kronolith_events.dump
~# mysql -uadmin -p`cat /etc/psa/.psa.shadow` horde < kronolith_storage.dump
Before you restore the Horde database, you will want to remove the existing one first and then recreate it;
~# mysql -uadmin -p`cat /etc/psa/.psa.shadow` -e"drop database horde"
~# mysql -uadmin -p`cat /etc/psa/.psa.shadow` -e"create database horde"
Then restore the original Horde database;
~# mysql -uadmin -p`cat /etc/psa/.psa.shadow` horde < horde.old.dump
Once you do this and restart Horde/Exim, you will have all of your contacts and settings migrated and ready to use on the new server.
*MAKE SURE YOU MAKE BACKUPS BEFORE YOU DO THIS*

No comments »

Posted in Plesk, Windows 2003, horde

Tags:

Cannot login to Horde Webmail (Plesk): Login Failed

March 18th, 2009

PROBLEM:
While Login into Webmail it returns the error: “Login failed”

SOLUTION:
Make sure that it is possible to connect to localhost:143 from the command line using telnet. If you get the error as below:
-=-=-
# telnet localhost 143
localhost/143: Name or service not known
-=-=-

then check /etc/hosts file. It must have permissions -rw-r–r– and contain the record for localhost in the following format:
-=-=-
127.0.0.1       localhost localhost.localdomain
-=-=-
Above is from From Parallels Knowledgebase

If /var/log/psa-horde/psa-horde.log shows something like:

FAILED LOGIN xx.xx.xx.xx to localhost:143[imap/notls] as me@mydomain.co.uk
FAILED LOGIN xx.xx.xx.xx to localhost:143[imap/notls] as me@mydomain.co.uk

I have searched regarding this but unable to find any fix so, I just re-installed the IMAP Service on the server. Following are the steps using which I have re-installed IMAP Server:
-=-=-
1) You can find the RPMS used by Plesk in /root/psa/PSA_version directory OR you can download the Tar (Not Autoinstaller) containing RPMS from Parallels website http://www.parallels.com/en/download/ (need registration it’s free)

2) go to the RPM directory which contains courier Imap RPM’s
#cd [path to the PSA RPM Directory]/dist-rpm-CentOS-4.2-i386/base/

3) Re-install courier-imap-3.0.8-cos4.build81070322.16.i586.rpm and psa-courier-imap-add-8.1.1-cos4.build81070322.16.i586.rpm which will automatically restart the services too
-=-=-
[root@vps base]# pwd
/root/plesk/dist-rpm-CentOS-4.2-i386/base
[root@vps base]# rpm -Uvh courier-imap-3.0.8-cos4.build81070322.16.i586.rpm psa-courier-imap-add-8.1.1-cos4.build81070322.16.i586.rpm –force
Preparing… ########################################### [100%]
Reloading configuration: [ OK ]
1:courier-imap ########################################### [ 50%]
Stopping Courier-IMAP server:
Stopping imap [ OK ]
Stopping imap-ssl [ OK ]
Stopping pop3 [ OK ]
Stopping pop3-ssl [ OK ]

Starting Courier-IMAP server:
Starting imapd [ OK ]
Starting imap-ssl [ OK ]
Starting pop3 [ OK ]
Starting pop3-ssl [ OK ]

2:psa-courier-imap-add ########################################### [100%]
Stopping Courier-IMAP server:
Stopping imap [ OK ]
Stopping imap-ssl [ OK ]
Stopping pop3 [ OK ]
Stopping pop3-ssl [ OK ]

Starting Courier-IMAP server:
Starting imapd [ OK ]
Starting imap-ssl [ OK ]
Starting pop3 [ OK ]
Starting pop3-ssl [ OK ]

[root@vps base]# netstat -nap | grep :143
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 1657/couriertcpd
[root@vps base]# telnet localhost 143
Trying 127.0.0.1…
Connected to localhost.
Escape character is ‘^]’.
-=-=-

No comments »

Posted in Plesk

Tags:

Managing log rotation in Plesk

March 18th, 2009

Plesk allows managing log files and log rotation settings from the control panel. To access these functions, click the Log Manager icon on the Domain Administration page (depending on the version of Plesk, you may need to click on the actual domain name instead of going to the domain administrator). The Log Manager page will open.

- Define the number of log file’s lines to be displayed at once. To do that, type in the number of lines in the Lines of log file to be displayed input field prior to selecting a log file for viewing.
- View a log file. To this effect, click on a log file’s name in the list. The log file contents will be displayed in a separate Log File Viewer window.
- Save a log file on your local machine. To do that, click on the appropriate icon. After that you will need to specify the location on your local machine and the file name for the downloaded log file to be saved, and then click Save.
- Delete log files. To this effect, select the corresponding checkboxes, and click Remove Selected.

To configure the log rotation preferences, follow these steps:

1. Click the Log Rotation icon on the Log Files Management page. The Log Rotation Preferences page will open.
2. Click the Enable or Disable icon respectively to enable/disable log rotation.
3. Select the log rotation condition:

- log file size – enter the size in kilobytes in the appropriate field
- time – select from the drop-down list. It can be set to Daily, Weekly, and Monthly.

4. Specify the maximum number of log files in the appropriate input field, if desired. The maximum number is the number of processed files to be kept for each log file.
5. Select the Compress log files checkbox to enable compression.
6. If desired, in the Send processed log files to e-mail input field, enter the e-mail address, for the processed log files to be delivered to.
7. Click OK to submit changes.

No comments »

Posted in Plesk

Tags:

ERROR: PleskFatalException : Unable to remove hosting: SiteAppManager: Provided Client object is invalid or Internal Plesk error occurred: Unable to remove hosting: SiteAppManager: MySQL query failed: Unknown column ‘app_release’ in ‘field list’

March 4th, 2009

ERROR: PleskFatalException : Unable to remove hosting: SiteAppManager: Provided Client object is invalid or Internal Plesk error occurred: Unable to remove hosting: SiteAppManager: MySQL query failed: Unknown column ‘app_release’ in ‘field list’

ERROR: PleskFatalException
Unable to remove hosting: SiteAppManager: Provided Client object is invalid or ERROR: Internal Plesk error occurred: Unable to remove hosting: SiteAppManager: MySQL query failed: Unknown column ‘app_release’ in ‘field list’

Solution: you have to login to psa’s database via MysqlQuery Browser or any other client you want and then the following steps

1) find the domain id, just go to the client of the domain, and in the domain select list,
put your mouse over the domain name, in the status bar of the browser you will see something like:

https://yourserver.tld:8443/domains/dom_ctrl.php3?dom_id=865&previous_page=domains

the domain id there is “dom_id=865″.

2)open the psa database in mysql
3)run: SELECT * FROM SiteApps where dom_id=’865′;
you will see the application in 1 line, then delete it
4)run: DELETE FROM SiteApps where dom_id=’865′;

try again to delete the domain from Plesk.

after that if you receive the error:

ERROR: PleskFatalException
Cannot delete database which is in use by a site application

do the above:
2)open the psa database in mysql
2)run: SELECT * FROM data_bases where dom_id=’865′;
you will see the lines with the databases the domain has,
3)run: DELETE FROM FROM data_bases where dom_id=’865′;

After the 3rd step you will be able to delete the domain from Plesk, just
dont forget to manualy delete the databases (given from step 2)

No comments »

Posted in Plesk

Tags:

Unable to add a recipient when trying to send an email with webmail.

February 4th, 2009

If I compose and send a message with webmail the following error appears:

There was an error sending your message: unable to add recipient
[name@domain.com]: Invalid response code received from server.

Please add the following record to Server > Mail > White list in Plesk CP:

127.0.0.1 /8

If you are not able to add that record, you can also try 127.0.0.1/255.255.0.0 or 127.0.0.1/255.0.0.0

If the record is already there, you may want to remove it and then add it again. This normall is the case if you have reinstalled any of the courier/imap components on the server (This would affect the whitelist). Ultimately, if you nothing else works, you can also add the actual ip/ip’s of the server as well.

No comments »

Posted in Plesk

Tags: