bazarr
bazarr copied to clipboard
morpheus65535
WebUI seems to randomly crash?
Describe the bug After running for a while, the WebUI will become inaccessible, however, the container will still be running. If I restart the container, the UI will become accessible again. Nothing particularly of interest shows in the logs when the issue is present so it's hard to track.
To Reproduce Not sure how.
Software (please complete the following information):
- Bazarr: 1.4.3-beta.24
- Radarr version 5.4.6.8723
- Sonarr version 4.0.4.1491
- OS: Docker
Side note: Adjust the position of the activity popup because it covers up page navigation
bazarrui.log Just caught it doing it again so here's the last 150 lines from Docker logs. It appears that nothing functions anymore once it happens. If there isn't enough evidence, I can send a longer log.
This logs only tell me that a subtitles downloaded from animetosho encoding wasn't guessed properly. I think we'll need a longer log...
@PassiveLemon What do you mean the web ui becomes inaccessible? Do you get like refused to connect error from browser? Also do you still get logs while the WebUI is inaccessible?
I suspect that the node process died. But the backend still running?
I get Firefoxes "Hmm. We're having trouble finding that site." error, not sure exactly type of error it is lol. And no, I do not seem to get any more logs once it happens.
Doing some maintenance today on all my bazarr setup, disk mappings etc. Third time now in an hour where UI crashes and cant reach backend. So there seem to be an issue for sure.
Just for testing purpose, what happen if you disable animetosho provider for a while?
Perhaps @flensburg2 can also provide some logs?
https://github.com/morpheus65535/bazarr/issues/2470#issuecomment-2076137237
Just for testing purpose, what happen if you disable animetosho provider for a while?
Never had animetosho enabled.
I saw PassiveLemon logs i was wondering if they have different behaviors and if they are both using animetosho?
I saw PassiveLemon logs i was wondering if they have different behaviors and if they are both using animetosho?
My bad, sorry. It's still early here ;)
Never had animetosho enabled.
This message was for @PassiveLemon .
@flensburg2 can you provide debug logs?
I removed the animetosho provider and AniDB integration and I have yet to see it happen. I'll give it overnight before I say with confidence though.
It's been way more than one night and no problems so far. I guess it can be reasonably assumed that the animetosho provider or AniDB integration is a culprit
@flensburg2 still waiting for your logs.
@PassiveLemon thanks for checking that.
@anderson-oki are you able to look into this?
The animetosho encoding issue is a separated issue and i can for sure reproduce but doesnt break anything else. I will be looking to fix that but it seems unrelated?
I have been running the docker version with an uptime of 32 hours fully using anidb and animetosho and i cant find anything that can be causing it. I will keep looking into it but im not sure if i can spot the root cause soon without more details.
@morpheus65535 can we ask to try the beta 26 since it fixes some exceptions? My guess in the worst case the exceptions are accumulating some garbage that kills it fixed on the beta 26. Or maybe Docker disk space for the cache?
@morpheus65535 can we ask to try the beta 26 since it fixes some exceptions? My guess in the worst case the exceptions are accumulating some garbage that kills it fixed on the beta 26. Or maybe Docker disk space for the cache?
Of course we can ask @PassiveLemon to test latest beta. Can you also provide docker-compose just in case we see something?
Heres my docker-compose:
bazarr:
image: lscr.io/linuxserver/bazarr:development-version-v1.4.3-beta.24
container_name: bazarr
restart: always
volumes:
- /home/docker/Containers/Media/Bazarr/config/:/config/:rw
- /home/HDD2TBEXT4/Media/:/data/:rw
environment:
TZ: "${TZ}"
PUID: "${PUID}"
PGID: "${PGID}"
ports:
- 55367:6767/tcp
networks:
torrent:
deploy:
resources:
limits:
cpus: "1"
memory: 300M
I'm going to bump it to beta 26, renable animetosho/anidb and let it run over night and see if anything happens
Thanks @PassiveLemon, please re-send the logs of the version 26 if the breaks again 🙇🏻 And tell us around what is the time that you noticed it stopped working.
Limiting Bazarr to 300M of memory is probably the root cause. Depending of what feature you use, it may require more memory than that. Subtitles synchronization could use over a gigabyte of memory depending of audio track format.
I can reproduce the issue lowering the memory. The /lsiopy/bin/python3 -u /app/bazarr/bin/bazarr/main.py --no-update --config /config gets killed on kernel level by out of memory.
Hm i didn't even think of that. Usually if i have memory problems, in other containers, they just become much slower but I've never had crashes before. I'll increase it.
Edit: Just checked my instance and it's still running.
So everything seems to be good now. I'll close this issue but let me know if you experience it again.
@PassiveLemon Let me ask a couple more questions and ask you to try something:
1 - Does it happen on a specific time every time? Like more specifically on the time it is set on the Settings > Scheduler?
2 - Can you try to open System > Tasks and run some tasks like Index All Movie , or maybe the other tasks as well.
Can you see if while doing the 2 it crashes? Or maybe monitor the memory usage while running the tasks?
Looking at where the logs end (4:02 AM), it seems like either the search for missing movie or series subtitles is at least partially responsible. I also never saw it go above 300 MB, although I can't confirm that for the entire night as I wasn't watching it then. The issue is that I ran it last night and it didn't crash. I'm running it again to confirm though.
Edit: Ran movie and series scan and did not have a problem.