php-mcrypt hosed?

madsere · Unread post by **madsere** » Wed Sep 28, 2005 8:31 am

Yum-update'ed php and php-mcrypt ... but phpinfo doesn't show it.

Any idea what's wrong?

# rpm -qa | grep ^php
php-mcrypt-4.4.0-3.rhel3.art
php-mbstring-4.4.0-3.rhel3.art
php-mysql-4.4.0-3.rhel3.art
php-pear-4.4.0-3.rhel3.art
php-4.4.0-3.rhel3.art

Restarted httpd, anything else needed doin for mcrypt to turn up as module?

Unread post by **scott** » Wed Sep 28, 2005 9:59 am

That should be all you have to do. Are you sure you're not looking at a cached web page?

madsere · Unread post by **madsere** » Wed Sep 28, 2005 1:08 pm

Quite sure. By renaming an ioncube directory I can provoke a different error message.

# rpm -qa | grep mcrypt
php-mcrypt-4.4.0-3.rhel3.art
libmcrypt-devel-2.5.7-1.rhel3.art
libmcrypt-2.5.7-1.rhel3.art

What am I doing wrong?

Unread post by **scott** » Wed Sep 28, 2005 1:16 pm

Ah thats something I always forget about, you've got to upgrade Ioncube and/or Zend when you upgrade php. Also, make sure you're not replacing your php.ini with the one from the rpm. I dont think the paths are set up correctly in it.

madsere · Unread post by **madsere** » Wed Sep 28, 2005 2:14 pm

It's a new installation, downloaded and installed latest ioncube version at the same time.

Also, make sure you're not replacing your php.ini with the one from the rpm

There's only one php.ini on the server. Please explain?

breun · Unread post by **breun** » Wed Sep 28, 2005 7:08 pm

I just installed 4.4.0-3 from art and noticed that MySQL was not working with PHP. I noticed the php.ini from art's rpm has

extension_dir = "./"

while my old copy had:

extension_dir = "/usr/lib/php4"

I put that last path in and everything is working again.

madsere · Unread post by **madsere** » Wed Sep 28, 2005 9:11 pm

Yep, that was the problem!

Thanks!

madsere · Unread post by **madsere** » Wed Sep 28, 2005 9:58 pm

Hm, that was not the only problem in this php.ini. Next error was unable to connect to mysql. By copying a php.ini from an older installation, I got over that just to get a new problem:

Warning: mysql_connect(): Client does not support authentication protocol requested by server; consider upgrading MySQL client in.... Mysql is tested and works fine from the CLI so I think this is probably yet another PHP problem.

I think I'd like to install the previuos version of php and modules instead - is there a way to do that with yum? How?

Also, may I suggest only tested software goes into the production repositories? It seems this particular php version belongs in "beta" ...

madsere · Unread post by **madsere** » Thu Sep 29, 2005 1:46 am

I made a phpinfo() script and it says, under mysql:

Client API version 3.23.58

The mysql version we have installed is 4.1 - how come it still says clietn API is 3.23 ?

# rpm -qa | grep -i mysql
mysql-server-4.1.12-1.rhel3.art
mysql-4.1.12-1.rhel3.art
perl-DBD-MySQL-2.1021-3
php-mysql-4.4.0-3.rhel3.art
mysql-compat-4.1.12-1.rhel3.art

breun · Unread post by **breun** » Thu Sep 29, 2005 4:30 am

The art MySQL rpms are made like that so that Plesk still works with MySQL. It shows the API version to be 3.23.x, but internally it's really 4.x.

Unread post by **scott** » Thu Sep 29, 2005 7:25 am

I link php against whatever the native mysql install is for that distribution (so for CentOS4 users, they'd have mysql 4.1, everyone else has mysql 3). That way you don't also have to upgrade mysql along with php.