Bug 445367
Summary: | openoffice.org2 x86_64 + LDAP fails without nscd | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Chris Hunter <chris.hunter> |
Component: | distribution | Assignee: | RHEL Program Management <pm-rhel> |
Status: | CLOSED WONTFIX | QA Contact: | Daniel Riek <riek> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 4.6 | CC: | jplans, nalin |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-20 16:12:00 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Chris Hunter
2008-05-06 14:54:43 UTC
You've got the 32-bit office package installed, which uses the 32-bit libc, so it needs the 32-bit version of the nss_ldap plugin for libc. Is there a 64-bit version of the package available? Is this a combination that you get by default in the distribution (installed that way? you got there using yum?) or did you get here some other way? I _think_ openoffice.org2 only exists as 32bit packages for RHEL 4.6; I will have to double-check. There is a 32bit version of nss_ldap, which we have never used. There appears to be only a 64bit version of nscd available. These systems were orginally installed as x86_64 RHEL 4.3 or RHEL 4.5, and then set to automatically download software updates/service packs as they become available. So this should be the default combination for a 64bit "workstation" install. Okay, if you can only get a 32-bit openoffice.org2, then you'll have to install the 32-bit nss_ldap package in order for it to be able to look up user information when nscd isn't running. (Because processes only communicate with nscd over a socket, a 64-bit nscd can also be used by 32-bit applications, but the same isn't true for loadable modules like nss_ldap.) Moving this to 'distribution', though I'm not sure if this belongs there, or in 'comps' or in 'up2date' or 'anaconda'. Can't install 32bit nss_ldap because it wants 32bit openldap package, which conflict with the x86_64 openldap package. Suggestions ? (In reply to comment #3) > Okay, if you can only get a 32-bit openoffice.org2, then you'll have to install > the 32-bit nss_ldap package in order for it to be able to look up user > information when nscd isn't running. (Because processes only communicate with > nscd over a socket, a 64-bit nscd can also be used by 32-bit applications, but > the same isn't true for loadable modules like nss_ldap.) > > Moving this to 'distribution', though I'm not sure if this belongs there, or in > 'comps' or in 'up2date' or 'anaconda'. Think I found the problem. I disabled start_tls encryption between the x86_64 workstations & our ldap server and openoffice2 now works. I had problems with "sudo" in RedHat 5.0 & 5.1 hosts when they used start_tls encryption to our redhat 4.3 openldap server. Perhaps these problems are related ? I don't see how they could be. The 64-bit plugin shouldn't be more or less loadable by a 32-bit application based on the contents of the configuration file which that plugin would consult. The problems has re-occured. The solution is to install the 32bit plugin (nss_ldap.i386). However, it requires openldap.i386 which conflicts with openldap.x86_64 which is installed by default. My fix is to force uninstall openldap.x86_64 (rpm --nodeps) then install openldap.i386 + nss_ldap.i386. I can't install openldap.x86_64 and openldap.i386 st the same time. Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. Please See https://access.redhat.com/support/policy/updates/errata/ If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue. |