You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Sam Ruby (JIRA)" <ji...@apache.org> on 2016/03/06 17:39:40 UTC

[jira] [Updated] (INFRA-11193) ldaps://ldap2-us-west.apache.org:636 often does not respond

     [ https://issues.apache.org/jira/browse/INFRA-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sam Ruby updated INFRA-11193:
-----------------------------
    Status: Waiting for Infra  (was: Closed)

I'll note that the choice of LDAP servers is made by the infrastructure team, based on the configuration of the hosting colo.  This information finds its way into /etc/ldap/ldap.conf, which is what the whimsy code uses to determine what server(s) to use.

If the infrastructure team would like a different set of servers to be used, the configuration for the colo should be updated.

> 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)