On 7/16/07, Richard Megginson <rmeggins@xxxxxxxxxx> wrote:
Nate Huddleson wrote:
> Thanks for your quick response, my clarifications are below
>
> On 7/16/07, *Richard Megginson* < rmeggins@xxxxxxxxxx
> <mailto:rmeggins@xxxxxxxxxx>> wrote:
>
> Nate Huddleson wrote:
> > I have attempted to follow the instructions included in the
> > HowTo:ChainOnUpdate, but have run into a problem when attempting to
> > configure the chaining backend for the chaining plugin.
> What problem?
>
> I am getting a "ldap_add: Local error" from ldap_modify when I attempt
> to import the following LDIF file:
What does it say in the Fedora DS access and error log?
my bad. I thought local error implied that it was an error that occured in the client. I got the following from the access and error logs, and after that, determined that the error occured because I had left off the trailing "/" on the URL. This has since solved my problem. Thanks for your help!
Access Log:
[16/Jul/2007:15:15:11 -0500] conn=2 fd=65 slot=65 connection from 10.105.12.125 to 10.105.12.125
[16/Jul/2007:15:15:11 -0500] conn=2 op=0 BIND dn="cn=Directory Manager" method=128 version=3
[16/Jul/2007:15:15:11 -0500] conn=2 op=0 RESULT err=0 tag=97 nentries=0 etime=0 dn="cn=directory manager"
[16/Jul/2007:15:15:11 -0500] conn=2 op=1 ADD dn="cn=chainbe1, cn=chaining database, cn=plugins, cn=config"
[16/Jul/2007:15:15:11 -0500] conn=2 op=1 RESULT err=82 tag=105 nentries=0 etime=0
[16/Jul/2007:15:15:11 -0500] conn=2 op=-1 fd=65 closed - B1
Error Log:
[16/Jul/2007:15:15:11 -0500] chaining database - Error with config attribute nsfarmserverurl : missing suffix
[16/Jul/2007:15:15:11 -0500] chaining database - Can't instantiate chaining backend instance chainbe1.
[16/Jul/2007:15:15:11 -0500] conn=2 fd=65 slot=65 connection from 10.105.12.125 to 10.105.12.125
[16/Jul/2007:15:15:11 -0500] conn=2 op=0 BIND dn="cn=Directory Manager" method=128 version=3
[16/Jul/2007:15:15:11 -0500] conn=2 op=0 RESULT err=0 tag=97 nentries=0 etime=0 dn="cn=directory manager"
[16/Jul/2007:15:15:11 -0500] conn=2 op=1 ADD dn="cn=chainbe1, cn=chaining database, cn=plugins, cn=config"
[16/Jul/2007:15:15:11 -0500] conn=2 op=1 RESULT err=82 tag=105 nentries=0 etime=0
[16/Jul/2007:15:15:11 -0500] conn=2 op=-1 fd=65 closed - B1
Error Log:
[16/Jul/2007:15:15:11 -0500] chaining database - Error with config attribute nsfarmserverurl : missing suffix
[16/Jul/2007:15:15:11 -0500] chaining database - Can't instantiate chaining backend instance chainbe1.
>
> -------------
> dn: cn=chainbe1, cn=chaining database, cn=plugins, cn=config
> objectclass: top
> objectclass: extensibleObject
> objectclass: nsBackendInstance
> cn: chainbe1
> nsslapd-suffix: dc=mycompany,dc=net
> nsfarmserverurl: ldaps://gigdev0062.mycompany.net:636
> nsmultiplexorbinddn: cn=Replication Manager, cn=config
> nsmultiplexorcredentials: testpass
> nsCheckLocalACI: on
> -------------
>
> I also attempted to import the file via JXplorer and perl's Net::LDAP
> module. Both failed with the same error (Error 82, in the case of
> JXplorer). When I attempted to create the object with just the dn, cn
> and objectclasses, it worked fine.
>
>
> > After digging for a while, I discovered that my problem seemed to be
> > that the attributes used (such as "nsFarmServerURL" and
> > "nsMultiplexorBindDN", etc, etc) are not defined in the schema.
> What leads you to believe this is the problem? The schema for this is
> defined internally in the server code, so there are no external
> schema
> files required to define this schema.
>
> I am using JXplorer to browse the LDAP, which provides a schema
> browser for whatever DB you are connected to. It does not list the
> attributes I listed above, but does show many of the other Fedora-DS
> specific attributes, as well as custom object classes and attributes
> that we have added.
These are internal only schema and are not exposed to clients.
>
> > I have checked out the source code for FDS 1.0, 1.0.1, 1.0.2, 1.0.3
> > and 1.0.4 and have not been able to find the schema file that
> contains
> > these attributes. Can anybody help me with finding the schema file
> > and/or the correct way to set up Chaining on Update?
> >
> > Thanks,
> > Nate.
> >
> > P.S. I am trying to set up a master-slave system with a Round Robin
> > DNS in front of it for load balancing. I wanted to set up the chain
> > on update so that all the clients can see the system as a single
> > server, rather than a collection of servers.
> >
> ------------------------------------------------------------------------
>
> >
> > --
> > Fedora-directory-devel mailing list
> > Fedora-directory-devel@xxxxxxxxxx
> <mailto:Fedora-directory-devel@xxxxxxxxxx>
> > https://www.redhat.com/mailman/listinfo/fedora-directory-devel
> >
>
> --
> Fedora-directory-devel mailing list
> Fedora-directory-devel@xxxxxxxxxx
> <mailto:Fedora-directory-devel@xxxxxxxxxx>
> https://www.redhat.com/mailman/listinfo/fedora-directory-devel
>
>
>
> ------------------------------------------------------------------------
>
> --
> Fedora-directory-devel mailing list
> Fedora-directory-devel@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/fedora-directory-devel
>
--
Fedora-directory-devel mailing list
Fedora-directory-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-devel
-- Fedora-directory-devel mailing list Fedora-directory-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-devel