Logger install incomplete - ETH1 does not exist

[hackjalstead]

• Operating System Version: Windows 10
• Provider (VirtualBox/VMWare): VMWare
• Vagrant Version: 2.2.17
• Packer Version: 1.7.4
• Are you using stock boxes (downloaded) or were they built from scratch using Packer? Stock Boxes
• Is the issue reproducible or intermittent? Reproducible

Please verify that you are building from an updated Master branch before filing an issue. Yes pulling the latest Master

Description of the issue:

Fails on the Logger install. I have seen people with a similar issue but tickets are closed with no solutions

This same problem has occurred 4-5 times, I am trying to install on a D drive but have full admin rights.

Thanks for any help/advice, please see log below -

logger: [13:08:09]: [TEST] Validating that redis-server is correctly installed...
logger: [+] redis-server was successfully installed!
logger: [13:08:09]: [TEST] Validating that python-pip is correctly installed...
logger: [+] python-pip was successfully installed!
logger: Device "eth1" does not exist.
logger: Incorrect IP Address settings detected. Attempting to fix.
logger: Unknown interface eth1
logger: Device "eth1" does not exist.
logger: Unknown interface eth1
logger: eth1: error fetching interface information: Device not found
logger: [13:08:10]: Failed to fix the broken static IP for eth1. Exiting because this will cause problems with other VMs.

The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

[OriginalPwnster]

Also having this issue....has anyone found a fix?

[Thegrasscutter]

Good morning!
The issue is due to line 79 in vagrant/bootstrap.sh. It tries to check to see if the interface is created and has the correct IP. The command contains an error.
The solution is to edit that line to ETH1_IP=$(ifconfig eth1 | grep -oP '(?<=inet\s)\d+(\.\d+){3}')
This returns the correct interface and will not mess up the script.

Additionally, if you havn't allready, I also reccommend changing all 192.168.38.X to 192.168.56.X. To avoid IP errors down the line. Vim can do this using %s/192.168.38/192.168.56/g