PHP not working on some virtuals

Submitted by securewebs on Mon, 05/23/2016 - 17:00 Pro Licensee

This is a weird one. One of our clients has a CentOS 6.6 server and he reports the last two virtual accounts he added the PHP is not working. In his case he just has a GPL license where as on our own servers we use strictly the pro licenses. Be happy to pay for support if someone has any ideas what the problem could be. We took a look but can't figure out what is the problem. We even replaced the php.ini files from a working virtual to the not working and restarted Apache and that is not the issue. Logfiles so far are not helping, at least the Apache log files. Trying a webpage just gets you a 500 error, but html works fine. Trying that info php test page, will not work in these last two virtuals he created. Any ideas on how to debug the issue would be appreciated.

Status: 
Active

Comments

Submitted by andreychek on Mon, 05/23/2016 - 17:17

Howdy -- what output are you seeing in the Apache error logs for that domain at the time you get that 500 error?

You can view that in $HOME/logs/error_log.

Submitted by securewebs on Mon, 05/23/2016 - 17:35 Pro Licensee

Failed loading /lib/ioncube/ioncube_loader_lin_5.2.so: /lib/ioncube/ioncube_loader_lin_5.2.so: cannot open shared object file: No such file or directory PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib64/php/modules/mcrypt.so' - /usr/lib64/php/modules/mcrypt.so: cannot open shared object file: No such file or directory in Unknown on line 0 Cannot load the ionCube PHP Loader - it was built with configuration 2.2.0, whereas running engine is API220090626,NTS

Submitted by andreychek on Mon, 05/23/2016 - 17:38

It sounds like the php.ini file is configured to load ioncube, but ioncube isn't actually installed.

Do you need ioncube though?

If not, it may just be a matter of disabling the line that's loading it.

If you need ioncube, then it's just a matter of installing it. That's a module that needs to be manually installed, there isn't a package for it.

Oh, also, I just noticed that there's a similar message for mcrypt. That one is easier to fix, you can just install the "php-mcrypt" package.

Submitted by securewebs on Tue, 05/24/2016 - 10:50 Pro Licensee

The client fixed his own server by deleting a setting /services/server configuration/php that had a "engine off" setting. Once removed the website(s) started to work.