ambari-issues 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-17544) [Change Log Directory] Storm service is going down after modifying the storm_log_dir variable
Date Sun, 03 Jul 2016 15:24:10 GMT

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

Hadoop QA commented on AMBARI-17544:
------------------------------------

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

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

    {color:green}+1 tests included{color}.  The patch appears to include 2 new or modified
test files.

    {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/7668//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7668//console

This message is automatically generated.

> [Change Log Directory] Storm service is going down after modifying the storm_log_dir
variable
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17544
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17544
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17544.patch
>
>
> What i did
> Through ambari ui modified the variable storm_log_dir from
>     
>     
>      /var/log/storm 
> to
>     
>     
>      /tmp/log/storm 
> Clicked on Services -> restart all required
> The Background Service Windows showed the operation as successful. But the
> service was not started.
> Observed that log files were getting created under /var/log/storm and the file
> supervisor.out contained
>     
>     
>     
>     JMXetricAgent instrumented JVM, see https://github.com/ganglia/jmxetric
>     Jun 29, 2016 7:55:22 AM info.ganglia.gmetric4j.GMonitor start
>     INFO: Setting up 1 samplers
>     2016-06-29 07:59:00,654 FATAL Ignoring log event after log4j was shut down
>     



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

Mime
View raw message