arr-scripts icon indicating copy to clipboard operation
arr-scripts copied to clipboard

[BUG] - Lidarr - Error: writing output failed: Broken pipe

Open compactly8274 opened this issue 2 years ago • 16 comments

Application Lidarr

Host platform Unraid

Script BeetsTagger.bash, LyricExtractor.bash, ArtworkExtractor.bash

Script Version 1.6, 1.5, 1.2

Describe the bug When running automatically I see this in the run log for all three scripts: Error: writing output failed: Broken pipe The Beets Tagger script runs successfully when manually calling in console with album id#

To Reproduce Steps to reproduce the behavior:

  1. Download an album
  2. Let the system import the album
  3. See the errors in the error log

Expected behavior All three scripts complete successfully on album import

Logs/Screenshots image ArtworkExtractor.txt BeetsTagger.txt LyricExtractor.txt lidarr.txt

Additional context This just started recently.

compactly8274 avatar Sep 21 '23 01:09 compactly8274

I think the latest changes may solve the issue, update and give it a test...

RandomNinjaAtk avatar Sep 21 '23 10:09 RandomNinjaAtk

I'm not sure how to resolve this, it doesn't appear to be causing any problems though... So for now, you can just ignore it...

RandomNinjaAtk avatar Sep 21 '23 12:09 RandomNinjaAtk

I think the latest changes may solve the issue, update and give it a test...

Tested after update: still getting the errors

lidarr.txt LyricExtractor-2023_09_21_11_58_AM.txt ArtworkExtractor-2023_09_21_11_58_AM.txt BeetsTagger-2023_09_21_11_58_AM.txt

Looks like they're all working though. Not sure what pipe it's complaining about, but there are the logs just in case they're any help!

compactly8274 avatar Sep 21 '23 19:09 compactly8274

Is it possible this is happening because the log file is still open while a logrotate happens ? Shouldn't we always write to scripts.log then mv the file to BeetsTagger-whateverdate.log when we do the logrotate ? I will try if that fixes it and will open a PR.

chadouming avatar Mar 08 '24 05:03 chadouming

I have the same error on all my downloads

Varming73 avatar Jul 29 '24 05:07 Varming73

Think this is now resolved, please verify the latest update resolves it and let me know. If I don't see a response, I'll move forward with closure.

RandomNinjaAtk avatar Jul 30 '24 13:07 RandomNinjaAtk

In this sequence it always occurs [Info] ImportDecisionMaker: Reading file 10/10 [Info] TrackGroupingService: Grouping 10 tracks [Info] IdentificationService: Identifying album 1/1 [Info] ImportApprovedTracks: Importing album 1/1 [Info] ImportApprovedTracks: Importing 10 tracks [Error] LyricExtractor.bash: jq: error: writing output failed: Broken pipe [Error] ArtworkExtractor.bash: jq: error: writing output failed: Broken pipe [Error] BeetsTagger.bash: jq: error: writing output failed: Broken pipe

humansage avatar Aug 24 '24 01:08 humansage