[
https://issues.apache.org/jira/browse/METRON-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527140#comment-15527140
]
ASF GitHub Bot commented on METRON-466:
---------------------------------------
GitHub user dlyle65535 opened a pull request:
https://github.com/apache/incubator-metron/pull/279
METRON-466: Full Dev Platform build sometimes fails
Tested on Full Dev and Quick Dev.
Ambari seems to have changed their response in 2.4.0.1-1, if you request
"START ALL" on a cluster where all services are already started, it doesn't
actually make a request, so there is no request ID reported back.
I also suppressed starting of the Yaf probe (because we don't run the
parser topology for Yaf) and bumped java_home so Snort would work.
I needed to separate the inventory directories for quick and full dev
certain properties (in this case java_home) can lag between quick and full dev.
Note- Full dev still doesn't come up cleanly after the build successfully
completes due to what looks like insufficient memory. I've opened
[METRON-467](https://issues.apache.org/jira/browse/METRON-467).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dlyle65535/incubator-metron METRON-466
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/279.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #279
----
commit 64f2256bb549db1ee8bbf1870f628ca6a649a422
Author: David Lyle <[email protected]>
Date: 2016-09-27T17:29:04Z
METRON-466: Full Dev Platform build sometimes fails
----
> Full Dev Platform build sometimes fails
> ---------------------------------------
>
> Key: METRON-466
> URL: https://issues.apache.org/jira/browse/METRON-466
> Project: Metron
> Issue Type: Bug
> Reporter: David M. Lyle
> Assignee: David M. Lyle
>
> Full Dev Platform build will sometimes fail with:
> "Ambari client exception occurred: No JSON object could be decoded"
> As a workaround to the services not all starting, we have 2 calls to start
> all services in the Vagrant deploy. The second call seems to fail if the
> services are already started.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
