Hi Laurens, I don't see any errors, but it does seem like the log output is light in number of tasks executed. Just an fyi, we recently revamped the way we do the Vagrant deployments to leverage Ambari MPacks via Ansible rather than Ansible alone. This is per https://issues.apache.org/jira/browse/METRON-671. The next time you build and deploy, I would try with the latest master branch.
Best, Mike On Tue, Mar 14, 2017 at 8:58 AM, Laurens Vets <laur...@daemon.be> wrote: > Hi Michael, > > See http://pastebin.com/xHS3mVuA for the Ansible log. > > Kind regards, > > Laurens > > On 2017-03-09 10:58, Michael Miklavcic wrote: > > Thanks for providing that info. The ansible log should be at > incubator-metron/metron-deployment/vagrant/full-dev-platform/ansible.log > > On Thu, Mar 9, 2017 at 8:56 AM, Laurens Vets <laur...@daemon.be> wrote: > >> Hi Michael, >> >> No worries, it got all sorted in the end. Where can I find the Ansible >> logs? >> >> OS: >> >> laurens@lof:~/Source/incubator-metron$ cat /etc/lsb-release >> DISTRIB_ID=Ubuntu >> DISTRIB_RELEASE=16.04 >> DISTRIB_CODENAME=xenial >> DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" >> laurens@lof:~/Source/incubator-metron$ >> >> The output of platform-info.sh: >> >> laurens@lof:~/Source/incubator-metron$ metron-deployment/scripts/plat >> form-info.sh >> Metron 0.3.1 >> -- >> * master >> -- >> commit 22591a7cbe7c373b8744caf8a96d1b358e0d419e >> Author: merrimanr <merrim...@gmail.com> >> Date: Tue Mar 7 16:10:56 2017 -0500 >> >> METRON-758 HdfsServiceImplTest should sort files for list test >> (merrimanr via ottobackwards) closes apache/incubator >> -metron#474 >> -- >> metron-deployment/vagrant/full-dev-platform/Vagrantfile | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> -- >> ansible 2.0.0.2 >> config file = /etc/ansible/ansible.cfg >> configured module search path = Default w/o overrides >> -- >> Vagrant 1.8.1 >> -- >> Python 2.7.12 >> -- >> Apache Maven 3.3.9 >> Maven home: /usr/share/maven >> Java version: 1.8.0_121, vendor: Oracle Corporation >> Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre >> Default locale: en_US, platform encoding: UTF-8 >> OS name: "linux", version: "4.4.0-64-generic", arch: "amd64", family: >> "unix" >> -- >> Linux lof 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 UTC 2017 >> x86_64 x86_64 x86_64 GNU/Linux >> -- >> Total System Memory = 32164.2 MB >> Processor Model: Intel(R) Xeon(R) CPU L5639 @ 2.13GHz >> Processor Speed: 1600.000 MHz >> Processor Speed: 1733.000 MHz >> Processor Speed: 1600.000 MHz >> Processor Speed: 1733.000 MHz >> Processor Speed: 1600.000 MHz >> Processor Speed: 1733.000 MHz >> Processor Speed: 1600.000 MHz >> Processor Speed: 2000.000 MHz >> Processor Speed: 1600.000 MHz >> Total Physical Processors: 24 >> Total cores: 144 >> Disk information: >> /dev/mapper/vg-root 1.8T 22G 1.7T 2% / >> /dev/sda5 961M 139M 774M 16% /boot >> /dev/mapper/vg-tmp 945M 2.5M 878M 1% /tmp >> laurens@lof:~/Source/incubator-metron$ >> >> On 2017-03-08 18:57, Michael Miklavcic wrote: >> >> Hi Laurens, Sorry this turned out to be some trouble for you. We will >> occasionally have services go down since we're pushing a lot into a small >> VM, but I really don't expect to see as many dead services as you're seeing >> there. Would you mind passing along your environment info including primary >> OS version? If you happen to have the Ansible logs, that would be helpful >> as well. After fixing the ssh problem, running 'vagrant provision' should >> have set everything straight. >> >> On Wed, Mar 8, 2017 at 3:23 PM, Laurens Vets <laur...@daemon.be> wrote: >> >>> Hello list, >>> >>> For future reference, after I've successfully set up the >>> full-dev-platform, I still had a couple of small issues: >>> >>> - The following services were not running: >>> >>> Supervisor / Storm >>> RegionServer / HBase >>> Nimbus / Storm >>> HBase Master / HBase >>> >>> Manually starting them in the Ambari GUI fixed this. >>> >>> - I did not know the login/password of the Services GUI ( >>> http://node1:2812/). This turned out to be admin/monit. >>> >>> - Elastic Search & Kibana were not running. This is fixed by doing: >>> >>> $ vagrant ssh >>> $ sudo su - >>> >>> # /etc/init.d/elasticsearch start >>> >>> # /etc/init.d/kibana start >>> >> >> >
