Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D65BD200498 for ; Tue, 29 Aug 2017 13:39:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D4C7316642B; Tue, 29 Aug 2017 11:39:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2845516641F for ; Tue, 29 Aug 2017 13:39:04 +0200 (CEST) Received: (qmail 68510 invoked by uid 500); 29 Aug 2017 11:39:02 -0000 Mailing-List: contact issues-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 issues@ambari.apache.org Received: (qmail 68500 invoked by uid 99); 29 Aug 2017 11:39: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; Tue, 29 Aug 2017 11:39: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 DA617186A53 for ; Tue, 29 Aug 2017 11:39:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id nHB1EZ-gmn_v for ; Tue, 29 Aug 2017 11:39:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 042EE5F6C3 for ; Tue, 29 Aug 2017 11:39: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 5B1E4E0059 for ; Tue, 29 Aug 2017 11:39: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 0B48623F0D for ; Tue, 29 Aug 2017 11:39:00 +0000 (UTC) Date: Tue, 29 Aug 2017 11:39:00 +0000 (UTC) From: "Dmytro Sen (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-21839) METRICS_MONITOR start is failing due to "ImportError: cannot import name _common" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 29 Aug 2017 11:39:05 -0000 Dmytro Sen created AMBARI-21839: ----------------------------------- Summary: METRICS_MONITOR start is failing due to "ImportError: cannot import name _common" Key: AMBARI-21839 URL: https://issues.apache.org/jira/browse/AMBARI-21839 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.4.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.6.0 METRICS_MONITOR start is failing on one of the nodes of a cluster due to "ImportError: cannot import name _common". Ambari server version is 2.4.0.4.100. Seeing this error in 2.5.0.4.1 also. Redirecting psutils build output to log file to investigate the issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)