-
Notifications
You must be signed in to change notification settings - Fork 27
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
Not cleaning up files after upload #2
Comments
There should be no leftover files unless you modified the -rclone_command="move"
+rclone_command="copy" If you haven't already, try running the script with As for the |
I've added some checks to prevent the script from running if the rclone config isn't found or if the specified remote has any issues (not found, unauthorized, etc.). If either of these are the culprit the latest version should let you know. To update:
|
Just realized you meant it's only failing to upload the metadata, not everything. This is in part due to For a channel with ~450 videos, the metadata ( Couple ways you can try to circumvent this:
As for cleaning up the mess so
|
Thank you for the very in-depth reply! After some testing and thinking, I believe I figured out the cause - I was running rclone with custom flag Totally my fault I must admit! Something I noticed when looking through the limited screen session log is that ytdlrc will continue working through the list even with a full disk: [download] Downloading video 605 of 661 I have a suggestion if you don't mind: A minimum space remaining on disk check before each youtube download is started. Thank you for creating this wonderful script! |
Suggestions are more than welcome! A free space check before each download is a possibility if I can work out a sane way to add it. What you can do in the meantime is tell youtube-dl to abort if it encounters any errors by removing the Line 252 in 3d6b2fc
The downside to this is some videos tend to be unavailable (usually due to copyright) and youtube-dl treats these as errors, as such it will skip the rest of the channel even if your VPS has plenty of space left. If you opt to go this route, you'll need to check your syslog periodically or run FWIW, it should be fairly safe to keep |
Is this by intention to not clean up files left over, e.g. covers, json, description, occasional .webm?
I was running it on a rather large channel (2TB+) and eventually the VPS disk got filled due to those remaining files building up, and for some reason some .webm.parts - not sure on the cause of that yet.
The text was updated successfully, but these errors were encountered: