[
https://issues.apache.org/jira/browse/AMBARI-17544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360668#comment-15360668
]
Hudson commented on AMBARI-17544:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #5216 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5216/])
AMBARI-17544. [Change Log Directory] Storm service is going down after
(aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f657a4d6bd00eeede3153cbeb0a732736b29d0e8])
* ambari-server/src/test/python/stacks/2.3/STORM/test_storm_base.py
*
ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/storm.py
* ambari-server/src/test/python/stacks/2.1/STORM/test_storm_base.py
> [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)
