Upgrade to Plesk 11.5 fails: "ERROR while trying to act on PEAR packages"

[burnley]

While upgrading 11.0.9 to 11.5.30 this morning I've got this error which couldn't be fixed by /usr/local/psa/bootstrapper/pp11.5.30-bootstrapper/bootstrapper.sh repair

Trying to upgrade and repair Horde webmail configuration...
ERROR while trying to act on PEAR packages - description directory is not specified or does not exist
Check the error reason(see log file: /tmp/plesk_11.5.30_repair.log), fix and try again

***** problem report *****
ERROR while trying to act on PEAR packages - description directory is not specified or does not exist
Check the error reason(see log file: /tmp/plesk_11.5.30_repair.log), fix and try again

/tmp/plesk_11.5.30_installation.log says:

[...]
upgrade ok: channel://pear.horde.org/mnemo-4.0.3

ERROR while trying to act on PEAR packages - description directory is not specified or does not exist
Check the error reason(see log file: /tmp/plesk_11.5.30_installation.log), fix and try again

Updating 'horde' configuration status after a critical failure during upgrade stage 'files' on '20130531120650-kronolith_install_application' action

**** Product post-install for horde failed.

***** problem report *****
ERROR while trying to act on PEAR packages - description directory is not specified or does not exist
Check the error reason(see log file: /tmp/plesk_11.5.30_installation.log), fix and try again
STOP Bootstrapper 11.5.30 post-install for horde AT Wed Aug 14 08:14:27 EST 2013
To complete product installation one should run bootstrapper script:
/usr/local/psa/bootstrapper/pp11.5.30-bootstrapper/bootstrapper.sh repair

How am I supposed to fix quickly and get the upgrade process to resume? I don't like to have angry customers.

 

[burnley]

/tmp/autoinstaller3.log:

ERROR while trying to act on PEAR packages - description directory is not specified or does not exist
Check the error reason(see log file: /tmp/plesk_11.5.30_installation.log), fix and try again

***** problem report *****
ERROR while trying to act on PEAR packages - description directory is not specified or does not exist
Check the error reason(see log file: /tmp/plesk_11.5.30_installation.log), fix and try again

Bootstrapper has finished action (exec time: 0.01 sec.): parent_name='horde', sequence='post', stage='execute', sequence_order='0', operation='install', exec_cmd='/usr/local/psa/bootstrapper/pp11.5.30-bootstrapper/bootstrapper.sh post-install horde'
~empty
Bootstrapper has finished action (exec time: 0 sec.): parent_name='PLESK_11_5_30', sequence='post', stage='rollback', sequence_order='1', operation='install', exec_cmd='rm -f /tmp/pp-bootstrapper-mode.flag; rm -f /var/lock/parallels-panel-maintenance-mode.flag; touch /var/lock/parallels-panel-upgrade-failure.flag; :'
Execute command /usr/local/psa/admin/bin/send-error-report install
FileFetcher: get file (~empty)/PSA_11.5.30/plesk-11.5.30-cos5-x86_64.inf3
FileFetcher: get file (~empty)/SITEBUILDER_11.5.6/sitebuilder-11.5.6-rhall-all.inf3
FileFetcher: get file (~empty)/BILLING_11.5.30/billing-11.5.30-rhall-all.inf3
FileFetcher: get file (~empty)/MYSQL_5.5/mysql-5.5-rhel5-x86_64.inf3
FileFetcher: get file (~empty)/APACHE_2.2.24/apache-2.2.24-rh5-x86_64.inf3
FileFetcher: get file (~empty)/NGINX_1.5.0/nginx-1.5.0-cos5-x86_64.inf3
Error: An error occurred during performing of installation POST actions (see log for details).
Warning! Not all packages were installed.
Please check if your system services are operable.
Please resolve this issue and try installing the packages again.
If you cannot resolve the issue on your own, contact product technical support for assistance.

 

[burnley]

I had a look on one of the successfully upgraded servers in the rpm install scripts for psa-kronolith-4.0.4-cos5.build115130628.18 and the error is returned from this function here:

pear_register_packages()
{
local action=$1
local pkg_descr_dir=$2

[ -n "${pkg_descr_dir}" -a -d ${pkg_descr_dir} ] || die "act on PEAR packages - description directory is not specified or does not exist"

case "${action}" in
install)
action=upgrade
;;
uninstall)
;;
*)
die "act on PEAR packages - unknown command '${action}'"
;;
esac

for i in ${pkg_descr_dir}/*.xml; do
local pkg_name
if [ "${action}" = "upgrade" ]; then
#on install/upgrade we specify only full path for package xml description, for example /usr/share/psa-horde/.xml/Horde_Data.xml
pkg_name=${i}
else
#on uninstall we should use channel/app-name, for example - horde/Horde_Data
pkg_name="horde/"`basename "${i}" | cut -d '.' -f 1`
fi

if ! ${psa_pear_bin} -c "$psa_pear_conf" "${action}" --offline --nodeps --register-only "${pkg_name}" >> $product_log 2>&1; then
warn "${action} package ${i} in PEAR"
return 1
fi
done
}

Any ideas?

L.E. Just so you know, we're not using Horde at all on the affected server, so if removing Horde packages will help I'm more than glad to do it.