Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

Blackside

10 Posts

9249

June 23rd, 2005 13:00

OMI 4.4 linux x86_64 install problem

Hi,
It bails out with:

warning: instsvc-drivers-5.0.0-1.i386.rpm: V3 DSA signature: NOKEY, key ID 23b66a9d
error: Failed dependencies:
        libncurses.so.5 is needed by srvadmin-isvc-4.4.0-339.i386
        libncurses.so.5 is needed by srvadmin-omacore-4.4.0-339.i386
        libpam.so.0 is needed by srvadmin-omacore-4.4.0-339.i386
 
These libs DO exist in /usr/lib64/
 
Any ideas?

tester25

626 Posts

June 23rd, 2005 17:00

Yes, there are two packages that need to be installed.  The Compatibility Arch Support packages that are part of the list of packages in Add/Remove programs in RHEL.  I had this same problem.  I forgot exactly what they are called but I know they included "Compatibility Arch" in the names.

Let us know what happens.

UPDATE - The note on this page mentions them actually:  http://www.centos.org/docs/4/html/rhel-ig-ppc-multi-en-4/s1-pkgselection.html

Message Edited by tester25 on 06-23-2005 01:10 PM

Blackside

10 Posts

June 24th, 2005 07:00

Ok, thanks!

But what are the names of those packages that are part of the Compat Arch group?

Im not running X on this server so I do not have the luxury of a gui where I can Add/Remove packages....

Ive been searching redhat/rhn for Compat Arch and similar but no luck :-(

Cheers

tester25

626 Posts

June 24th, 2005 13:00

Actually, I found something else that will be easier for you.
 
After you extract the OMSA install files,
 
1.  Go to extractedfolder/linux/RPMS/RH4_x86_64 (If that's the OS that you've got installed)
 
2.  Type rpm -Uvh *.rpm
 
3.  Then install OMSA
 
Let us know how this works.

Blackside

10 Posts

June 24th, 2005 17:00

Oh,
I didnt see those. But, in order to install theese I need to do a --force and what difference is there between the ncurses-5.4-13.i386.rpm in that folder and the ncurses-5.4-13.i386.rpm I get from redhat? Is it just adding links to the already existing libs or ...?
Sorry for beeing a little paranoid but Im a little control freak and need to know :-)
 
Thanks for the help!
 
BTW doing rpm -Uvh *.rpm gives me :
error: Failed dependencies:
        libglib-2.0.so.0 is needed by pam-0.77-65.1.i386
 
But, I already have that lib in /usr/lib64/libglib-2.0.so.0
Also, I already have pam-0.77-66.5 installed so why is pam-0.77-65 needed?
 
To me this seems like Dell has not completely managed to make their OM app compatible with the basic RedHat x86_64 install.... (It installs without any fuss on my regular 32-bit systems)
I hate being dependent on separate rpms (non redhat) for already existing files/libs. What hapens when an update from redhat shows up and overwrites existing non redhat, modified?, libs and such. Will the OM app just stop working or worse? Will it damage my system in some way?
 
Sorry for the rant ;-)
 

Message Edited by Blackside on 06-24-2005 11:00 PM

Message Edited by Blackside on 06-24-2005 11:04 PM

Blackside

10 Posts

August 10th, 2005 15:00

Anyone else have this problem?

tester25

626 Posts

August 15th, 2005 17:00

All of these RPMs that are included with the OpenManage Install (inside srvadmin/linux/RPMS/RH4_x86_64) are included on the RedHat Installation CDs.  The version numbers of the RPMs may change but the actual RPMs that are needed will not change.  OMSA is still a 32Bit application so when it is installed on a 64Bit Linux System, it is making use of all of the old 32Bit RPMs/Shared object files.  So rather than looking for all of these .so files inside /usr/lib64, it is going to /usr/lib, which is where the 32Bit shared object library is located.  As you may have already noticed, there are 2 versions of each RPM available on your RedHat Installation Media.  The x86_64 version of RPM and the i386 version of the RPM.  OMSA needs the i386 version of the RPMs because that is the 32Bit version.  One way to resolve these dependencies on your own without using the RPMs that Dell includes is to find out which RPM the 64Bit version of the .so file is using.  An example is "rpm -q --whatprovides /usr/lib64/libglib-2.0.so.0".  This will tell you which RPM provides this shared object file.  Then try to find the i386 version of that RPM on your Linux Install Media and rpm -ivh it.

Does all that make sense?

Message Edited by tester25 on 08-15-2005 01:27 PM

View More

View All

No Events found!

Top