httpsd: symbol lookup error: /usr/local/Zend/lib/ZendExtensi

[WaDavid]

[solved] httpsd: symbol lookup error: /usr/local/Zend/lib/ZendExtensi

Interesting error. Found today for the second time that a specific server running Plesk 8.6 on Centos 4 to be down. Now this server pretty much ran 100% for more than 6 months on Plesk 8.2.1 and it took me a long time to consider an upgrade because it was really stable.

First thing I tried was to restart it the normal way.

[root@control3 ~]# /etc/init.d/psa restart
PSA is down, performing full restart.
Starting xinetd service... done
Starting named service... done
Starting mysqld service... done
Starting qmail service... done
Starting courier-imap service... done
Starting postgresql service... done
Starting psa-spamassassin service... done
Starting Plesk... failed
Starting drwebd service... not installed
[root@control3 ~]#

No luck no matter what I tried so I decided to do a test.

[root@control3 ~]# /usr/local/psa/admin/bin/httpsd -t
/usr/local/psa/admin/bin/httpsd: symbol lookup error: /usr/local/Zend/lib/ZendExtensionManager.so: undefined symbol: zend_get_configuration_directive
[root@control3 ~]#

Now this is quite unexpected. I am not 100% sure why the plesk apache or is it lighthttpd server need Zend, as far as I remember the plesk control panel php files are encrypted with something else that I can't remember right now but definitly not zend, though I guess things could have changed.

How can I go about fixing this?

I did some more testing, and this is the really wierd pard:

[root@control3 ~]# /usr/local/psa/admin/bin/httpsd
/usr/local/psa/admin/bin/httpsd: symbol lookup error: /usr/local/Zend/lib/ZendExtensionManager.so: undefined symbol: zend_get_configuration_directive
[root@control3 ~]# cd /usr/local/psa/admin/bin/
[root@control3 bin]# ./httpsd
Processing config directory: /usr/local/psa/admin/conf/httpsd.*.include
Processing config file: /usr/local/psa/admin/conf/httpsd.rw.include
[root@control3 bin]#

Like what? It is back up now but somewhere something is not set the way it should be.

 

[WaDavid]

Alright, noticed there was a new small update to 8.6, updated again and this problem seems to be resolved now.