Retool Workflow Worker constantly restart with self-host temporal

Self Hosted Retool
1

Hi Retool Community,

I'm currently trying to setup a self-host temporal to work with the workflow.

I used the docker-compose-with-temporal.yml as the startpoint. After starting all containers, i can:

  • access self-host Retool without issue (except the Workflow)
  • access self-host Temporal UI without issue

However, the workflow is still not working and ask me to 'upgrade deployment'. What I can see on the docker is the Workflow Worker is constantly restarting. So I guess the issue is restricted on Workflow component.

here's the error I received:

2024-05-31 17:08:19 wait-for-it.sh: waiting 15 seconds for postgres:5432
2024-05-31 17:08:19 wait-for-it.sh: postgres:5432 is available after 0 seconds
2024-05-31 17:08:19 sed: can't read ./dist/mobile/*.js: No such file or directory
2024-05-31 17:08:21 (node:22) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.
2024-05-31 17:08:21 
2024-05-31 17:08:21 Please migrate your code to use AWS SDK for JavaScript (v3).
2024-05-31 17:08:21 For more information, check the migration guide at https://a.co/7PzMCcy
2024-05-31 17:08:21 (Use `node --trace-warnings ...` to show where the warning was created)
2024-05-31 17:08:22 {"level":"info","message":"license check http response code: 200","timestamp":"2024-06-01T00:08:22.226Z"}
2024-05-31 17:08:22 {"level":"info","message":"License key feature flag overrides: {}","timestamp":"2024-06-01T00:08:22.228Z"}
2024-05-31 17:08:22 {"level":"info","message":"Updated license status from licensing server","timestamp":"2024-06-01T00:08:22.232Z"}
2024-05-31 17:08:22 (node:22) [DEP0111] DeprecationWarning: Access to process.binding('http_parser') is deprecated.
2024-05-31 17:08:22 {"level":"info","message":"creating temporal worker connection","timestamp":"2024-06-01T00:08:22.532Z"}
2024-05-31 17:08:22 /node_modules/@temporalio/worker/lib/connection.js:55
2024-05-31 17:08:22                 throw new core_bridge_1.TransportError(err.message);
2024-05-31 17:08:22                       ^
2024-05-31 17:08:22 
2024-05-31 17:08:22 TransportError: tonic::transport::Error(Transport, hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })))
2024-05-31 17:08:22     at NativeConnection.connect (/node_modules/@temporalio/worker/lib/connection.js:55:23)
2024-05-31 17:08:22     at async Xx (/retool_backend/bundle/main.js:3942:12843)
2024-05-31 17:08:22     at async rEe (/retool_backend/bundle/main.js:4362:8671)
2024-05-31 17:08:22     at async Object.k53 (/retool_backend/bundle/main.js:4362:9994)
2024-05-31 17:08:22 
2024-05-31 17:08:22 Node.js v18.18.2

The self-host retool version I'm currently on is: 3.33.31-stable

Can anyone assist me on this?

1 Like
2

hey @zelterNN i'm spinning up using the steps you provided and will report back in a minute

1 Like
3

@zelterNN hmm... I wasn't able to reproduce, my workflow container stays started. I zipped up my retool on-prem folder, if you try it out, do you get the same issue?

4

Hi @trz-justin-dev,
Thanks for testing on your side. I can test your setup folder on Monday when I get back to the office.

Mine is actually to be able to start all containers initially (all shows running without issue) but

  • click on Workflow tab, the self-host Retool still asks me to 'upgrade deployment'. This is the same situation when I deploy without temporal.
  • after a while (serveral mins) since initiating all containers, the Workflow Worker container starts to exit-restarting-running-exit-restarting-running-.... cycle and shows the error on the console repetitively as in my original post

Can you confirm if you are able to use the Workflow on your self-host Retool (on temporal instead of on playground mode)?

5

Just tried your folder....not in luck :frowning:

6

Okay.....I found the issue, I accidentally use the temporalio/auto-setup:1.23.1 when I tried to solve another issue

After I switch it back to tryretool/one-offs:retool-temporal-1.1.2, the worker runs without issue and I'm now able to use Workflow in self host.

2 Likes