🐋 <Backup Option & Progress While Ripping>

[polskikrol]

Is there an existing issue for this?

• I have searched the existing issues

Does this issue exist in the latest version?

• I'm using the latest release

Describe the bug?

This may be a quick one to fix in code. When ripping from BD using backup method, I see errors when viewing docker logs:

tail: cannot open '/home/arm/logs/progress/58.log' for reading: No such file or directory
[2024-03-06 22:14:11,651] DEBUG ARM: json_api.read_log_line Error while reading logfile for ETA
[2024-03-06 22:14:11,652] DEBUG ARM: json_api.get_x_jobs jobs  - we have 1 jobs
[2024-03-06 22:14:13,700] DEBUG ARM: json_api.process_logfile ripping
[2024-03-06 22:14:13,700] DEBUG ARM: json_api.process_logfile using mkv - /home/arm/logs/LONE_SURVIVOR_170977994642.log

Now, the directory has the proper permissions for the user... if I touch the file and chmod with the same UID/GID, the error goes away.

[2024-03-06 22:22:59,763] DEBUG ARM: json_api.get_x_jobs jobs  - we have 1 jobs
[2024-03-06 22:23:01,804] DEBUG ARM: json_api.process_logfile ripping
[2024-03-06 22:23:01,804] DEBUG ARM: json_api.process_logfile using mkv - /home/arm/logs/LONE_SURVIVOR_170977994642.log

However, nothing is ever written to the file. Log file 58.log in the progress folder remains at size zero. So, not sure why we even attempt to tail this file. I presume this is to maybe somehow update the GUI status of the ripping operation. This does not update, status is ripping, and job time is none.

To Reproduce

Please see description.

Built from source files ?

• I Built the image from source

What architecture are you seeing the problem on?

amd64

Expected behavior?

I would expect a log file to be used properly, and updates to the status when ripping. Quick fix may be to get rid of the tail statement in code.

Relevant log output

No response

Anything else?

No response

Code of Conduct

• I agree to follow this project's Code of Conduct