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
WORKER TIMEOUT on application start in AWS EC2 instance #36
Comments
Same problem here. Did you get with a solution? |
@cucomans no, didn't find a workround and went with an alternate solution (which didn't include phash). |
It was working fine untill last monday and then boom this error started to occurr. |
I had the same problem, from the logs I was getting the following: Following this stackoverflow i did the following: edit ran |
Hello,
We have been trying to set up an instance of the application on an AWS EC2 instance. Everything seems to be setup correctly; EC2 instance is running, we can telnet to the ports, attached volume is OK, and AWS Elasticsearch instance appears accessible and running. When we hit the /ping URL it times out. And looking at the docker logs we can see the below messages:
[2018-12-04 16:50:33 +0000] [1946] [INFO] Booting worker with pid: 1946
[2018-12-04 16:50:33 +0000] [1947] [INFO] Booting worker with pid: 1947
[2018-12-04 16:50:33 +0000] [1950] [INFO] Booting worker with pid: 1950
[2018-12-04 16:50:33 +0000] [1954] [INFO] Booting worker with pid: 1954
[2018-12-04 16:51:33 +0000] [6] [CRITICAL] WORKER TIMEOUT (pid:1946)
[2018-12-04 16:51:33 +0000] [1946] [INFO] Worker exiting (pid: 1946)
[2018-12-04 16:51:33 +0000] [6] [CRITICAL] WORKER TIMEOUT (pid:1947)
[2018-12-04 16:51:33 +0000] [6] [CRITICAL] WORKER TIMEOUT (pid:1950)
[2018-12-04 16:51:33 +0000] [6] [CRITICAL] WORKER TIMEOUT (pid:1954)
[2018-12-04 16:51:33 +0000] [1954] [INFO] Worker exiting (pid: 1954)
[2018-12-04 16:51:33 +0000] [1947] [INFO] Worker exiting (pid: 1947)
[2018-12-04 16:51:33 +0000] [1950] [INFO] Worker exiting (pid: 1950)
We have ruled out memory and cache issues and tried using different versions. The issue appears to originate from the dsys/match image. Does anybody know what our issue is?
AMI: ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20180912 (ami-07a3bd4944eb120a0)
EC2 instance type: t2.medium
Elastic Search version: 6.3
Thanks
The text was updated successfully, but these errors were encountered: