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
Infinite loop in backend? #223
Comments
In this issue it looks like it might be memory related: benoitc/gunicorn#1663 |
Thanks for your answer. The behaviour is the same with one worker. I have 8 GB of RAM. |
@alexislefebvre you are not the only one with this bug... some others reported it through discord... let see if @derneuere can do some magic here to solve it ;) |
The CPU of my server is “Intel(R) Celeron(R) CPU 1037U @ 1.80GHz”. It doesn't support AVX. |
See also LibrePhotos/librephotos-docker#7 |
With the last update, with this fix: docker-compose logs --tail 20 --follow backend
Attaching to librephotos-ayu_backend_1
backend_1 | statd: unrecognized service
backend_1 | /entrypoint.sh: line 10: 48 Illegal instruction (core dumped) python manage.py clear_cache
backend_1 | Running backend server...
backend_1 | production backend starting
backend_1 | [2021-04-15 18:28:28 +0000] [63] [INFO] Starting gunicorn 20.1.0
backend_1 | [2021-04-15 18:28:28 +0000] [63] [INFO] Listening at: http://172.23.0.4:8001 (63)
backend_1 | [2021-04-15 18:28:28 +0000] [63] [INFO] Using worker: gevent
backend_1 | [2021-04-15 18:28:28 +0000] [67] [INFO] Booting worker with pid: 67
backend_1 | [2021-04-15 18:28:39 +0000] [63] [WARNING] Worker with pid 67 was terminated due to signal 4
backend_1 | [2021-04-15 18:28:39 +0000] [76] [INFO] Booting worker with pid: 76
backend_1 | [2021-04-15 18:28:46 +0000] [63] [WARNING] Worker with pid 76 was terminated due to signal 4
backend_1 | [2021-04-15 18:28:46 +0000] [81] [INFO] Booting worker with pid: 81
backend_1 | [2021-04-15 18:28:54 +0000] [63] [WARNING] Worker with pid 81 was terminated due to signal 4
backend_1 | [2021-04-15 18:28:54 +0000] [86] [INFO] Booting worker with pid: 86
backend_1 | [2021-04-15 18:29:01 +0000] [63] [WARNING] Worker with pid 86 was terminated due to signal 4
backend_1 | [2021-04-15 18:29:01 +0000] [91] [INFO] Booting worker with pid: 91 And so on. |
The last update did not work for me (same error as before). |
@deliantwo Could you upload your backend image to dockerhub? Just to check if it resolves @alexislefebvre problems too. |
eager to test too! or tell me how to rebuild the backend docker image |
@darrepac you can try this: # 2. Build images on your own machine:
# build cmd: COMPOSE_DOCKER_CLI_BUILD=1 DOCKER_BUILDKIT=1 docker-compose build
# run cmd: docker-compose up -d |
I must be missing something: $ export COMPOSE_DOCKER_CLI_BUILD=1 DOCKER_BUILDKIT=1 ; docker-compose build
db uses an image, skipping
backend uses an image, skipping
frontend uses an image, skipping
proxy uses an image, skipping
redis uses an image, skipping
WARNING: Native build is an experimental feature and could change at any time
$ docker-compose -v
docker-compose version 1.25.0, build 0a186604 |
The |
Sure, no problem. I'm pushing it right now but I'm on a slow network and it's 4.32GB... have faith 😄 |
Sorry for the noob question but what do I have to put in yml file to use your image instead of the current one? |
@darrepac Just change the backend image repository. I've pushed the same tag dev, so no additional change is needed @@ -39,7 +39,7 @@
- backend
backend:
- image: reallibrephotos/librephotos:${tag}
+ image: delian2/librephotos:${tag}
restart: always
volumes:
- ${myPhotos}:/data |
Thanks a lot @deliantwo, it works! 🎉 |
All right, I will write a tutorial on how to build the backend image yourself for users who use CPUs without AVX support. |
@deliantwo well done, solve the problem on my side too |
Wrote docs about it: https://docs.librephotos.com/1/old_processors/ |
@deliantwo do you plan to maintain the image or not? thx |
…norepo Update dependency @babel/eslint-parser to v7.22.9
🐛 Bug Report
What Operating system and version is LibrePhotos running on:
Debian, last Docker release.
What architecture is LibrePhotos running on:
x64
How is LibrePhotos installed:
Docker
If running via Docker or Kubernets please list version including docker-compose:
Click to expand!
The difference with default conf is
- ${myPhotos}:/data:ro
, my filed are mounted on a read-only mount point.Are you running LibrePhotos on a virtual machine if so please list:
How is you picture library mounted on the host (or in the virtual machine):
Local file system (ext4)
Description of issue:
My CPU has too much usage, I have to stop LibrePhotos.
How can we reproduce it:
I don't know.
Additional Information:
The text was updated successfully, but these errors were encountered: