A few days ago there was a discussion that was precisely the opposite: Someone who did NOT have a Red Hat Contract (therefore not running red hat) was trying to install RHS.
There was an answer about using the latest EPEL. Well, your case is not that, but, still, using 6.3, it might be worth (if at all possible) updating to 6.5 and running yum install again, jut in case. Hope it helps. just in case, refer to the discussion list archives of a few days back. On Fri, Mar 21, 2014 at 5:00 PM, Kamal MOULINE <[email protected]> wrote: > > > ---------- Forwarded message ---------- > From: Kamal MOULINE <[email protected]> > Date: Fri, Mar 21, 2014 at 3:32 PM > Subject: Re: [Gluster-users] Installation issue glusterfs-3.4.2 > To: "Kaleb S. KEITHLEY" <[email protected]> > > > I have this files: > > [root@localhost etc]# find / -name libssl* > /usr/lib64/libssl3.so > /usr/lib64/libssl.so.10 > /usr/lib64/libssl.so.1.0.0 > [root@localhost etc]# > > > On Fri, Mar 21, 2014 at 3:30 PM, Kamal MOULINE <[email protected]> wrote: > >> Hello Kaleb, >> >> libssl.so is not present. >> >> [root@localhost ~]# yum clean all >> Loaded plugins: product-id, refresh-packagekit, security, >> subscription-manager >> Updating certificate-based repositories. >> Cleaning repos: glusterfs-epel glusterfs-noarch-epel >> Cleaning up Everything >> [root@localhost ~]# >> >> [root@localhost ~]# yum install glusterfs >> Loaded plugins: product-id, refresh-packagekit, security, >> subscription-manager >> Updating certificate-based repositories. >> glusterfs-epel | 2.9 kB >> 00:00 >> glusterfs-epel/primary_db | 8.3 kB >> 00:00 >> glusterfs-noarch-epel | 2.9 kB >> 00:00 >> glusterfs-noarch-epel/primary_db | 2.2 kB >> 00:00 >> Setting up Install Process >> Resolving Dependencies >> --> Running transaction check >> ---> Package glusterfs.x86_64 0:3.4.2-1.el6 will be installed >> --> Processing Dependency: libssl.so.10(libssl.so.10)(64bit) for package: >> glusterfs-3.4.2-1.el6.x86_64 >> --> Processing Dependency: libcrypto.so.10(libcrypto.so.10)(64bit) for >> package: glusterfs-3.4.2-1.el6.x86_64 >> --> Processing Dependency: libglusterfs.so.0()(64bit) for package: >> glusterfs-3.4.2-1.el6.x86_64 >> --> Processing Dependency: libgfxdr.so.0()(64bit) for package: >> glusterfs-3.4.2-1.el6.x86_64 >> --> Processing Dependency: libgfrpc.so.0()(64bit) for package: >> glusterfs-3.4.2-1.el6.x86_64 >> --> Running transaction check >> ---> Package glusterfs.x86_64 0:3.4.2-1.el6 will be installed >> --> Processing Dependency: libssl.so.10(libssl.so.10)(64bit) for package: >> glusterfs-3.4.2-1.el6.x86_64 >> --> Processing Dependency: libcrypto.so.10(libcrypto.so.10)(64bit) for >> package: glusterfs-3.4.2-1.el6.x86_64 >> ---> Package glusterfs-libs.x86_64 0:3.4.2-1.el6 will be installed >> --> Processing Dependency: libcrypto.so.10(libcrypto.so.10)(64bit) for >> package: glusterfs-libs-3.4.2-1.el6.x86_64 >> --> Finished Dependency Resolution >> Error: Package: glusterfs-3.4.2-1.el6.x86_64 (glusterfs-epel) >> Requires: libcrypto.so.10(libcrypto.so.10)(64bit) >> Error: Package: glusterfs-libs-3.4.2-1.el6.x86_64 (glusterfs-epel) >> Requires: libcrypto.so.10(libcrypto.so.10)(64bit) >> Error: Package: glusterfs-3.4.2-1.el6.x86_64 (glusterfs-epel) >> Requires: libssl.so.10(libssl.so.10)(64bit) >> You could try using --skip-broken to work around the problem >> You could try running: rpm -Va --nofiles --nodigest >> [root@localhost ~]# >> >> >> >> >> >> >> >> On Fri, Mar 21, 2014 at 3:18 PM, Kaleb S. KEITHLEY >> <[email protected]>wrote: >> >>> On 03/21/2014 11:08 AM, Kamal MOULINE wrote: >>> >>>> --> Finished Dependency Resolution >>>> Error: Package: glusterfs-3.4.2-1.el6.x86_64 (glusterfs-epel) >>>> Requires: libcrypto.so.10(libcrypto.so.10)(64bit) >>>> Error: Package: glusterfs-libs-3.4.2-1.el6.x86_64 (glusterfs-epel) >>>> Requires: libcrypto.so.10(libcrypto.so.10)(64bit) >>>> Error: Package: glusterfs-3.4.2-1.el6.x86_64 (glusterfs-epel) >>>> Requires: libssl.so.10(libssl.so.10)(64bit) >>>> You could try using --skip-broken to work around the problem >>>> You could try running: rpm -Va --nofiles --nodigest >>>> [root@localhost ~]# >>>> =============== >>>> >>>> and the libcrypto.so.10 is present on my system: >>>> >>>> === >>>> [root@localhost ~]# find / -name libcry* >>>> /usr/lib64/libcryptui.so.0 >>>> /usr/lib64/libcrypt.so >>>> /usr/lib64/libcrypto.so.1.0.0 >>>> /usr/lib64/libcryptui.so.0.0.0 >>>> /usr/lib64/libcrypto.so.10 >>>> /usr/lib/x86_64-redhat-linux5E/lib64/libcrypt.so >>>> /usr/lib/x86_64-redhat-linux5E/lib64/libcrypt.a >>>> [root@localhost ~]# >>>> === >>>> >>>> Any advise will be very appreciated. >>>> >>> >>> What about libssl.so? Try `yum clean all` first then install gluster. >>> >>> -- >>> >>> Kaleb >>> >> >> > > > _______________________________________________ > Gluster-users mailing list > [email protected] > http://supercolony.gluster.org/mailman/listinfo/gluster-users >
_______________________________________________ Gluster-users mailing list [email protected] http://supercolony.gluster.org/mailman/listinfo/gluster-users
