On prem installation errors (both AWS stack and manual approach)

Vijay_Ram_H · May 8, 2023, 11:58am

I tried to install retool on my AWS account via the stack. It took a long time for the stack to run and finally it failed with this error "Failed to receive 1 resource signal(s) within the specified duration".

Then I resorted to launching an instance with same specs provided in the self hosting documenation. During the final stages while starting the docker containers the install script said there was an error and pointed me to a docker log. On opening that I found the following error:

WORKFLOW_TEMPORAL_WORKER_SHUTDOWN_GRACE_TIME: 11 minute
WORKFLOW_WORKER_HEALTHCHECK_PORT: 3005

{"message":"Rechecking license status...","level":"info","timestamp":"2023-05-08T10:13:45.099Z"}
Encountered error
TypeError: Cannot read properties of null (reading 'getUsers')
at checkLicenseStatus (/snapshot/retool_development/backend/transpiled/server/modules/licensing.js)
at async startOnPremServer (/snapshot/retool_development/backend/transpiled/server/main.js)
at async main (/snapshot/retool_development/backend/transpiled/server/main.js)
Exiting...

Need some help to sort either of the approaches. Thanks.

Vijay_Ram_H · May 8, 2023, 11:59am

Adding the final status of the docker ps command.

root@ip-172-31-5-71:~/retool/retool-onpremise# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
73fb898365f1 retool-onpremise-jobs-runner "docker-entrypoint.s…" 2 hours ago Up 2 hours 3000-3002/tcp retool-onpremise-jobs-runner-1
1d9a6eb6bdc6 postgres:9.6.5 "docker-entrypoint.s…" 2 hours ago Up 2 hours 5432/tcp retool-onpremise-postgres-1
d71e26449980 retool-onpremise-db-connector "docker-entrypoint.s…" 2 hours ago Up 2 hours 3000-3002/tcp retool-onpremise-db-connector-1
5a9b2f4d7181 retool-onpremise-db-ssh-connector "docker-entrypoint.s…" 2 hours ago Up 2 hours 3000-3002/tcp retool-onpremise-db-ssh-connector-1

I see the api container is not running.

Kabirdas · May 9, 2023, 4:28pm

Hey @Vijay_Ram_H!

This is an issue with the 2.117.2 release that the dev team has been looking into since yesterday. They recently pushed release 2.117.3 which should contain a fix, can you try reinstalling with that version and let me know if you're successful?

Vijay_Ram_H · May 10, 2023, 5:34am

This error has gone away. But still the install fails. See the logs below:

-- !! RETOOL IS BOOTING !! --

Waiting for Retool to start up... ****There was an issue starting the Retool container

You can view the logs by running: docker logs c704977b2a189fb7913ea389e81e64529be2b74fbffecad1fd8c72540c83f8e4')

CONTENT OF THE DOCKER LOG

root@ip-172-31-7-222:~# docker logs c704977b2a189fb7913ea389e81e64529be2b74fbffecad1fd8c72540c83f8e4

wait-for-it.sh: waiting 15 seconds for postgres:5432

wait-for-it.sh: postgres:5432 is available after 6 seconds

not untarring the bundle

{"message":"[process service types] MAIN_BACKEND","level":"info","timestamp":"2023-05-10T05:22:41.978Z"}

There are 409 pending database migrations, checking for up-to-date schema in 1 second(s)...

There are 409 pending database migrations, checking for up-to-date schema in 1 second(s)...
...... (same lines as before)

DOCKER PS OUTPUT:
root@ip-172-31-7-222:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c704977b2a18 retool-onpremise-api "docker-entrypoint.s…" 4 minutes ago Up 4 minutes 0.0.0.0:3000->3000/tcp, :::3000->3000/tcp, 3001-3002/tcp retool-onpremise-api-1
e38c3d2e9e75 postgres:9.6.5 "docker-entrypoint.s…" 4 minutes ago Up 4 minutes 5432/tcp retool-onpremise-postgres-1
0bacc235373d retool-onpremise-db-connector "docker-entrypoint.s…" 4 minutes ago Up 4 minutes 3000-3002/tcp retool-onpremise-db-connector-1
abc2b0eaf145 retool-onpremise-db-ssh-connector "docker-entrypoint.s…" 4 minutes ago Up 4 minutes 3000-3002/tcp retool-onpremise-db-ssh-connector-1

root@ip-172-31-7-222:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e38c3d2e9e75 postgres:9.6.5 "docker-entrypoint.s…" 7 minutes ago Up 7 minutes 5432/tcp retool-onpremise-postgres-1
0bacc235373d retool-onpremise-db-connector "docker-entrypoint.s…" 7 minutes ago Up 7 minutes 3000-3002/tcp retool-onpremise-db-connector-1
abc2b0eaf145 retool-onpremise-db-ssh-connector "docker-entrypoint.s…" 7 minutes ago Up 7 minutes 3000-3002/tcp retool-onpremise-db-ssh-connector-1

Kabirdas · May 11, 2023, 2:35am

Not sure exactly what's going on here can you try running curl http://localhost:3000/api/checkHealth from the command line of your AWS instance? The There was an issue starting the Retool container error might indicate that a curl request to that endpoint is failing, I'm curious to see the response you get.

Vijay_Ram_H · May 11, 2023, 5:43am

Ok I suspected if t2.medium with 4GB RAM wasn't sufficient and tried to run it with a larger instance and the install went through. Also may be 3000 port wasn't added to the security group earlier and I did that manually this time. One of these 2 or both must have worked. I got the instance to run.

BTW, yesterday the launch stack still didn't work. Not sure if that was fixed. But I didn't try that option and went only manual.

I have now other application errors and will post them in other relevant threads. Thanks for your help so far on this.

Kabirdas · May 11, 2023, 4:55pm

Ok, thanks for sharing what's moved you along and surfacing the error with the stack launch.