Repository: clong/DetectionLab

Issue #604: Hanging on "Waiting for fleet service to start..."
Created: 2021-02-15T17:33:40Z
Operating System Version: MacOS Catalina version 10.15.7
Deploying via (VirtualBox/VMWare/AWS/Azure/ESXi): VirtualBox
Vagrant Version (if applicable): Vagrant 2.2.14

Please verify that you are building from an updated Master branch before filing an issue.
Description of the issue:
While building the logger host it is hanging while waiting for fleet service to start. Not sure how long it takes to start the service, but I'm figuring it should be fairly quick sub 30mins I could be wrong though and am just being impatient.
    logger: Init script installed at /etc/init.d/splunk.
    logger: Init script is configured to run at boot.
    logger: [17:11:58]: Downloading Palantir osquery configs...
    logger: Cloning into 'osquery-configuration'...
    logger: [17:11:59]: Installing Fleet...
    logger: mysql: 
    logger: [Warning] Using a password on the command line interface can be insecure.
    logger: No URLs found in -.
    logger: unzip:  cannot find or open fleet.zip, fleet.zip.zip or fleet.zip.ZIP.
    logger: cp: 
    logger: cannot stat 'fleet/linux/fleetctl'
    logger: : No such file or directory
    logger: cp: 
    logger: cannot stat 'fleet/linux/fleet'
    logger: : No such file or directory
    logger: /tmp/vagrant-shell: line 280: fleet: command not found
    logger: cp: 
    logger: target '/opt/fleet/' is not a directory
    logger: Created symlink /etc/systemd/system/multi-user.target.wants/fleet.service → /etc/systemd/system/fleet.service.
    logger: [17:12:00]: Waiting for fleet service to start...

I have attempted the troubleshooting steps outlined here: troubleshooting which did not resolve the issue.
Link to Gist Containing Build Logs:
N/A

Duplicate issue #605: Terraform stuck at Logger "Still creating"
Created: 2021-02-15T22:38:42Z
Operating System Version: Windows 10
Deploying via: AWS/Terraform

Description of the issue: (seems related to issue:604 )
While building the logger host via "terraform apply", I'm running into the following loop (I have let this go for up to 3 hours) :
aws_instance.logger (remote-exec): Resolving deltas: 100% (94/94), done.
aws_instance.logger (remote-exec): [22:08:50]: Installing Fleet...
aws_instance.logger (remote-exec): mysql: [Warning] Using a password on the command line interface can be insecure.
aws_instance.logger (remote-exec): No URLs found in -.
aws_instance.logger (remote-exec): unzip:  cannot find or open fleet.zip, fleet.zip.zip or fleet.zip.ZIP.
aws_instance.logger (remote-exec): cp: cannot stat 'fleet/linux/fleetctl': No such file or directory
aws_instance.logger (remote-exec): cp: cannot stat 'fleet/linux/fleet': No such file or directory
aws_instance.logger (remote-exec): /opt/DetectionLab/Vagrant/logger_bootstrap.sh: line 280: fleet: command not found
aws_instance.logger (remote-exec): cp: target '/opt/fleet/' is not a directory
aws_instance.logger (remote-exec): Created symlink /etc/systemd/system/multi-user.target.wants/fleet.service → /etc/systemd/system/fleet.service.
aws_instance.logger (remote-exec): [22:08:51]: Waiting for fleet service to start...
aws_instance.dc: Still creating... [4m30s elapsed]
aws_instance.logger: Still creating... [4m30s elapsed]
aws_instance.dc (remote-exec):  The install of winpcap was successful.
aws_instance.dc (remote-exec):   Software install location not explicitly set, could be in package or
aws_instance.dc (remote-exec):   default install location if installer.

aws_instance.dc (remote-exec): Chocolatey installed 1/1 packages.
aws_instance.dc (remote-exec):  See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

aws_instance.dc (remote-exec): C:\Users\vagrant>ipconfig /renew

aws_instance.dc (remote-exec): Windows IP Configuration


aws_instance.dc (remote-exec): Ethernet adapter Ethernet 5:

aws_instance.dc (remote-exec):    Connection-specific DNS Suffix  . : us-west-1.compute.internal
aws_instance.dc (remote-exec):    IPv4 Address. . . . . . . . . . . : 192.168.38.102
aws_instance.dc (remote-exec):    Subnet Mask . . . . . . . . . . . : 255.255.255.0
aws_instance.dc (remote-exec):    Default Gateway . . . . . . . . . : 192.168.38.1

aws_instance.dc (remote-exec): C:\Users\vagrant>powershell.exe -c "Add-Content 'c:\windows\system32\drivers\etc\hosts' '        192.168.38.103    wef.windomain.local'"
aws_instance.logger: Still creating... [4m41s elapsed]
aws_instance.dc: Still creating... [4m41s elapsed]
aws_instance.dc: Still creating... [4m51s elapsed]
aws_instance.logger: Still creating... [4m51s elapsed]
aws_instance.dc: Still creating... [5m1s elapsed]
aws_instance.logger: Still creating... [5m1s elapsed]
aws_instance.dc: Creation complete after 5m3s [id=i-0f23a7b337c046e48]
aws_vpc_dhcp_options.default: Creating...
aws_vpc_dhcp_options.default: Creation complete after 0s [id=dopt-0e04a5a134378d890]
aws_vpc_dhcp_options_association.default: Creating...
aws_vpc_dhcp_options_association.default: Creation complete after 1s [id=dopt-0e04a5a134378d890-vpc-0e711bf19ce736ccd]
aws_instance.logger: Still creating... [5m11s elapsed]
aws_instance.logger: Still creating... [5m21s elapsed]
aws_instance.logger: Still creating... [5m31s elapsed]
aws_instance.logger: Still creating... [5m41s elapsed]
aws_instance.logger: Still creating... [5m51s elapsed]
aws_instance.logger: Still creating... [6m1s elapsed]
aws_instance.logger: Still creating... [6m11s elapsed]
aws_instance.logger: Still creating... [6m21s elapsed]
aws_instance.logger: Still creating... [6m31s elapsed]
aws_instance.logger: Still creating... [6m41s elapsed]
aws_instance.logger: Still creating... [6m51s elapsed]
aws_instance.logger: Still creating... [7m1s elapsed]
    continues like this 

I have stopped the installation and run "destroy" then "apply" again with the same results. I am in us-west-1 and the other machines appear to have deployed successfully.

Closing comment (2021-02-15T23:45:04Z): Closing as this is a dupe of #604