I've fixed the problem I mailed you about yesterday, and debugged your
eDir88 module abit now.

There are a couple of major issues in the eDir88 RA's status check, I
ran into the following;

It assumes that you use an ip-address for the n4u.server.interfaces
parameter.

It only supports one single interface

As for the documentation, it states,

n4u.server.interfaces

The IP address and port number the eDirectory server should listen to
for client connections. The value can be a comma-separated list
specifying more than one combination of possible settings. You can
specify the value as <Interface name>|<IP Address>@<port>. You can
specify either the whole string or the interface name or IP address. If
the parameter is not specified in the nds.conf file, the eDirectory
server gets any one IP address with the default port specified in the
n4u.server.interfaces parameter. If the n4u.server.interfaces parameter
is also not specified, the default port will be 524. The possible values
are given below.

      * Interface name | IP Address - The eDirectory server gets the
        specified interface name or IP address with the default port.
      * Interface name | IP [EMAIL PROTECTED] - The eDirectory server gets
        the specified interface name or IP address with the specified
        port number.

The problem I had was because of both these issues. I have a virtual IP
that I move along with the cluster resource (ofcourse I can change
nds.conf to point to this IP instead of eth0:0 but still, it will break
again on other installation if it isn't checked in the RA), and I open a
listener port on both the virtual interface and the loopback.

Ie, my configuration looked like this:

n4u.server.interfaces=eth0:[EMAIL PROTECTED],[EMAIL PROTECTED]

As it is today, eDir88 can't handle that. I haven't supplied a patch but
it's an easy fix now that you know what the problem is I hope.

Johan
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to