Plesk 7.1.6 & rpm errors

February 12th, 2005

RedHat Enterprise Linux 3 (RHEL3), Update 4, in certain cases breaks your Plesk 7.1.6 installation. When you attempt to login you might get the following error message:

Unable to exec utility packagemng: packagemng: Unable to open rpm db: cannot
open Packages using index db3 (-30982)

System error 2: No such file or directory

Below is my WORKAROUND for the problem, until a permanent solution can be found.

I have edited my /etc/sysconfig/rhn/up2date file so that the pkgSkipList entry reads as follows: pkgSkipList=kernel*;rpm*;.

up2date will now, no longer upgrade the rpm system.

If you have already upgraded your rpm system, you could run the following commands:

up2date --get rpm-4.2.3-10 rpm-python-4.2.3-10 rpm-build-4.2.3-10 rpm-devel-4.2.3-10 rpm-libs-4.2.3-10
cd /var/spool/up2date/
rpm -Uvh --oldpackage rpm-4.2.3-10.i386.rpm rpm-build-4.2.3-10.i386.rpm rpm-devel-4.2.3-10.i386.rpm rpm-libs-4.2.3-10.i386.rpm rpm-python-4.2.3-10.i386.rpm
rm /var/lib/rpm/__db.00*

The above commands should get you up and running with the older rpm system.

RedHat did release the updated rpm system, due to a bug, as explained by in this Errata.

Run any program as a Service

February 6th, 2005

You have installed a program on your Windows server and needs to have it starting everytime the server reboots. The obvious solution is to have the program installed as a service, but how do you do it if the program does not support it by default? Well Microsoft provides the solution.

How To Create a User-Defined Service [Open New Window]

Windows 2003 Tools

February 6th, 2005

You may want to have a little bit more control over your Windows 2003 server. Microsoft does provide you with the tools, if you know where to find them. Below is links to tools that I have found useful.

Windows Server 2003 Resource Kit Tools [ Open New Window]
Windows Server 2003 Administration Tools Pack [ Open New Window]

Mail Enable 1.8 on Plesk 7.0.3 & the default email message

February 5th, 2005

When creating a new email address (mailbox) on Plesk 7.0.3 for Windows, you will recieve a default email in the mailbox. This default email is stored in the following locations:

System default: C:\Program Files\SWsoft\Plesk\Mail Enable\Config\Postoffices
Domain default: C:\Program Files\SWsoft\Plesk\Mail Enable\Config\Postoffices\<domainname>

To alter the email is very easy. All you need to do is to create the email message as you would like it to appear to your clients and then send it to one of the defined email addresses on the system. You will be able to retrieve the email from the location below.

Email file locaton: C:\Program Files\SWsoft\Plesk\Mail Enable\Postoffices\<domainname>\MAILROOT\<mailbox>\Inbox\*.MAI

Plesk backups and psadump

February 2nd, 2005

/usr/local/psa/bin/psadump -F -z --nostop --nostop-domain --tar-ignore-failed-read --do-not-dump-logs -f - | split -b 1000m - /backup/psa-`cat /usr/local/psa/version | cut -d ' ' -f 1`-backup-`date +%Y%m%d%H`.

Basically it does a full dump and doesn’t stop services, doesn’t switch a domain off, ignores misread files (files which are being modified whilst psadump is backing them up), doesn’t backup logfiles (waste of time/space/resources) and splits the backup into 1000MB chunks, labeling them with the Plesk version and that date and hour of the backup.

Plesk and CentOS

February 2nd, 2005

Plesk will run fine on RedHat Enterprise Linux 3 (RHEL 3). CentOS is a distibution based on the RHEL 3 source RPMS and is almost totally compatible with RHEL 3. Plesk does however not recognise the OS identification string, to fix it do the following:

cp /etc/redhat-release /etc/redhat-release_original
echo "Red Hat Enterprise Linux ES release 3 (Taroon Update 4)" > /etc/redhat-release

Plesk 7.1.6 and osCommerce (Application Vault)

February 1st, 2005

After installing osCommerce on a clients website, the osCommerce installation gave a number of errors. Searching the web and forums, let to the discovery that you have to have register_globals on and safe_mode off.

Add a vhost.conf file with the following entries:

<IfModule sapi_apache2.c>
php_admin_flag register_globals On
php_admin_flag safe_mode Off

and then reconfigure the webserver:

/usr/local/psa/admin/bin/websrvmng --reconfigure-vhost --vhost-name=<domainname>

and restart the webserver:

/usr/local/psa/admin/bin/websrvmng --restart

Plesk 7.1.6 and Dr. Web Antivirus

February 1st, 2005

We purchased the Dr. Web Antivirus solution for 2 of our Plesk 7.1.6 installations. When we recieved the key files, we were instructed to upload the keys via the Pleskcontrol panel.

Every time we tried, Plesk informed us that the file did not contain a valid key file.

To resolve the problem, we finally installed the key file manually, by copying the key file to the /opt/drweb/drweb32.key and then restarting Dr. Web using service drwebd restart.

The above solved the problem on both, a RedHat 9 and RHEL 3 box.

Plesk 7.0.3 for Windows & PASV FTP

February 1st, 2005

After playing with the defautl install of Plesk 7.0.3 for Windows we reliased that it does not support PASV FTP if you enable the Firewall. After a few minutes of searching, the solution was found.

You need to tell IIS to only use a certain range of ports for PASV FTP connections. Microsof provides the following knowledge base article on how to achive this: How To Configure PassivePortRange In IIS

After you have limited IIS to only use a certain port range, you have to configure the default firewall management file Plesk\admin\bin\pfwmng.js to listen on the TCP ports for incomming connections. Yes, this does mean adding each port seperated by a comma in this file. For more information please visit the followin link: Plesk Firewall question