meeb
videos not being removed from share when time to auto delete
Hi Meeb,
On all my sources none of the videos are being removed from the share when it's time for them to auto delete. They are no longer showing in the media tab and are only listed in the skipped video section, but the files themselves are never removed from the folder share. There aren't any issues with permissions for the share. Nor did I find any errors in the logs.
Running on unraid 6.9.1 and tubesync:v0.9.1
Hi, the file deletion should work quite reliably. If the file deletion is triggering properly there should be something in the logs if the file can't be deleted. Can you confirm the sources have their delete old videos flag set as well as the date cap?
this is the setting for one of my sources. Delete old videos is ticked. Download cap is set for 7 Days. Keep is set for 1 Day. it all looks as expected in tubesynce but the share folder still contains all the video files. there is no error listed in logs pertaining to this nor is there any errors on the task page.
I tried to update the source to see if it would correct the issue by ticking and unticking delete old files but then I receive an 502 Bad Gateway error nginx that log error is post below.
2021/03/17 11:44:30 [error] 463#463: *1 upstream prematurely closed connection while reading response header from upstream, client: 192.168.3.134, server: _, request: "POST /source-update/6b30a2b9-d42f-4388-8ccb-327d94c51787 HTTP/1.1", upstream: "http://127.0.0.1:8080/source-update/6b30a2b9-d42f-4388-8ccb-327d94c51787", host: "192.168.3.49:4848", referrer: "http://192.168.3.49:4848/source-update/6b30a2b9-d42f-4388-8ccb-327d94c51787"
Ah, how many media items are in your sources? If they are large channels with a lot of media you are likely being affected by performance issues which are scheduled to be fixed in issues like #93, #94 and #72 - that is the back end is exceeding 60 seconds before the task is complete and doesn't get around to finishing some tasks. If this is the case it's unfortunately annoying for you in the short term but the good news is that it will be fixed before the 1.0 release.