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

Nick Allen commented on METRON-353:
-----------------------------------

I also regularly experience this issue.  MySQL does not seem to start when i 
stand-up Quick-Dev.  I can manually start MySQL just fine.  I can even use 
Monit to trigger the start of MySQL manually.

{code}
$ ./metron-deployment/scripts/platform-info.sh
Metron 0.2.1BETA
--
* master
--
commit 609ea40c2e8ab3b35b645f4238d2f66afc120fb5
Author: cstella <ceste...@gmail.com>
Date:   Tue Oct 11 13:59:45 2016 -0400

    METRON-488: Snort should use a proper CSV implementation (cestella via 
mmiklavc) closes apache/incubator-metron#297
--
--
ansible 2.0.0.2
  config file =
  configured module search path = Default w/o overrides
--
Vagrant 1.8.1
--
Python 2.7.12
--
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
2015-11-10T11:41:47-05:00)
Maven home: /usr/local/Cellar/maven/3.3.9/libexec
Java version: 1.8.0_66, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_66.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
--
Darwin HW12402.local 15.6.0 Darwin Kernel Version 15.6.0: Mon Aug 29 20:21:34 
PDT 2016; root:xnu-3248.60.11~1/RELEASE_X86_64 x86_64
{code}

> Monit unable to start mysqld after successful single node vagrant deployment
> ----------------------------------------------------------------------------
>
>                 Key: METRON-353
>                 URL: https://issues.apache.org/jira/browse/METRON-353
>             Project: Metron
>          Issue Type: Bug
>    Affects Versions: 0.2.1BETA
>         Environment: Quick dev setup installation using vagrant on Macbook 
> Pro.
>            Reporter: Anand Subramanian
>              Labels: metronqe
>             Fix For: 0.2.1BETA
>
>         Attachments: messages, messages-20160725, output-platform-info.rtf
>
>
> This is a single node quick-dev deployment from HEAD using vagrant on a 
> Macbook Pro.  The platform-info output is attached.
> I noticed that monit was not able to start despite trying multiple times and 
> I had to start it manually post-deployment. 
> Note that post-installation, I am able to manually start the mysqld service 
> and it comes up fine.
> Here are the relevant lines from the /var/log/messages on the vagrant node. 
> {code}
> Jul 25 10:30:11 node1 ansible-command: Invoked with warn=True executable=None 
> chdir=None _raw_params=monit start mysql removes=None creates=None 
> _uses_shell=True
> <snip>
> Jul 25 10:30:21 node1 ansible-command: Invoked with warn=True executable=None 
> chdir=None _raw_params=monit start mysql removes=None creates=None 
> _uses_shell=True
> Jul 25 10:30:32 node1 ansible-command: Invoked with warn=True executable=None 
> chdir=None _raw_params=monit start mysql removes=None creates=None 
> _uses_shell=True
> Jul 25 10:30:42 node1 ansible-command: Invoked with warn=True executable=None 
> chdir=None _raw_params=monit start mysql removes=None creates=None 
> _uses_shell=True
> Jul 25 10:30:52 node1 ansible-command: Invoked with warn=True executable=None 
> chdir=None _raw_params=monit start mysql removes=None creates=None 
> _uses_shell=True
> Jul 25 10:31:02 node1 ansible-command: Invoked with warn=True executable=None 
> chdir=None _raw_params=monit start mysql removes=None creates=None 
> _uses_shell=True
> <snip>
> {code}
> From the /var/log/mysqld.log, I could see that there was a shutdown initiated 
> after monit tried restarting bunch of times:
> {code}
> 2016-07-25T10:30:55.152359Z 0 [Note] Giving 0 client threads a chance to die 
> gracefully
> 2016-07-25T10:30:55.152397Z 0 [Note] Shutting down slave threads
> 2016-07-25T10:30:55.152405Z 0 [Note] Forcefully disconnecting 0 remaining 
> clients
> 2016-07-25T10:30:55.152471Z 0 [Note] Event Scheduler: Purging the queue. 0 
> events
> 2016-07-25T10:30:55.153536Z 0 [Note] Binlog end
> 2016-07-25T10:30:55.154549Z 0 [Note] Shutting down plugin 'validate_password'
> 2016-07-25T10:30:55.154573Z 0 [Note] Shutting down plugin 'ngram'
> 2016-07-25T10:30:55.154577Z 0 [Note] Shutting down plugin 'ARCHIVE'
> 2016-07-25T10:30:55.154581Z 0 [Note] Shutting down plugin 'partition'
> 2016-07-25T10:30:55.154584Z 0 [Note] Shutting down plugin 'BLACKHOLE'
> 2016-07-25T10:30:55.154588Z 0 [Note] Shutting down plugin 'CSV'
> 2016-07-25T10:30:55.154601Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
> 2016-07-25T10:30:55.154621Z 0 [Note] Shutting down plugin 'MyISAM'
> 2016-07-25T10:30:55.154631Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL'
> 2016-07-25T10:30:55.154635Z 0 [Note] Shutting down plugin 
> 'INNODB_SYS_DATAFILES'
> 2016-07-25T10:30:55.154638Z 0 [Note] Shutting down plugin 
> 'INNODB_SYS_TABLESPACES'
> 2016-07-25T10:30:55.154640Z 0 [Note] Shutting down plugin 
> ‘INNODB_SYS_FOREIGN_COLS'
> <snip>
> {code}



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

Reply via email to