You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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.
Virtual Network Editor Configuration:
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:
Overall this process takes around 1-4 hrs to complete, BE PATIENT DURING INSTALLATION*.
After installation, you get the below output:
The text was updated successfully, but these errors were encountered:
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)
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.
Virtual Network Editor Configuration:
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:
Overall this process takes around 1-4 hrs to complete, BE PATIENT DURING INSTALLATION*.
After installation, you get the below output:
The text was updated successfully, but these errors were encountered: