Netware Webserver - LDAP errors on Apache screen

Author

LDAP errors on Apache screen

rgainesNOSPAM_65203@yahoo.com

2006-07-25, 7:11 pm

I'm seeing the following errors on our NW6.5 SP3 box:
>14:30:42 14:30:42 ldap *MASTER[domain.com] down
>14:32:40 14:32:40 *MASTER[domain.com][-1] ldap_simple_bind : Can't contact
LDAP server(81)
>14:33:40 14:33:40 *MASTER[domain.com][0] ldap_simple_bind : Can't contact
LDAP server(81)
>14:34:40 14:34:40 *MASTER[domain.com][1] ldap_simple_bind : Can't contact
LDAP server(81)

this continues through iterations 2 through 7 (see # in brackets above)
but then
>14:40:37 14:40:37 ldap *MASTER[domain.com] connection restored
Then it starts all over
>14:42:35 14:42:35 *MASTER[domain.com][-1] ldap_simple_bind : Can't contact
LDAP server(81)

iFolder is installed but is not being used currently.
FYI at one point we were getting recurring LDAP errors somewhat like these
and changing the LdapPort setting from 636 to 389 in
\Apache2\iFolder\Server\HTTPD_iFolder_NW
.CONF made them go away.

1) Suggestions?
2) If there is a log file which contains all of these notes where is it? I
want to see how long this has been happening since it seems new to this box.
3) Is this even a problem? I and the users are experiencing no side
effects. Prior to updating Apache to 2.0.55 this condition caused a memory
leak in Apache2.nlm which eventually consumed all memory, but there's no
memory leak today.

Thanks in advance!

Anders Gustafsson

2006-07-26, 7:11 am

,
> 1) Suggestions?
Fix iFolder

> 2) If there is a log file which contains all of these notes where is it? I
> want to see how long this has been happening since it seems new to this box.
> 3) Is this even a problem?

Not unless you want to use iFolder, in which case:

IFolder simple troubleshooting steps:

1. iFolder 2.x needs eDirectory 8.6.2 or better for LDAP. It will not
work with NW 5.1 DS 8.82 for example.
2. Check that the admin name in the iFolder server config file is
correct
3. Use the clear-text LDAP (389) port for troubleshooting
(SSL/TLS tab, turn off "require TLS", see below)
4. Have iFolder log its screen to a file (below)
5. Turn on LDAP tracing on the LDAP Server Object
(Screen options tab, check at least "connection" and "response")
6. LOAD DSTRACE. Turn off everything and turn on LDAP, then try to log
in.
7. Does it work if you bypass the proxy in your browser?

Does the new iFolder help?
http://support.novell.com/servlet/f...ifolder213.exe/
(This is for 6.0. For 6.5, use SP2)

Note on 4:
Change startifolder.ncf to read:
LOAD ADDRESS SPACE = IFOLDER APACHE -s -f
SYS:APACHE\IFOLDER\SERVER\HTTPD.CONF
(all on one line)

Note on 3:
1. LDAP Server Object, SSL/TLS Config Page
Untick "Require TLS for All Operations"
2. LDAP Group Object
Untick "Require TLS for simple binds with password"

Note on 6:
LOAD DSTRACE
DSTRACE -ALL
DSTRACE +LDAP
DSTRACE SCREEN ON
DSTRACE FILE On

The trace file is called DSTRACE.LOG and is in sys:system

For some helpful tips:
http://nscsysop.hypermart.net/ifolder.html
http://www.gordonross.org.uk/iFolder.html

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop
Pedago, The Aaland Islands (N60 E20)

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

Using VA 5.51 build 315 on Windows 2000 build 2195

Guenter

2006-07-27, 1:11 pm

rgainesNOSPAM_65203@yahoo.com Wrote:
> I'm seeing the following errors on our NW6.5 SP3 box:
> contact
> LDAP server(81)
> contact
> LDAP server(81)
> contact
> LDAP server(81)
>
> this continues through iterations 2 through 7 (see # in brackets
> above)
> but then
> Then it starts all over
> contact
> LDAP server(81)
>
> iFolder is installed but is not being used currently.
> FYI at one point we were getting recurring LDAP errors somewhat like
> these
> and changing the LdapPort setting from 636 to 389 in
> \Apache2\iFolder\Server\HTTPD_iFolder_NW
.CONF made them go away.
>
> 1) Suggestions?
> 2) If there is a log file which contains all of these notes where is
> it? I
> want to see how long this has been happening since it seems new to this
> box.
> 3) Is this even a problem? I and the users are experiencing no side
> effects. Prior to updating Apache to 2.0.55 this condition caused a
> memory
> leak in Apache2.nlm which eventually consumed all memory, but there's
> no
> memory leak today.
>
> Thanks in advance!
I guess this came up with SP3 - I had that too, and IIRC it was
something with the load order of the original mod_auth_ldap and
Novell's patched mod_auth_ldap2...
probably you have just secured a directory, and the standard
mod_auth_ldap was introduced?
Anyway, I believe it was fixed with later SPs, f.e SP4a and SP5 dont
show this issue AFAICT.

Guenter.

--
Guenter