automatic-ripping-machine: 🐛 Web UI Unresponsive During a Rip
Is there an existing issue for this?
- I have searched the existing issues
I have checked the wiki
- I have searched the wiki for this problem
Does this issue exist in the latest version?
- I’m using the latest release
Describe the bug?
Whilst ripping a few blu-ray, I noticed that the webUI becomes unresponsive and constantly spins like it is trying to load something. As soon as the blu-ray finishes and the disk is ejected, the application responds again and I can browse around.
I’ve used this tool before and not noticed the issue until after I upgraded my machine and reinstalled everything.
I’m wondering if the issue is possibly related to the amount of resources Docker has allocated (perhaps not enough CPU Cores). Think I perhaps just wondered if someone else may have had this issue before and a few things to possibly try.
I’ve linked off to some error logs I noticed.
To Reproduce
- I installed an older version through Docker initially (2.6.48).
- Then I upgraded to the most recent one once all the files for the container had been created in docker and on my host.
- When ripping a blu-ray, trying to access localhost:8080, the page never loads just constantly spins.
What OS are you seeing the problem on?
Other (please state in Anything else? section)
ARM Release Version or Git hash (You can find this in the arm settings page)
v2.6.69 Ubuntu 22.04
Expected behavior?
I should be able to see the UI and browse around whilst a Blu-ray is ripping.
Relevant log output
Jan 27 00:27:43 f13c2c498a39 ARM: [ARM] Entering docker wrapper
Jan 27 00:27:43 f13c2c498a39 ARM: Sat Jan 27 00:27:43 UTC 2024 [[ARM] Starting ARM for Bluray on sr0
Jan 27 00:27:43 f13c2c498a39 ARM: -1 day, 23:57:04.490301
[2024-01-27 00:28:10,002] DEBUG ARM: notifications.arm_nav_notify 10
[2024-01-27 00:28:10,021] WARNING ARM: task.add_task Task queue depth is 1
[2024-01-27 00:28:10,050] DEBUG ARM: utils.validate_logfile Logfile: THE_PLACE_BEYOND_THE_PINES_170631508785.log
[2024-01-27 00:29:03,255] WARNING ARM: task.add_task Task queue depth is 1
[2024-01-27 00:31:31,233] WARNING ARM: task.add_task Task queue depth is 2
[2024-01-27 00:33:29,076] WARNING ARM: task.add_task Task queue depth is 3
Anything else?
Not sure if it is relevant but here are my specs.
Ryzen 5 5000 CPU LG Blu-Ray (16NS) I think is the model Ubuntu 22.04
And my ARM Start Script.
#!/bin/bash
docker run -d \
-p "8080:8080" \
-e ARM_UID="1001" \
-e ARM_GID="1001" \
-e NVIDIA_DRIVER_CAPABILITIES=all \
-v "/home/arm:/home/arm" \
-v "/home/arm/logs:/home/arm/logs" \
-v "/home/arm/media:/home/arm/media" \
-v "/home/arm/config:/etc/arm/config" \
--device="/dev/sr0:/dev/sr0" \
--device="/dev/sr1:/dev/sr1" \
--device="/dev/sr2:/dev/sr2" \
--device="/dev/sr3:/dev/sr3" \
--privileged \
--restart "always" \
--name "arm-rippers" \
--cpuset-cpus='2,3,4,5,6,7' \
--gpus "all" \
automaticrippingmachine/automatic-ripping-machine:latest
Code of Conduct
- I agree to follow this project’s Code of Conduct
About this issue
- Original URL
- State: closed
- Created 5 months ago
- Comments: 15 (1 by maintainers)
Commits related to this issue
- Update runui.py, fix for #1046 — committed to microtechno9000/automatic-ripping-machine by microtechno9000 5 months ago
- Fix for #1046 and #1020 — committed to microtechno9000/automatic-ripping-machine by microtechno9000 5 months ago
Sorry for the late reply, but so far, the config change seems to have done the trick for my setup.