Thanks Nick,

I have left my comment. Is there any other information I can provide to
help troubleshoot this?

- Dima

On 10/12/2016 08:20 PM, Nick Allen wrote:
> We do have an open issue on this;
> https://issues.apache.org/jira/browse/METRON-353
>
> It would be great if anyone seeing this issue, would chime in with a
> comment on the JIRA describing their experience (just like Dima).  If you
> are an overachiever and want a gold star, add the output of running
> `metron-deployment/scripts/platform-info.sh` to your JIRA comment.
>
> On Wed, Oct 12, 2016 at 12:32 PM, Dima Kovalyov <dima.koval...@sstech.us>
> wrote:
>
>> I can confirm that I start mysqld manually every time (performed around
>> 10 single-node installs). Was wondering whether I did something wrong.
>>
>> - Dima
>>
>> On 10/12/2016 04:30 PM, Carolyn Duby wrote:
>>> I instantiated quick-dev twice and had the same results. Not quite
>> statistically significant yet but definitely a trend.
>>> Carolyn
>>>
>>>
>>>
>>>
>>> On 10/12/16, 9:27 AM, "Nick Allen" <n...@nickallen.org> wrote:
>>>
>>>> Thanks, Carolyn.  Good to know that you are experiencing that too.  I
>>>> wasn't sure if it was a "sometimes" kind of thing.
>>>>
>>>> On Wed, Oct 12, 2016 at 9:20 AM, Carolyn Duby <cd...@hortonworks.com>
>> wrote:
>>>>> Rita:  Here is the command to restart mysql
>>>>>
>>>>> sudo service mysqld start
>>>>>
>>>>>
>>>>> Michael Young posted an article on debugging quick dev that contains a
>> lot
>>>>> of helpful hints:
>>>>>
>>>>> https://community.hortonworks.com/content/kbentry/59801/
>>>>> troubleshooting-missing-events-in-metron-quick-dev.html
>>>>>
>>>>>
>>>>> I think the monit configuration for mysql may be incorrect.  The mysql
>>>>> service doesn’t come up by itself.  You have to start it after you
>> create
>>>>> quick dev.
>>>>>
>>>>> Thanks
>>>>> Carolyn
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 10/12/16, 8:47 AM, "Nick Allen" <n...@nickallen.org> wrote:
>>>>>
>>>>>> It seems to work for me.  Something like the following...
>>>>>>
>>>>>> - name: "Check for Metron jar path: {{ metron_jar_path }}"
>>>>>>>   local_action: stat path={{ metron_jar_path }}
>>>>>>>   become: false
>>>>>>>   register: metron_jars
>>>>>>>
>>>>>>> - name: Verify Metron jars exist
>>>>>>>   fail: msg="Unable to locate staged Metron jars at {{
>> metron_jar_path
>>>>>>> }}.  Did you run 'mvn package'?"
>>>>>>>   when: not metron_jars.stat.exists
>>>>>> On Wed, Oct 12, 2016 at 8:24 AM, Kyle Richardson <
>>>>> kylerichards...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I like that idea. It seems much cleaner. Let me give it a try.
>>>>>>>
>>>>>>> On Tue, Oct 11, 2016 at 9:53 PM, Nick Allen <n...@nickallen.org>
>> wrote:
>>>>>>>> Does it really need to sudo? Can we do something like "become:
>> false"
>>>>> so
>>>>>>> it
>>>>>>>> doesn't try to sudo?
>>>>>>>>
>>>>>>>> On Oct 11, 2016 9:33 PM, "Kyle Richardson" <
>> kylerichards...@gmail.com
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Ok, I think I have the fix for this. With the new local_action
>>>>> logic,
>>>>>>>>> ansible is checking the jar path on the host with sudo but doesn't
>>>>> have
>>>>>>>> the
>>>>>>>>> password. Just need to add the line below to the Vagrantfile.
>>>>>>>>>
>>>>>>>>> ansible.ask_sudo_pass = true
>>>>>>>>>
>>>>>>>>> I will test tomorrow and, if successful, open a new PR for the fix.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Oct 11, 2016 at 8:42 PM, Kyle Richardson <
>>>>>>>>> kylerichards...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> This error could be related to my PR that was merged today
>>>>>>> (METRON-492
>>>>>>>>>> <https://github.com/apache/incubator-metron/pull/302>). I tested
>>>>>>> this
>>>>>>>>>> successfully in a single node vm deployment, but not with vagrant.
>>>>>>>>> Perhaps
>>>>>>>>>> there is something about vagrant that doesn't like the ansible
>>>>>>>>> local_action
>>>>>>>>>> logic? I'm trying to reproduce the error now.
>>>>>>>>>>
>>>>>>>>>> On Tue, Oct 11, 2016 at 7:06 PM, Nick Allen <n...@nickallen.org>
>>>>>>>> wrote:
>>>>>>>>>>> Hi Rita -
>>>>>>>>>>>
>>>>>>>>>>> Yes, I was seeing this same issue today.  I haven't looked into
>>>>> the
>>>>>>>>> cause
>>>>>>>>>>> yet, but you can comment out that check and proceed with the
>>>>>>> install.
>>>>>>>>>>> Doing this from memory, but I believe it is in
>>>>>>>>>>> metron-deployment/roles/metron_common/tasks/main.yml.  Comment
>>>>> out
>>>>>>> or
>>>>>>>>>>> delete any task that references the "metron_jar_path" variable.
>>>>>>> There
>>>>>>>>> are
>>>>>>>>>>> two tasks that need commented out.
>>>>>>>>>>>
>>>>>>>>>>> I will try and get a fix out tomorrow.
>>>>>>>>>>>
>>>>>>>>>>> On Oct 11, 2016 6:35 PM, "Rita McKissick" <
>>>>>>> rmckiss...@hortonworks.com
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> *** Resending because this message seemed to disappear into the
>>>>>>>> ether
>>>>>>>>>>> and
>>>>>>>>>>>> I didn’t receive a copy of it.
>>>>>>>>>>>>
>>>>>>>>>>>> I’m having difficulties with the latest Quick Development
>>>>> Platform
>>>>>>>>>>>> installation. During deployment I received the following error
>>>>>>>>> message:
>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>
>>>>>>>>>>>> TASK [metron_common : Check for Metron jar path]
>>>>>>>>>>>> *******************************
>>>>>>>>>>>> fatal: [node1 -> localhost]: FAILED! => {"changed": false,
>>>>>>> "failed":
>>>>>>>>>>> true,
>>>>>>>>>>>> "module_stderr": "sudo: a password is required\n",
>>>>>>> "module_stdout":
>>>>>>>>> "",
>>>>>>>>>>>> "msg": "MODULE FAILURE", "parsed": false}
>>>>>>>>>>>>
>>>>>>>>>>>> PLAY RECAP ******************************
>>>>>>>>> ******************************
>>>>>>>>>>>> *********
>>>>>>>>>>>> node1                      : ok=20   changed=2    unreachable=0
>>>>>>>>>>> failed=1
>>>>>>>>>>>> Ansible failed to complete successfully. Any error output
>>>>> should
>>>>>>> be
>>>>>>>>>>>> visible above. Please fix these errors and try again.
>>>>>>>>>>>>
>>>>>>>>>>>> ---------------------------------
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Everything up to this point looked fine.
>>>>>>>>>>>>
>>>>>>>>>>>> By the way, I installed the latest Quick-Dev installation
>>>>> earlier
>>>>>>>> this
>>>>>>>>>>>> afternoon and it didn’t install/configure any topologies.
>>>>> That’s
>>>>>>>> why I
>>>>>>>>>>> did
>>>>>>>>>>>> a second install … which turned out even worse.
>>>>>>>>>>>>
>>>>>>>>>>>> Anyone else having this issue? Can someone help me with a fix
>>>>> or
>>>>>>>>>>>> workaround?
>>>>>>>>>>>>
>>>>>>>>>>>> Thank you!
>>>>>>>>>>>>
>>>>>>>>>>>> Rita
>>>>>>>>>>>>
>>>>>>>>>>>> Rita McKissick ! Sr. Technical Writer
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Nick Allen <n...@nickallen.org>
>>>>
>>>> --
>>>> Nick Allen <n...@nickallen.org>
>>
>

Reply via email to