Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GOAD LAB Setup - Common Errors #231

Open
Moorocks opened this issue May 6, 2024 · 1 comment
Open

GOAD LAB Setup - Common Errors #231

Moorocks opened this issue May 6, 2024 · 1 comment

Comments

@Moorocks
Copy link

Moorocks commented May 6, 2024

This is a quick walkthrough about the errors we might see while setting up the GOAD template.

I installed GOAD directly from Windows host instead of Ubuntu.

As described on the Github pages, “the lab is intended to be installed from a Linux host”, but it is still possible to successfully install the lab from a Windows host. I did not want to install the lab in ubuntu as it makes the performance of the windows server so slow as it results in nested virtualisation.

**** DO NOT TRY TO DEPLOY GOAD TEMPLATE IN ORACLE VIRTUALBOX FROM WINDOWS HOST as I faced lot of errors while running ansible scripts ****

$$$$ INSTALL GOAD VIA VMWARE WORKSTATION PRO AS IT MAKES YOUR LIFE EASY $$$$

Goad installation Command : ./goad.sh -t install -l GOAD vmware -m local -a (This command will run all the ansible playbooks and there would no need to run the playbooks individually)
image

Error 1 : vagrant unable to find vmware provider

Sol 1 : This occurs when you do not have vagrant plugin for vmware installed. Install it from the below link and update it.
https://developer.hashicorp.com/vagrant/docs/providers/vmware/installation

Github link for same error: hashicorp/vagrant#9444

Error 2 : Unreachable Error

Sol 2: You get this error when the ip's allocated to the servers do not match the ip's within the inventory file or if you might need to check virtual network editor in VMWARE Workstation PRO (check VMNET1 and VMNET8 configuration) .
When you deploy all the Windows servers, try to login with creds (uname - Vagrant and pass - vagrant) and check the ip. Do the same for all machines and once done, modify the inventory file with the allocated ip's. Inventory file is found under /GOAD/ad/GOAD/providers/vmware/. Do nano inventory and try to modify the ip's. If the ip's are unchanged, then you will still face the error repeatedly.

My subnet is 192.168.112.0/24 and as you can see the below image, all my windows servers are under the same subnet.
image

Virtual Network Editor Configuration:
image

Error 3: SRV02 machine failing to install SQL Service causing servers playbook to fail.

Sol 3 : Check your server status if you are getting this error. In my case, I observed that my server was restarting and as a result my ansible playbook (servers.yml) was throwing error. After restart, I ran my ansible script again and it worked.

Error Screenshot:

image

Overall this process takes around 1-4 hrs to complete, BE PATIENT DURING INSTALLATION*.

After installation, you get the below output:
image

@BinaryExecutioner
Copy link

Popped up with this error, can someone please help?
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants