Failure at vagrant up - ElasticSearch/WinRM about metasploitable3

[jbarnett-r7]

Are you still having problems with the build? We've pushed a few fixes recently that may have resolved it.

[jikuja]

I'm getting same. Using

• Current master: ef8fed0
• OS: Debian testing
• Packer: v0.10.2
• Vagrant: 1.9.1
• Virtualbox: 5.1.14

Full log for vagrant up https://gist.githubusercontent.com/anonymous/8bdcc2621d9f49869b1c002f59d444ce/raw/2408ba6093a20231a759560db58954f87f1bc64f/elastic.log Seems to be identical with this and #73.

[a-garcia]

Hi everyone,

I changed the sleep time from 5 to 30 seconds within the metasploitable3\scripts\installs\install_elasticsearch.bat file. I believe that the original 5 seconds is not enough time for some machines to start elasticsearch and run a successful GetResponse().

The specific line that I changed in metasploitable3\scripts\installs\install_elasticsearch.bat file was from this:
powershell -Command "Start-Sleep -s 5"

to this:
powershell -Command "Start-Sleep -s 30"

This is the first time I have ever commented on anything on GitHub, so hopefully this helps with this specific problem.

This is what I am currently using, just in case anyone is wondering.
Packer: 0.12.2
Vagrant: 1.9.1
Virtualbox: 5.1.14

[jikuja]

Thanks. That fixed the problem.

[jbarnett-r7]

Nice fix, @a-garcia. Definitely sounds like that timer should be increased to have better support for more systems. Would you mind submitting a PR with the change?

[jikuja]

How much is enough for waiting time? Should it poll service until it's running and returning 200 for requests?

[a-garcia]

@jbarnett-r7, I have attempted to submit the PR, please let me know if you don't see it. I haven't worked on a project in awhile so my git skills are a little rusty. Just kind of started tinkering with metasploitable :).

@jikuja, that sounds like an efficient way of solving that issue. A blanket time frame may not be the most optimal solution. How about a try catch? An issue I see is if for some reason the service does not start for some reason, does the polling functionality eventually stop? I think either way there might have to be some kind of timing mechanism for the given scenarios.