• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Fix for Zend Optimizer on Plesk 8.2.1

calderwood

Regular Pleskian
I spoke to Zend about errors on Plesk and the said there was an issue with Plesk and Zend - I have used their supplied files and the problems went away.

My system is:
Plesk 8.2.1
CentOS4.2
PHP 4.3.9

I also made theses changes after installing Optimizer:
Edit the includer for ioncube in /etc/php.d/ and add a # infront of the loader.

Then edit your php.ini file and add at the top of the Zend section:
zend_extension = /usr/lib/php4/ioncube_loader_lin_4.3.so

Test your PHP output with: php -v

HERE IS THE MESSAGE AND FILE LINKS FROM ZEND:
This is a known issue and you need to either upgrade or downgrade Optimizer.

Use one of the versions (preferred 3.2.8 or else 2.6.2) below:
http://downloads.zend.com/optimizer/3.2.8/ZendOptimizer-3.2.8-linux-glibc21-i386.tar.gz
http://downloads.zend.com/optimizer/2.6.2/ZendOptimizer-2.6.2-linux-glibc21-i386.tar.gz

Note: that these are links for Linux i386 - if you need something else, go to http://www.zend.com/downloads/

In addition, please disable ioncube extension before loading Optimizer,
if it solves a loading problem (you can see it in the stderr, console output as below, or Apache error log when starting up Apache.
 
Back
Top