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

After installation, WORKER TIMEOUT web does not open, in the logs #62

Closed
suharevA opened this issue Apr 3, 2024 · 11 comments
Closed

After installation, WORKER TIMEOUT web does not open, in the logs #62

suharevA opened this issue Apr 3, 2024 · 11 comments

Comments

@suharevA
Copy link

suharevA commented Apr 3, 2024

Installed according to the instructions
after installation the container with

NAME="Ubuntu"
VERSION_ID="22.04"

docker logs redash-server-1

[2024-04-03 13:14:02 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:16)
[2024-04-03 13:14:02 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:17)
[2024-04-03 13:14:02 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:18)
[2024-04-03 13:14:02 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:19)
[2024-04-03 13:14:02 +0000] [16] [INFO] Worker exiting (pid: 16)
[2024-04-03 13:14:02 +0000] [17] [INFO] Worker exiting (pid: 17)
[2024-04-03 13:14:02 +0000] [18] [INFO] Worker exiting (pid: 18)
[2024-04-03 13:14:02 +0000] [19] [INFO] Worker exiting (pid: 19)
[2024-04-03 13:14:03 +0000] [20] [INFO] Booting worker with pid: 20
[2024-04-03 13:14:03 +0000] [21] [INFO] Booting worker with pid: 21
[2024-04-03 13:14:03 +0000] [22] [INFO] Booting worker with pid: 22
[2024-04-03 13:14:03 +0000] [23] [INFO] Booting worker with pid: 23
@suharevA suharevA changed the title After installation, WORKER TIMEOUT web does not open in the logs After installation, WORKER TIMEOUT web does not open, in the logs Apr 3, 2024
@justinclift
Copy link
Member

Oh, that's not good. How much ram and how many cpu cores is the system you're trying it on?

@justinclift
Copy link
Member

As a general thought, you probably want to be using a system with 8GB of ram. I've seen it "technically" start up with less (eg 6GB), but it was already paging out to swap with that.

@suharevA
Copy link
Author

suharevA commented Apr 3, 2024

minimum 2cpu 4gb. I will try to add resources

@justinclift
Copy link
Member

Yeah, that's probably the reason for the timeout. 😄

@justinclift
Copy link
Member

@suharevA How did it go? 😄

@suharevA
Copy link
Author

suharevA commented Apr 4, 2024

Thank you.
macbook air with virtual machine in UTM did not work no matter how many resources I added.
hp laptop with ubuntu and virt-manager virtualisation worked even with minimal resources

@justinclift
Copy link
Member

Interesting. Sounds like something weird with UTM then. 😦

At least you got it working though. 😄

Is it ok with you for this issue to be closed?

@nezirz
Copy link

nezirz commented Apr 30, 2024

Tried to use it on Digital Ocean ubuntu v22.04 with 1gb ram and had that issue later created new droplet with 2gb ram and still showing those workers issues...

@justinclift
Copy link
Member

@nezirz Try with 8GB of ram and see how you go. If that works ok, then you can try reducing the memory from there to a level you're happy with.

But, go with 8GB as the starting point as that should work. 😄

@evalencia-ss
Copy link

Im on a vmware using ubuntu 24.04 with 4GB ram and 1 CPU and its working fine.

@justinclift
Copy link
Member

Closing this as it sounds like the standard problem of not allocating enough resources, and several people have pointed out how to fix things. 😄

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

4 participants