www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-11193) ldaps://ldap2-us-west.apache.org:636 often does not respond
Date Mon, 14 Mar 2016 22:25:33 GMT

    [ https://issues.apache.org/jira/browse/INFRA-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194286#comment-15194286
] 

Chris Lambertus commented on INFRA-11193:
-----------------------------------------

You can override with, for example,

ldapclient::ldapservers: 'ldaps://ldap1-lw-us.apache.org:636 ldaps://ldap2-lw-us.apache.org:636'

The full list of ldap servers is defined in common.yaml ldapserver::slapd_peers. For non-internal
applications, only the ldap* hosts should be used. The others are for server-specific local
lookups. 


> ldaps://ldap2-us-west.apache.org:636 often does not respond
> -----------------------------------------------------------
>
>                 Key: INFRA-11193
>                 URL: https://issues.apache.org/jira/browse/INFRA-11193
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: LDAP
>            Reporter: Sebb
>            Assignee: Geoffrey Corey
>            Priority: Trivial
>
> The LDAP server ldaps://ldap2-us-west.apache.org:636 often fails to respond when contacted
by Whimsy.
> Note that the server does usually work OK. However AFAICR it is the only one that has
been reported as failing by Whimsy, so there may be an issue with the server or connectivity
that is worth noting.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message