ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-9510) Metric Monitor can not be started
Date Fri, 06 Feb 2015 15:09:36 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-9510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309276#comment-14309276
] 

Hadoop QA commented on AMBARI-9510:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12697022/AMBARI-9510.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/1609//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1609//console

This message is automatically generated.

> Metric Monitor can not be started
> ---------------------------------
>
>                 Key: AMBARI-9510
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9510
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics, ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Blocker
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9510.patch
>
>
> After deploying Metric Monitor can not be started.
> /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out contains:
> psutil binaries need to be built by running, psutil/build.py manually or by running a,
mvn clean package, command.
> {noformat}
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/site-packages/resource_monitoring/main.py", line 27, in <module>
>     from core.controller import Controller
>   File "/usr/lib/python2.6/site-packages/resource_monitoring/core/controller.py", line
28, in <module>
>     from metric_collector import MetricsCollector
>   File "/usr/lib/python2.6/site-packages/resource_monitoring/core/metric_collector.py",
line 23, in <module>
>     from host_info import HostInfo
>   File "/usr/lib/python2.6/site-packages/resource_monitoring/core/host_info.py", line
22, in <module>
>     import psutil
>   File "/usr/lib/python2.6/site-packages/resource_monitoring/psutil/build/lib.linux-x86_64-2.6/psutil/__init__.py",
line 89, in <module>
>     import psutil._pslinux as _psplatform
>   File "/usr/lib/python2.6/site-packages/resource_monitoring/psutil/build/lib.linux-x86_64-2.6/psutil/_pslinux.py",
line 20, in <module>
>     from psutil import _common
> ImportError: cannot import name _common
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message