Topic: Installing mcrypt for PHP & upgrading glibc files

[edb]

I'm trying to install mcrypt for PHP on a SME v6.0.1 server. Mcrypt is a way of encrypting and decrypting PHP files and is necessary for running our custom designed ecommerce site.

I downloaded the mcrypt rpm and prceeded to install the rpm but here is the result:
[root@mail rpms]# rpm -Uvh mcrypt-2.6.4-3.i386.rpm
error: failed dependencies:
        libc.so.6(GLIBC_2.3)   is needed by mcrypt-2.6.4-3
        libmcrypt.so.4   is needed by mcrypt-2.6.4-3
        libmhash.so.2   is needed by mcrypt-2.6.4-3

So I downloaded the missing dependencies and installed with the following error:  :cry:
[root@mail rpms]# rpm -Uvh glibc-2.3.2-11.9.i386.rpm
error: failed dependencies:
        glibc-common = 2.3.2-11.9 is needed by glibc-2.3.2-11.9
        glibc > 2.2.5 conflicts with glibc-common-2.2.5-43

The other libmcrypt.so.4 and libmhash.so.2 seemed to install just fine with the following output:

[root@mail rpms]# rpm -Uvh libmcrypt-2.5.7-1.dag.rh73.i386.rpm
Preparing...                ########################################### [100%]
   1:libmcrypt              ########################################### [100%]
[root@mail rpms]# rpm -Uvh libmhash-0.9.1-1.rh73.dag.i386.rpm
Preparing...                ########################################### [100%]
   1:libmhash               ########################################### [100%]

I then tried to install the glibc-common dependency rpm and received the following error:

[root@mail rpms]# rpm -Uvh glibc-common-2.3.2-11.9.i386.rpm
error: failed dependencies:
        glibc < 2.3.2 conflicts with glibc-common-2.3.2-11.9
        glibc-common = 2.2.5-43 is needed by glibc-2.2.5-43

I seem to be duped as far as upgrading the glib files. If anyone can help me I'd sure appeciate it. Thanks in advance to all that responde.

Ed

[edb]

I think I found part of my issue and that is that there is a link in /lib that is called libc.so.6 that points to libc-2.2.5.so.
The problem that I'm having relates to the fact that the "mcrypt" module that I'm trying to install requires libc.so.6 if this makes any sense.

Any suggestions appreciated. Thanks

Ed

[CharlieBrady]

So I downloaded the missing dependencies and installed with the following error:  
[root@mail rpms]# rpm -Uvh glibc-2.3.2-11.9.i386.rpm
error: failed dependencies:
        glibc-common = 2.3.2-11.9 is needed by glibc-2.3.2-11.9
        glibc > 2.2.5 conflicts with glibc-common-2.2.5-43
Ed

You need to upgrade glibc and glibc-common in the one command.

[edb]

Thanks for your reply CharlieB.  

Do you know if it is safe for me to upgrade the glibc files to the most current? I would hate to break something since my server is working perfectly right now.
When you say "in one command" can you give me an example because I'm not sure what you mean.
Thanks again for your reply.

Ed

[CharlieBrady]

Thanks for your reply CharlieB.  

Do you know if it is safe for me to upgrade the glibc files to the most current? I would hate to break something since my server is working perfectly right now.

No, I don't know. rpm will usually tell you if there's a dependency you'll break by upgrading glibc. But if you don't want to risk breaking it, don't change it. At the very least, do the upgrade on a test system first.

[quote[
When you say "in one command" can you give me an example ... [/quote]

rpm -Uhv glibc-2*rpm glibc-common-2*rpm

[edb]

Charlie

Thanks again for your reply to my previous post and I tried the command as you indicated and you are right the rpms seemed to install properly.
I then attempted to install the "mcrypt" rpm that needed the "glibc" dependencies installed first and here is the output:
[root@mail rpms]# rpm -Uvh glibc-2.3.2-11.9.i386.rpm glibc-common-2.3.2-11.9.i386.rpm
Preparing...                ########################################### [100%]
   1:glibc-common           ########################################### [ 50%]
   2:glibc                  warning: /etc/localtime created as /etc/localtime.rpmnew
warning: /etc/nsswitch.conf created as /etc/nsswitch.conf.rpmnew
########################################### [100%]
[root@mail rpms]# rpm -q glibc
glibc-2.3.2-11.9
[root@mail rpms]# rpm -Uvh mcrypt-2.6.4-3.i386.rpm
Preparing...                ########################################### [100%]
Segmentation fault

What is a "segmentation fault"? Is there something else that I need to do? I sure appreciate your opinion. Thanks

Ed

[CharlieBrady]

Charlie
[root@mail rpms]# rpm -Uvh mcrypt-2.6.4-3.i386.rpm
Preparing...                ########################################### [100%]
Segmentation fault

What is a "segmentation fault"?
Ed

It means roughly the same as "General Protection Error". It means either that you have a program bug, or a problem with hardware. In your case I would guess that your "rpm" program is not compatible with the glibc and glibc-common RPMs which you just installed. Good think it was only on a test box, eh?

If you're lucky, you will be able to roll back to your original glibc packages, using:

rpm -Uhv --oldpackages glibc-xxxx*rpm glibc-common-xxx*rpm

(when xxx matches the original package version - e.g. on your original CDROM).

[edb]

Thanks for your prompt reply Charlie.

That really sucks ... one minute it can't install without the upgraded rpms then it's conflicting with them?
Thanks for your help.

Ed

[CharlieBrady]

That really sucks ... one minute it can't install without the upgraded rpms then it's conflicting with them?

You're in what's known as dependency hell. What you really need is an mcrypt RPM which was compiled against the version of glibc that you already have installed, i.e. one compiled for use on RedHat 7.3.

[edb]

Figures, the one I selected was for "RedHat and other" and they didn't relate the download to RH version numbers.
I tried the command that you gave me to revert back:
[root@mail rpms]# rpm -Uhv --oldpackages glibc-2.2.5*rpm glibc-common-2.2.5*rpm
--oldpackages: unknown option

But the output wasn't relieving my frustration with this whole thing. Is there some other command that would allow me to revert back? Thanks

Ed

[edb]

I tried to revert without the --oldpackages option

[root@mail rpms]# rpm -Uhv glibc-2.2.5*rpm glibc-common-2.2.5*rpm               Preparing...                ########################################### [100%]
package glibc-2.3.2-11.9 (which is newer than glibc-2.2.5-44) is already installed
package glibc-common-2.3.2-11.9 (which is newer than glibc-common-2.2.5-44) is already installed
[root@mail rpms]#

but no luck. Do you think I could use the -e option to remove the rpms then reinstall the old ones with the -Uvh option. I understand that Linux needs these libraries to function properly.

Ed

[CharlieBrady]

I tried to revert without the --oldpackages option

Why?

[root@mail rpms]# rpm -Uhv glibc-2.2.5*rpm glibc-common-2.2.5*rpm               Preparing...                ########################################### [100%]
package glibc-2.3.2-11.9 (which is newer than glibc-2.2.5-44) is already installed
package glibc-common-2.3.2-11.9 (which is newer than glibc-common-2.2.5-44) is already installed
[root@mail rpms]#

No surprises there.

but no luck. Do you think I could use the -e option to remove the rpms then reinstall the old ones with the -Uvh option. I understand that Linux needs these libraries to function properly.

So how do expect it to function after you use the -e option?

[edb]

I tried it and here is how it responds

[root@mail rpms]# rpm -e glibc-2.3.2-11.9.i386.rpm glibc-common-2.3.2-11.9.i386.rpm
error: package glibc-2.3.2-11.9.i386.rpm is not installed
error: package glibc-common-2.3.2-11.9.i386.rpm is not installed
[root@mail rpms]#

What the heck does it mean ... of course it's installed.
I thought worst case senario that I would have to start fresh and restore from a backup.

Ed

[edb]

BTW Charlie everything seems to work properly exept that I can no longer install rpms.
I tried to install the myphpadmin upgrade just for kicks and it gave me the same segmentation error.
Sorry, just found out that email stopped working with this error:
The server responded with an error. Account: '192.168.10.11', Server: '192.168.10.11', Protocol: POP3, Server Response: 'Incorrectly built binary which accesses errno, h_errno or _res directly. Needs to be fixed.', Port: 110, Secure(SSL): No, Server Error: 0x800CCC90, Error Number: 0x800CCC90

[CharlieBrady]

I tried it

Why?

and here is how it responds

[root@mail rpms]# rpm -e glibc-2.3.2-11.9.i386.rpm glibc-common-2.3.2-11.9.i386.rpm
error: package glibc-2.3.2-11.9.i386.rpm is not installed
error: package glibc-common-2.3.2-11.9.i386.rpm is not installed
[root@mail rpms]#

What the heck does it mean ... of course it's installed.

No, the package named glibc-2.3.2-11.9 is installed, not the package named glibc-2.3.2-11.9.i386.rpm. What you've provided is a file name, not an RPM package name.

It won't let you remove glibc anyway - fortunately.

I thought worst case senario that I would have to start fresh and restore from a backup.

Yeah, that would be worst case.

Have you tried reverting using the --oldpackage option? If not, why not?