Bug 911474
Summary: | Invalid chaining config triggers a disk full error and shutdown | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Jiri Pallich <jpallich> |
Component: | 389-ds-base | Assignee: | Rich Megginson <rmeggins> |
Status: | CLOSED ERRATA | QA Contact: | Sankar Ramalingam <sramling> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.4 | CC: | abienven, dpal, jgalipea, jpallich, mkubik, mreynolds, nhosoi, nkinder, pm-eus, rmeggins, tlavigne |
Target Milestone: | rc | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 389-ds-base-1.2.11.15-12.el6_4 | Doc Type: | Bug Fix |
Doc Text: |
Due to an incorrect interpretation of an error code, a directory server considered an invalid chaining configuration setting as the disk full error and shut down unexpectedly. Now, a more appropriate error code is in use and the server no longer shuts down from invalid chaining configuration settings.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-03-11 18:38:51 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: | |||
Bug Depends On: | 830334, 913144 | ||
Bug Blocks: |
Description
Jiri Pallich
2013-02-15 06:48:15 UTC
test setup instance chain: ldap://dstet-mkubik.brq.redhat.com:3333/ instance dstet-mkubik: ldap://dstet-mkubik.brq.redhat.com:2222/ (chain instance might not be even necessary) $ service dirsrv status dirsrv chain (pid 7179) is running... dirsrv dstet-mkubik (pid 4802) is running... $ cat chain.ldif dn: cn=example link,cn=chaining database,cn=plugins,cn=config changetype: add objectclass: top objectclass: extensibleObject objectclass: nsBackendInstance nsslapd-suffix: dc=example,dc=com nsfarmserverurl: ldap://dstet-mkubik.brq.redhat.com:3333/ nsMultiplexorBindDN: cn=directory manager nsMultiplexorCredentials: Secret123 cn: example link $ ldapmodify -x -D "cn=directory manager" -w Secret123 -h localhost -p 2222 -a -f chain.ldif adding new entry "cn=example link,cn=chaining database,cn=plugins,cn=config" ldap_add: Can't contact LDAP server (-1) Log: [28/Feb/2013:11:30:15 +0100] chaining database - Error with config attribute nsMultiplexorBindDn (cn=directory manager: forbidden value) [28/Feb/2013:11:30:15 +0100] chaining database - Can't instantiate chaining backend instance example link. $ service dirsrv status dirsrv chain (pid 7179) is running... dirsrv dstet-mkubik (pid 4802) is running... Marking verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0628.html |