node-1 does not have /opt/zookeeper-3.4.8 directory

[msamogh]

All the VMs except node-1 have the /opt/zookeeper-3.4.8 directory, and seem to be working fairly fine. The VMs are running on ubuntu/trusty.

[mkrcah]

I cannot reproduce this. When I do fresh provisioning, ssh into node-1, the /opt/zookeeper-3.4.8 is there:

$ vagrant ssh node-1
vagrant@node-1:~$ ls /opt
zookeeper-3.4.8

Could you please provide more info?

[msamogh]

Same here. I'm unable to reproduce it since I did a fresh install. Of
course, it's important to note that the error was also part of a different
fresh install. I did have to Ctrl+C a few times during the vagrant up
command, so I'm not sure if that caused an issue.

On Wed, Oct 12, 2016, 10:17 Marcel Krcah notifications@github.com wrote:

I cannot reproduce this. When I do fresh provisioning, ssh into node-1,
the /opt/zookeeper-3.4.8 is there:

$ vagrant ssh node-1
vagrant@node-1:~$ ls /opt
zookeeper-3.4.8

Could you please provide more info?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#5 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLGMrdR0WHiGBwi62ykG64B1nR2u1utks5qzGZMgaJpZM4KRrtx
.

Best,
Amogh Mannekote

[mkrcah]

Yes, ctrl+c could very much cause this. vagrant up might take 3-5 minutes to complete, since it downloads VM and installs Java on each node. It should not be interrupted, otherwise the nodes are not provisioned properly.