Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 7 Dec 2016 10:40:58 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13026143.1481063185000.459790.1481107258473@Atlassian.JIRA>
In-Reply-To: <JIRA.13026143.1481063185000@Atlassian.JIRA>
References: <JIRA.13026143.1481063185000@Atlassian.JIRA> <JIRA.13026143.1481063185817@arcas>
Subject: [jira] [Commented] (AMBARI-19115) Metrics Monitor start failed:
 ERROR: Cannot write pid
 /grid/0/pid/metric_monitor/ambari-metrics-monitor.pid
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 07 Dec 2016 10:41:00 -0000


    [ https://issues.apache.org/jira/browse/AMBARI-19115?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15=
728420#comment-15728420 ]=20

Hadoop QA commented on AMBARI-19115:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest a=
ttachment=20
  http://issues.apache.org/jira/secure/attachment/12842130/AMBARI-19115.pat=
ch
  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 inclu=
de any new or modified tests.
                        Please justify why no new tests are needed for this=
 patch.
                        Also please list what manual steps were performed t=
o 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 incre=
ase the total number of release audit warnings.

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

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/9561//t=
estReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/9561/=
/console

This message is automatically generated.

> Metrics Monitor start failed: ERROR: Cannot write pid /grid/0/pid/metric_=
monitor/ambari-metrics-monitor.pid
> -------------------------------------------------------------------------=
----------------------------------
>
>                 Key: AMBARI-19115
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19115
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Vivek Rathod
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19115.patch
>
>
> STR: Install cluster with 4 services: HDFS, Flume, AMS and Smartsense, wi=
th custom PID's
> Metrics Monitor start fails while starting services
> {code}
> Traceback (most recent call last):
>   File "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/=
package/scripts/metrics_monitor.py", line 68, in <module>
>     AmsMonitor().execute()
>   File "/usr/lib/python2.6/site-packages/resource_management/libraries/sc=
ript/script.py", line 282, in execute
>     method(env)
>   File "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/=
package/scripts/metrics_monitor.py", line 42, in start
>     action =3D 'start'
>   File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py=
", line 89, in thunk
>     return fn(*args, **kwargs)
>   File "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/=
package/scripts/ams_service.py", line 103, in ams_service
>     user=3Dparams.ams_user
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py=
", line 155, in __init__
>     self.env.run()
>   File "/usr/lib/python2.6/site-packages/resource_management/core/environ=
ment.py", line 160, in run
>     self.run_action(resource, action)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/environ=
ment.py", line 124, in run_action
>     provider_action()
>   File "/usr/lib/python2.6/site-packages/resource_management/core/provide=
rs/system.py", line 262, in action_run
>     tries=3Dself.resource.tries, try_sleep=3Dself.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.p=
y", line 72, in inner
>     result =3D function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.p=
y", line 102, in checked_call
>     tries=3Dtries, try_sleep=3Dtry_sleep, timeout_kill_strategy=3Dtimeout=
_kill_strategy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.p=
y", line 150, in _call_wrapper
>     result =3D _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.p=
y", line 303, in _call
>     raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of '/usr/s=
bin/ambari-metrics-monitor --config /etc/ambari-metrics-monitor/conf start'=
 returned 1. ######## Hortonworks #############
> This is MOTD message, added for testing in qe infra
> Building psutil...
> running build
> running build_py
> creating build/lib.linux-x86_64-2.6
> creating build/lib.linux-x86_64-2.6/psutil
> copying psutil/__init__.py -> build/lib.linux-x86_64-2.6/psutil
> copying psutil/_common.py -> build/lib.linux-x86_64-2.6/psutil
> copying psutil/_compat.py -> build/lib.linux-x86_64-2.6/psutil
> copying psutil/_psbsd.py -> build/lib.linux-x86_64-2.6/psutil
> copying psutil/_pslinux.py -> build/lib.linux-x86_64-2.6/psutil
> copying psutil/_psosx.py -> build/lib.linux-x86_64-2.6/psutil
> copying psutil/_psposix.py -> build/lib.linux-x86_64-2.6/psutil
> copying psutil/_pssunos.py -> build/lib.linux-x86_64-2.6/psutil
> copying psutil/_pswindows.py -> build/lib.linux-x86_64-2.6/psutil
> running build_ext
> building '_psutil_linux' extension
> creating build/temp.linux-x86_64-2.6
> creating build/temp.linux-x86_64-2.6/psutil
> gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURC=
E=3D2 -fexceptions -fstack-protector --param=3Dssp-buffer-size=3D4 -m64 -mt=
une=3Dgeneric -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-=
D_FORTIFY_SOURCE=3D2 -fexceptions -fstack-protector --param=3Dssp-buffer-si=
ze=3D4 -m64 -mtune=3Dgeneric -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/inclu=
de/python2.6 -c psutil/_psutil_linux.c -o build/temp.linux-x86_64-2.6/psuti=
l/_psutil_linux.o
> psutil/_psutil_linux.c: In function =E2=80=98psutil_proc_cpu_affinity_set=
=E2=80=99:
> psutil/_psutil_linux.c:327: warning: suggest explicit braces to avoid amb=
iguous =E2=80=98else=E2=80=99
> gcc -pthread -shared build/temp.linux-x86_64-2.6/psutil/_psutil_linux.o -=
L/usr/lib64 -lpython2.6 -o build/lib.linux-x86_64-2.6/_psutil_linux.so
> building '_psutil_posix' extension
> gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURC=
E=3D2 -fexceptions -fstack-protector --param=3Dssp-buffer-size=3D4 -m64 -mt=
une=3Dgeneric -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-=
D_FORTIFY_SOURCE=3D2 -fexceptions -fstack-protector --param=3Dssp-buffer-si=
ze=3D4 -m64 -mtune=3Dgeneric -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/inclu=
de/python2.6 -c psutil/_psutil_posix.c -o build/temp.linux-x86_64-2.6/psuti=
l/_psutil_posix.o
> gcc -pthread -shared build/temp.linux-x86_64-2.6/psutil/_psutil_posix.o -=
L/usr/lib64 -lpython2.6 -o build/lib.linux-x86_64-2.6/_psutil_posix.so
> Verifying Python version compatibility...
> Using python  /usr/bin/python2.6
> Checking for previously running Metric Monitor...
> Starting ambari-metrics-monitor
> /usr/sbin/ambari-metrics-monitor: line 63: /grid/0/pid/metric_monitor/amb=
ari-metrics-monitor.pid: Permission denied
> ERROR:  Cannot write pid /grid/0/pid/metric_monitor/ambari-metrics-monito=
r.pid.
> {code}


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