search

UiPath / Infrastructure

42 stars 61 forks source link

The AWs deployments do not work #22

Closed picoroma closed 4 years ago

picoroma commented 4 years ago

After the "terraform apply" has finished, the Orchestrator EC2 machine, have no Orchestrator installed on it.

Havin a look into the logs - seems the was not possible to download the Orchestrator Installer from server. How can I solve ? THX

picoroma commented 4 years ago

The problem seems to be with the "orchestrator_version" in the script is 19.4.4 - that is not available

hteo1337 commented 4 years ago

Hello. The 19.4.4 version is available. Please check here : https://download.uipath.com/versions/19.4.4/UiPathOrchestrator.msi. Can you see if you have internet on the ASG group? Also if the NAT Gateway was deployed ?

picoroma commented 4 years ago

I still have error. The Terraform deploy response was (12 resources created). I attache the logs I found into C:\temp [UiPath-AWS-Install-Log.zip] I have another dubt related to the variable "orchestrator_license" What I have to put here ? Consider I want to install a TRIAL version. It's OK to insert the trial code I received from UiPath?

hteo1337 commented 4 years ago

Hello. Can you check from the VM created if you have connection to the DB? I checked your logs and it's downloading your client, trying to install but you get an error : MSI (s) (7C:9C) [09:32:40:219]: Note: 1: 1708 MSI (s) (7C:9C) [09:32:40:219]: Product: UiPath Orchestrator -- Installation failed.

Also if you are on the VM , check event viewer if it's the DB.

regarding orchestrator_license you can let it blank and manually add the license.

In conclusion, Orchestrator package is installed but gets rolled back due to one resource missing, Can you confirm you are using Win Server 2019?

picoroma commented 4 years ago

Orchestrator VM is deployed by Terraform on Windows server 2016 (NOT 2019!) The SG was created and seems to be OK Nat GW - WAS NOT Created. bUT THERE IS AN internet gw CORRECTLY CREATED. The RDS endpoint is reachable from Orchestrator. I tested with telnet on port 1433 Regards

hteo1337 commented 4 years ago

Ok, try on 2019. The problem is on 2016 as Orchestrator require last .net framework and if you manage to install it, still needs the reboot so the Orchestrator setup will revert back. Try with 2019 or use an AMI image with last .net framework installed.

picoroma commented 4 years ago

THX.. BUt The OS version is not editable\changecle into Terraform Script (variable)... How can I change the OS version or the ami image ?

hteo1337 commented 4 years ago

Welcome.

On :data-template.tf modify : 

values = ["Windows_Server-2016-English-Full-Base-*"]

with : 

values = ["Windows_Server-2019-English-Full-Base-*"]

Now I get it, you are using the single node deployment template. This wasn;t updated for so long and we want to delete it, if this will be an production environment then use the multi node one (you can scale down to 1 node if you want).

I will try to update the single node plan.

picoroma commented 4 years ago

How can I install a Single Node Installation using the Multinode template ?

hteo1337 commented 4 years ago

Server Instances

The count of Orchestrator instances in the ASG

variable "instance_count"

Actually is set to 1, so will deploy just 1 instance. This plan will deploy : 1 Orchestrator in ASG group with FileGateway for S3 Bucket (here are hosted all nuget packages) and with HAA Orchestrator addon (which is 30 days trial by default). https://docs.uipath.com/orchestrator/docs/aws-deployment

picoroma commented 4 years ago

IN the meantime I have re-tested the single node installation, but still fails. Attach the log files. [UiPath-AWS-Install-Log_WIN2019.zip]

hteo1337 commented 4 years ago

Few things: -orchestratorLicenseCode TheLicenseCreatedwithRegUtil << do not use this parameter in line 19 from data-template.tf powershell.exe -ExecutionPolicy Bypass -File "C:\ProgramData\Amazon\EC2-Windows\Launch\Scripts\Install-UiPathOrchestrator.ps1" -OrchestratorVersion "${var.orchestrator_version}" -passphrase "${var.orchestrator_passphrase}" -databaseServerName "${aws_db_instance.default_mssql.address}" -databaseName "${var.db_name}" -databaseUserName "${var.db_username}" -databaseUserPassword "${var.db_password}" -orchestratorAdminPassword "${var.orchestrator_password}"

And the other thing : ValidateParameters error: The password does not contain any digit character. << Add at leat 1 digit char to the password (the parameter is orchestratorAdminPassword)

hteo1337 commented 4 years ago

The error (from the logs you've sent) is regarding the admin password for Orchestrator is too simple and doesn't contain any digit.

hteo1337 commented 4 years ago

Btw, when you manage to deploy successfully our solution...please redeploy it or at least change the passwords and db account as these are already attached to the logs you've sent. I've deleted the urls of your logs.

picoroma commented 4 years ago

With password more complex works! THX!

hteo1337 commented 4 years ago

Welcome. I will close this issue

picoroma commented 4 years ago

Hi Teo!

I have one question related to this DEPLOY (both single and multi node)

These deploy do not include the ElasticSearch\Kibana peace of the stack, I mean.

How can I add the ElastiSearch and Kibana ? Possibly using the ELK managed by AWS ?

THX

P.

Il 20-03-2020 10:39 HTeo ha scritto:

Closed #22 [1].

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [2], or unsubscribe [3].

Links:

[1] https://github.com/UiPath/Infrastructure/issues/22 [2] https://github.com/UiPath/Infrastructure/issues/22#event-3148610313 [3] https://github.com/notifications/unsubscribe-auth/AFUGI2FABWGEMJNS652QV7LRIM2VDANCNFSM4LPDJNPA

hteo1337 commented 4 years ago

Hi,

It’s true, these deploy plans don’t deploy the ELK stack and this is because the ELK stack is optional. The multimode deploys only the mandatory resources.

But, you can use the ELK stack, here is the doc:

https://docs.uipath.com/orchestrator/docs/prerequisites-for-installation#section-elasticsearch-server

Here it’s for webconfig : https://docs.uipath.com/orchestrator/docs/webconfig

Here it’s how to create the index pattern:

https://docs.uipath.com/orchestrator/docs/creating-an-index-pattern-to-connect-to-elasticsearch

From: PiCo notifications@github.com Sent: Friday, March 20, 2020 12:17 PM To: UiPath/Infrastructure Infrastructure@noreply.github.com Cc: HTeo hteo1337@gmail.com; State change state_change@noreply.github.com Subject: Re: [UiPath/Infrastructure] The AWs deployments do not work (#22)

Hi Teo!

I have one question related to this DEPLOY (both single and multi node)

These deploy do not include the ElasticSearch\Kibana peace of the stack, I mean.

How can I add the ElastiSearch and Kibana ? Possibly using the ELK managed by AWS ?

THX

P.

Il 20-03-2020 10:39 HTeo ha scritto:

Closed #22 [1].

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [2], or unsubscribe [3].

Links:

[1] https://github.com/UiPath/Infrastructure/issues/22 [2] https://github.com/UiPath/Infrastructure/issues/22#event-3148610313 [3] https://github.com/notifications/unsubscribe-auth/AFUGI2FABWGEMJNS652QV7LRIM2VDANCNFSM4LPDJNPA

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/UiPath/Infrastructure/issues/22#issuecomment-601624299 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AGH2HSZZ2M5EZ3FARRT7AA3RIM7AVANCNFSM4LPDJNPA . https://github.com/notifications/beacon/AGH2HSYJHZOSRZXFD6RXOZLRIM7AVA5CNFSM4LPDJNPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEPOA52Y.gif

-- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

picoroma commented 4 years ago

Thank you very much for your help.

I have deployed the SINGLE-NODE Installation now.

But the MULTI-NODE still gives me an error. The error seems to be related to some variable name that is not compliant (maybe use "-" or uppercase letter). I tried to change something but still haven't found the solution.

In addiction a Can say that with latest terraform (I'm using Terraform v0.12.23) the "plan" report some warning related to deprecated parameters.

(Let me know if you want this kind of feedback)

Regarding the Elasticsearch. Again thankyou for suggestion.

I just installed the ES as per your link.

After that I have create a new "empty" INDEX into ES ( PUT /uipath ) - But this index is not recognized by KIBANA.

Maybe because is still empty.

regarding the web.config - what is the minimal setup\changes I need to perform in order to works fine with ES ?

The documentation is not so clear.

THX

Il 20-03-2020 11:26 HTeo ha scritto:

Hi,

It's true, these deploy plans don't deploy the ELK stack and this is because the ELK stack is optional. The multimode deploys only the mandatory resources.

But, you can use the ELK stack, here is the doc:

https://docs.uipath.com/orchestrator/docs/prerequisites-for-installation#section-elasticsearch-server

Here it's for webconfig : https://docs.uipath.com/orchestrator/docs/webconfig

Here it's how to create the index pattern:

https://docs.uipath.com/orchestrator/docs/creating-an-index-pattern-to-connect-to-elasticsearch

From: PiCo notifications@github.com Sent: Friday, March 20, 2020 12:17 PM To: UiPath/Infrastructure Infrastructure@noreply.github.com Cc: HTeo hteo1337@gmail.com; State change state_change@noreply.github.com Subject: Re: [UiPath/Infrastructure] The AWs deployments do not work (#22)

Hi Teo!

I have one question related to this DEPLOY (both single and multi node)

These deploy do not include the ElasticSearch\Kibana peace of the stack, I mean.

How can I add the ElastiSearch and Kibana ? Possibly using the ELK managed by AWS ?

THX

P.

Il 20-03-2020 10:39 HTeo ha scritto:

Closed #22 [1].

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [2], or unsubscribe [3].

Links:

[1] https://github.com/UiPath/Infrastructure/issues/22 [2] https://github.com/UiPath/Infrastructure/issues/22#event-3148610313 [3] https://github.com/notifications/unsubscribe-auth/AFUGI2FABWGEMJNS652QV7LRIM2VDANCNFSM4LPDJNPA

-- You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/UiPath/Infrastructure/issues/22#issuecomment-601624299 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AGH2HSZZ2M5EZ3FARRT7AA3RIM7AVANCNFSM4LPDJNPA . https://github.com/notifications/beacon/AGH2HSYJHZOSRZXFD6RXOZLRIM7AVA5CNFSM4LPDJNPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEPOA52Y.gif

-- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2].

Links:

[1] https://github.com/UiPath/Infrastructure/issues/22#issuecomment-601628008 [2] https://github.com/notifications/unsubscribe-auth/AFUGI2CLXO6JCHOJITOSB5DRINAEDANCNFSM4LPDJNPA