Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B864A114D8 for ; Thu, 4 Sep 2014 20:41:24 +0000 (UTC) Received: (qmail 442 invoked by uid 500); 4 Sep 2014 20:41:24 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 412 invoked by uid 500); 4 Sep 2014 20:41:24 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 399 invoked by uid 99); 4 Sep 2014 20:41:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Sep 2014 20:41:24 +0000 Date: Thu, 4 Sep 2014 20:41:24 +0000 (UTC) From: "Mahadev konar (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-7153) Admin: error printed to log when going to admin view MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121952#comment-14121952 ] Mahadev konar commented on AMBARI-7153: --------------------------------------- +1 for the patch. > Admin: error printed to log when going to admin view > ---------------------------------------------------- > > Key: AMBARI-7153 > URL: https://issues.apache.org/jira/browse/AMBARI-7153 > Project: Ambari > Issue Type: Bug > Components: ambari-views > Affects Versions: 1.7.0 > Reporter: Siddharth Wagle > Assignee: Siddharth Wagle > Fix For: 1.7.0 > > Attachments: AMBARI-7153.patch > > > After logging into ambari (using a local user), and going to Ambari Admin, there is an ERROR and exception printed to ambari-server.log. > NOTE: Done nothing with LDAP. This just shows up w/o any ldap or attempt to configure ldap. > {code} > 23:05:18,855 ERROR [qtp1661965622-24] AmbariLdapDataPopulator:99 - Could not connect to LDAP server > org.springframework.ldap.CommunicationException: localhost:33389; nested exception is javax.naming.CommunicationException: localhost:33389 [Root exception is java.net.ConnectException: Connection refused] > at org.springframework.ldap.support.LdapUtils.convertLdapException(LdapUtils.java:100) > at org.springframework.ldap.core.support.AbstractContextSource.createContext(AbstractContextSource.java:266) > at org.springframework.ldap.core.support.AbstractContextSource.getContext(AbstractContextSource.java:106) > at org.springframework.ldap.core.support.AbstractContextSource.getReadOnlyContext(AbstractContextSource.java:125) > at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:287) > at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:259) > at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:571) > at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:556) > at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:411) > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)