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

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15130638#comment-15130638 ] 

Geoffrey Corey commented on INFRA-11193:
----------------------------------------

One of the issues you might be seeing is that whimsy-vm2 is in a different hosting provider than ldap2-us-west. We have an ldapsync monitor and it hasn't reported anything about ldap2-us-west. On whimsy-vm2, ldap2-us-west is listed as a fallback ldap server in case it cannot connect to ldap3-us-west.

Also, for all the hosts in puppet3 (infrastructure-puppet repo) that are in osuosl, ldap2-us-west is the primary ldap server.

Until there is more evidence of issues with ldap2-us-west, I'm chalking it up to cross datacenter network stuff.

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