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

[compactly8274]

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

ArtworkExtractor.txt
BeetsTagger.txt
LyricExtractor.txt
lidarr.txt

Additional context
This just started recently.

[RandomNinjaAtk]

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

[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...

[compactly8274]

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!

[chadouming]

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.

[Varming73]

I have the same error on all my downloads

[RandomNinjaAtk]

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.

[humansage]

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

[Unspec7]

Definitely still an issue. Seeing it now with the latest version.

[zengateway]

Definitely still an issue. Seeing it now with the latest version.

yep, same problem there

[ersnow42]

Also seeing the same problem. I'm unclear - is it actually failing the tagging script? Or is this just a failed log pipe output from the tagger script?

[SKlopp]

same here. Not sure, but the Tagger seems to do the job with Tracks coming via Deezer/Tidal, but not for manally added Tracks.

[SKlopp]

same here. Not sure, but the Tagger seems to do the job with Tracks coming via Deezer/Tidal, but not for those via Usenet.

[calm108]

I have the exact same issue as of today. Using Tidal only - brand new install of Lidarr and the arrrscript.

log errors:

[Error] LyricExtractor.bash: jq: error: writing output failed: Broken pipe
[Error] ArtworkExtractor.bash: jq: error: writing output failed: Broken pipe
[Error] ArtworkExtractor.bash: find: ‘standard output’: Broken pipe
[Error] ArtworkExtractor.bash: find: write error
[Error] BeetsTagger.bash: jq: error: writing output failed: Broken pipe

[cryd-s]

same here

[agster27]

Same issues here as well:

[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

Not sure where to troubleshoot.