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

Docker Container is unhealthy on my Synology NAS (but appears to work) - can this be fixed? #80

Open
cleverestx opened this issue Apr 9, 2024 · 7 comments
Assignees
Labels
backend bug Something isn't working docker Docker config related help wanted Extra attention is needed usability

Comments

@cleverestx
Copy link

Concerned about a memory leak or other issues though. How do I fix this?

image

[2024-04-09 03:37:48 +0000] [32272] [INFO] Booting worker with pid: 32272

[2024-04-09 03:37:52 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:32271)

[2024-04-09 03:37:52 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:32272)

[2024-04-09 03:37:53 +0000] [1] [ERROR] Worker (pid:32271) was sent SIGKILL! Perhaps out of memory?

[2024-04-09 03:37:54 +0000] [1] [ERROR] Worker (pid:32272) was sent SIGKILL! Perhaps out of memory?

[2024-04-09 03:37:55 +0000] [32282] [INFO] Booting worker with pid: 32282

[2024-04-09 03:37:55 +0000] [32283] [INFO] Booting worker with pid: 32283

[2024-04-09 03:37:59 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:32282)

[2024-04-09 03:37:59 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:32283)

[2024-04-09 03:38:00 +0000] [1] [ERROR] Worker (pid:32282) was sent SIGKILL! Perhaps out of memory?

[2024-04-09 03:38:00 +0000] [1] [ERROR] Worker (pid:32283) was sent SIGKILL! Perhaps out of memory?

[2024-04-09 03:38:00 +0000] [32284] [INFO] Booting worker with pid: 32284

[2024-04-09 03:38:02 +0000] [32285] [INFO] Booting worker with pid: 32285

[2024-04-09 03:38:04 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:32284)

[2024-04-09 03:38:05 +0000] [1] [ERROR] Worker (pid:32284) was sent SIGKILL! Perhaps out of memory?

[2024-04-09 03:38:05 +0000] [32286] [INFO] Booting worker with pid: 32286

[2024-04-09 03:38:06 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:32285)

[2024-04-09 03:38:07 +0000] [1] [ERROR] Worker (pid:32285) was sent SIGKILL! Perhaps out of memory?

[2024-04-09 03:38:07 +0000] [32287] [INFO] Booting worker with pid: 32287

[2024-04-09 03:38:09 +0000] [32286] [INFO] Started server process [32286]

[2024-04-09 03:38:09 +0000] [32287] [INFO] Started server process [32287]

[2024-04-09 03:38:09 +0000] [32287] [INFO] Waiting for application startup.

[2024-04-09 03:38:09 +0000] [32286] [INFO] Waiting for application startup.

[2024-04-09 03:38:09 +0000] [32286] [INFO] ASGI 'lifespan' protocol appears unsupported.

[2024-04-09 03:38:09 +0000] [32287] [INFO] ASGI 'lifespan' protocol appears unsupported.

[2024-04-09 03:38:09 +0000] [32286] [INFO] Application startup complete.

[2024-04-09 03:38:09 +0000] [32287] [INFO] Application startup complete.

[2024-04-09 03:54:13 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:32286)

[2024-04-09 03:54:18 +0000] [1] [ERROR] Worker (pid:32286) was sent SIGKILL! Perhaps out of memory?

[2024-04-09 03:54:20 +0000] [32529] [INFO] Booting worker with pid: 32529

[2024-04-09 03:54:24 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:32529)

[2024-04-09 03:54:25 +0000] [1] [ERROR] Worker (pid:32529) was sent SIGKILL! Perhaps out of memory?

[2024-04-09 03:54:25 +0000] [32530] [INFO] Booting worker with pid: 32530

[2024-04-09 03:54:29 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:32530)

[2024-04-09 03:54:29 +0000] [1] [ERROR] Worker (pid:32530) was sent code 134!

[2024-04-09 03:54:29 +0000] [32531] [INFO] Booting worker with pid: 32531

[2024-04-09 03:54:33 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:32531)

[2024-04-09 03:54:34 +0000] [1] [ERROR] Worker (pid:32531) was sent code 134!

[2024-04-09 03:54:34 +0000] [32532] [INFO] Booting worker with pid: 32532

[2024-04-09 03:54:38 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:32532)

[2024-04-09 03:54:38 +0000] [1] [ERROR] Worker (pid:32532) was sent code 134!

[2024-04-09 03:54:38 +0000] [32533] [INFO] Booting worker with pid: 32533

[2024-04-09 03:54:42 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:32533)

[2024-04-09 03:54:43 +0000] [1] [ERROR] Worker (pid:32533) was sent SIGKILL! Perhaps out of memory?

[2024-04-09 03:54:43 +0000] [32534] [INFO] Booting worker with pid: 32534

[2024-04-09 03:54:46 +0000] [32534] [INFO] Started server process [32534]

[2024-04-09 03:54:46 +0000] [32534] [INFO] Waiting for application startup.

[2024-04-09 03:54:46 +0000] [32534] [INFO] ASGI 'lifespan' protocol appears unsupported.

[2024-04-09 03:54:46 +0000] [32534] [INFO] Application startup complete.

Desktop (please complete the following information):

  • Synology DS1621+ NAS (DSM 7)
@cleverestx cleverestx added the bug Something isn't working label Apr 9, 2024
@jocxfin jocxfin added usability docker Docker config related backend labels Apr 9, 2024
@jocxfin
Copy link
Owner

jocxfin commented Apr 9, 2024

Hi! Thanks for reporting this. I'll take a look and come back to you if I have any questions.

@jocxfin
Copy link
Owner

jocxfin commented Apr 9, 2024

@cleverestx There seems not to be any memory leaking as far as i have checked.
How much of memory is free on your system? Could it be that your system is running our of reserved memory?
Seems like your synology should have 4gb of ram. I tried to overload the memory by opening 100 sessions of the application without caching and it never went over 200MB and i never saw any issues you have.

This is the pwgen.joonatanh.com docker and even with approximately 200 unique users per day, there is absolutely no issues with the memory:

image

@cleverestx
Copy link
Author

cleverestx commented Apr 9, 2024 via email

@jocxfin jocxfin added the help wanted Extra attention is needed label Apr 9, 2024
@jocxfin
Copy link
Owner

jocxfin commented Apr 9, 2024

I actually took some time and tried to research this issue. As I double checked, there should not be any memory leaking even after long time. Only thing I found, was a Synology update causing a general memory leakage, but this happened in 2021 and they fixed that with an update. But they said that if users are still having issues with memory leaks, removing the container and re-deploying it should stop that. So maybe give that a go? I also thought maybe it's due to the amount of workers present (by default 2 and 4 threads) so I'll make a dev build soon where there will be the possibility to use the envs WORKERS and THREADS for defining them.

Edit: my bad, apparently i already had made the change and it should be available in jocxfin/pwgen-dev if you want to test. Just add new envs for WORKERS=1 and THREADS=2

@cleverestx
Copy link
Author

Thank you! I will check it out soon!

@cleverestx
Copy link
Author

The DEV PWgen works, same as before, but once again Portainer shows unhealthy, and I get this:

image

@hammaschlach
Copy link

I have the exact same problem on my synology with 20GB.

SCR-20240426-gxid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend bug Something isn't working docker Docker config related help wanted Extra attention is needed usability
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

3 participants