Skip to content
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

Error warning for something that it's not an error. #32

Closed
janaxhell opened this issue Jun 26, 2022 · 4 comments
Closed

Error warning for something that it's not an error. #32

janaxhell opened this issue Jun 26, 2022 · 4 comments

Comments

@janaxhell
Copy link

I have just delpoyed https://github.com/RandomNinjaAtk/docker-lidarr-extended which is a standard Lidarr + AMD/AMVD scripts included to download via Deemix/Youtube. I've added flac2mp3 and it just works fine. Nevertheless lidarr-extended log says:

[Error] flac2mp3-debug-2.sh: Debug|Enabling debug logging level 2. Starting AlbumDownload run. [Info] RefreshArtistService: Updating Info for Sam Sparro [Info] RefreshAlbumService: Updating Info for Return To Paradise [Info] RefreshAlbumService: Updating Info for Sam Sparro [Error] flac2mp3-debug-2.sh: Warn|Lidarr job ID 171387 timed out or failed.

and flac2mp3.txt says
https://pastebin.com/kdVuSJW0

but it works. I just wanted to notify about this weird error message for something that doesn't look as an error. I'm not sure whether this issue is from lidarr side or your script side. FLACs are normally downloaded, compressed to MP3-320 and moved to recycle. No half-baked tracks, everything's fine. Just this apparently bogus error warning.

@TheCaptain989
Copy link
Owner

This error means that the final Lidarr API call to rescan the artist folders failed. You still get converted files, but Lidarr just might not reflect the update. Since you have debug level 2, you can check the flac2mp3.txt log file for full details. If you post it here I can look it over.

I've found Lidarr's API to be very finicky. Especially when it comes to string quoting, even for properties.

@janaxhell
Copy link
Author

Tha pastebin i linked is the log of debug-2 while that happened.

@TheCaptain989
Copy link
Owner

TheCaptain989 commented Jun 26, 2022

Oh, got it! Sorry.

Okay, the log just indicates a timeout. The script only waits 15 seconds for a rescan to complete and then gives up, but you can see that the rescan was triggered.

In short, nothing to worry about.

@janaxhell
Copy link
Author

Fine, cheers! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants