From dev-return-57822-archive-asf-public=cust-asf.ponee.io@directory.apache.org Fri Jul 13 11:08:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id DB5E6180676 for ; Fri, 13 Jul 2018 11:08:03 +0200 (CEST) Received: (qmail 65748 invoked by uid 500); 13 Jul 2018 09:08:02 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 65620 invoked by uid 99); 13 Jul 2018 09:08:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jul 2018 09:08:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 568D1180635 for ; Fri, 13 Jul 2018 09:08:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id cRfgTBAcVwCC for ; Fri, 13 Jul 2018 09:08:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 429775F4E5 for ; Fri, 13 Jul 2018 09:08:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 81CE7E1034 for ; Fri, 13 Jul 2018 09:08:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2908123F9A for ; Fri, 13 Jul 2018 09:08:00 +0000 (UTC) Date: Fri, 13 Jul 2018 09:08:00 +0000 (UTC) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DIRSERVER-2241) Is there any tools to monitor apacheds MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DIRSERVER-2241?page=3Dcom.atlas= sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D= 16542752#comment-16542752 ]=20 Emmanuel Lecharny commented on DIRSERVER-2241: ---------------------------------------------- No, we haven't add any monitor tools yet. Although you can have an idea of = how many connection are used using netstat on linux. CPU usage can be gathe= red using teh 'sar' command on linux too. Last, not least, you can active some logs in the server, that could provide= some information on what's going on. Now, it's hard to tell you what's wrong or misconfigured, we have no idea o= n how your data are organized, nor their exact size, and the way the server= is being used.=20 As I said in the other ticket, the complete configuration would help a bit,= plus the list of requests the server receives. Last, not least, the client may ends connection brutally, leaving them open= for a very long time (typically 2 hours before it hits an OS timeout). > Is there any tools to monitor apacheds > -------------------------------------- > > Key: DIRSERVER-2241 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2241 > Project: Directory ApacheDS > Issue Type: Wish > Reporter: cokuehuang > Priority: Major > > Can anybody help me ?Is there any tools to monitor apacheds, like cpu, cu= rrent number of connection, aviliable number of connection, request time an= d=C2=A0 so on? Sometimes we found that some java process forget to close co= nnection of ldap, the server crash down when no connection can be got.Thank= s a lot! -- This message was sent by Atlassian JIRA (v7.6.3#76005)