mrjhb3
I used the script your suggested and got the following error if you can call them all errors.
the ionCube PHP Accelerator requires Zend Engine API version 20021010.
The Zend Engine API version 20050606 which is installed, is newer.
Contact Nick Lindridge at http://www.php-accelerator.co.uk for a later version of the ionCube PHP Accelerator.
What version of php are you using? The script is written to run php-4.3.10-3eo created by Ergin Özdemir (rpm -qa | grep php). I haven't tested this with any other php versions.
Installing base Horde configurations
Finishing up horde installation...
ERROR: No templates were found for /home/httpd/html/horde/kronolith/config/conf.php.
at /sbin/e-smith/expand-template line 49
You should have 2 files in /etc/e-smith/templates-custom/home/httpd/httpd/html/kronolith/config/conf.php. 10AllKronolith template-begin If you don't have these, then you will probably need to pull them down manually, then re-expand the template.
Adrianthe ionCube PHP Accelerator requires Zend Engine API version 20021010.
The Zend Engine API version 20050606 which is installed, is newer.
Contact Nick Lindridge at http://www.php-accelerator.co.uk for a later version of the ionCube PHP Accelerator.
A fatal error has occurred
Unable to load the definition of Kronolith_Driver_.
Details have been logged for the administrator.
Do a php -v to show some info about php and zend
[root@test65 conf.php]# php -v
PHP 4.3.10 (cli) (built: Mar 1 2005 08:30:27)
Copyright (c) 1997-2004 The PHP Group
Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies
with the ionCube PHP Accelerator v1.3.3r2, Copyright (c) 2001-2002, by Nick Lindridge
For the kronolith stuff, since you ran the previous script and it failed, I am thinking that all of the horde tables were not upgraded. If you are upgrading from horde 2.0 to 3.0, then change to the various horde directory scripts/upgrades and manually upgrade the tables. i.e - cd/ home/httpd/html/horde/kronolith/scripts/upgrades/
mysql horde < 1.1_to_2.0.mysql.sql
If you get any duplicate errors that just means that the DB already contains the necessary tables.
You also might run into some other issues since the first attempt failed. The symlinks that are used for horde 2.0 may not have all been removed. So, if the above works for you, I'd copy the horde/config/conf.php file, then open server-manager/e-mail and save your settings. Look at the horde/config/conf.php again and see if it has changed. If it has, then that will tell you the symlinks are still in place. Then you have 2 choices, either run the horde20-restore.sh script to revert back to 2.0. Check to make sure you can login to webmail, then run the upgrade script again.
JB
8 Replies
2781 Views