starred/arr-scripts
1
0
Fork 0
mirror of https://github.com/RandomNinjaAtk/arr-scripts.git synced 2026-03-02 22:57:35 -05:00
Code Issues 55 Projects Packages Wiki Activity

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

New issue
Closed
opened 2026-02-20 00:14:25 -05:00 by deekerman · 20 comments
deekerman commented 2026-02-20 00:14:25 -05:00
Owner
Copy link

Originally created by @compactly8274 on GitHub (Sep 20, 2023).

Originally assigned to: @RandomNinjaAtk on GitHub.

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.

Originally created by @compactly8274 on GitHub (Sep 20, 2023). Originally assigned to: @RandomNinjaAtk on GitHub. **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](https://github.com/RandomNinjaAtk/arr-scripts/assets/22104399/e128c84e-b42f-4a84-97df-12c21e046f2d) [ArtworkExtractor.txt](https://github.com/RandomNinjaAtk/arr-scripts/files/12678942/ArtworkExtractor.txt) [BeetsTagger.txt](https://github.com/RandomNinjaAtk/arr-scripts/files/12678943/BeetsTagger.txt) [LyricExtractor.txt](https://github.com/RandomNinjaAtk/arr-scripts/files/12678941/LyricExtractor.txt) [lidarr.txt](https://github.com/RandomNinjaAtk/arr-scripts/files/12678973/lidarr.txt) **Additional context** This just started recently.
deekerman 2026-02-20 00:14:25 -05:00
deekerman commented 2026-02-20 00:14:26 -05:00
Author
Owner
Copy link

@RandomNinjaAtk commented on GitHub (Sep 21, 2023):

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

@RandomNinjaAtk commented on GitHub (Sep 21, 2023): I think the latest changes may solve the issue, update and give it a test...
deekerman commented 2026-02-20 00:14:26 -05:00
Author
Owner
Copy link

@RandomNinjaAtk commented on GitHub (Sep 21, 2023):

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 commented on GitHub (Sep 21, 2023): 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...
deekerman commented 2026-02-20 00:14:27 -05:00
Author
Owner
Copy link

@compactly8274 commented on GitHub (Sep 21, 2023):

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 commented on GitHub (Sep 21, 2023): > I think the latest changes may solve the issue, update and give it a test... Tested after update: still getting the errors [lidarr.txt](https://github.com/RandomNinjaAtk/arr-scripts/files/12690709/lidarr.txt) [LyricExtractor-2023_09_21_11_58_AM.txt](https://github.com/RandomNinjaAtk/arr-scripts/files/12690711/LyricExtractor-2023_09_21_11_58_AM.txt) [ArtworkExtractor-2023_09_21_11_58_AM.txt](https://github.com/RandomNinjaAtk/arr-scripts/files/12690712/ArtworkExtractor-2023_09_21_11_58_AM.txt) [BeetsTagger-2023_09_21_11_58_AM.txt](https://github.com/RandomNinjaAtk/arr-scripts/files/12690713/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!
deekerman commented 2026-02-20 00:14:27 -05:00
Author
Owner
Copy link

@chadouming commented on GitHub (Mar 8, 2024):

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 commented on GitHub (Mar 8, 2024): 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.
deekerman commented 2026-02-20 00:14:28 -05:00
Author
Owner
Copy link

@Varming73 commented on GitHub (Jul 29, 2024):

I have the same error on all my downloads

@Varming73 commented on GitHub (Jul 29, 2024): I have the same error on all my downloads
deekerman commented 2026-02-20 00:14:28 -05:00
Author
Owner
Copy link

@RandomNinjaAtk commented on GitHub (Jul 30, 2024):

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 commented on GitHub (Jul 30, 2024): 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.
deekerman commented 2026-02-20 00:14:28 -05:00
Author
Owner
Copy link

@humansage commented on GitHub (Aug 23, 2024):

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 commented on GitHub (Aug 23, 2024): 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
deekerman commented 2026-02-20 00:14:28 -05:00
Author
Owner
Copy link

@Unspec7 commented on GitHub (Nov 22, 2024):

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

@Unspec7 commented on GitHub (Nov 22, 2024): Definitely still an issue. Seeing it now with the latest version.
deekerman commented 2026-02-20 00:14:29 -05:00
Author
Owner
Copy link

@zengateway commented on GitHub (Nov 24, 2024):

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

yep, same problem there

@zengateway commented on GitHub (Nov 24, 2024): > Definitely still an issue. Seeing it now with the latest version. yep, same problem there
deekerman commented 2026-02-20 00:14:29 -05:00
Author
Owner
Copy link

@ersnow42 commented on GitHub (Dec 3, 2024):

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?

@ersnow42 commented on GitHub (Dec 3, 2024): 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?
deekerman commented 2026-02-20 00:14:29 -05:00
Author
Owner
Copy link

@SKlopp commented on GitHub (Dec 9, 2024):

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 commented on GitHub (Dec 9, 2024): same here. Not sure, but the Tagger seems to do the job with Tracks coming via Deezer/Tidal, but not for manally added Tracks.
deekerman commented 2026-02-20 00:14:29 -05:00
Author
Owner
Copy link

@SKlopp commented on GitHub (Dec 9, 2024):

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

@SKlopp commented on GitHub (Dec 9, 2024): same here. Not sure, but the Tagger seems to do the job with Tracks coming via Deezer/Tidal, but not for those via Usenet.
deekerman commented 2026-02-20 00:14:30 -05:00
Author
Owner
Copy link

@sovereignalmida commented on GitHub (Dec 13, 2024):

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

@sovereignalmida commented on GitHub (Dec 13, 2024): 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
deekerman commented 2026-02-20 00:14:30 -05:00
Author
Owner
Copy link

@cryd-s commented on GitHub (Jan 2, 2025):

image
same here

@cryd-s commented on GitHub (Jan 2, 2025): ![image](https://github.com/user-attachments/assets/93c38e3c-fde9-4c36-907e-9b8ddbe13884) same here
deekerman commented 2026-02-20 00:14:31 -05:00
Author
Owner
Copy link

@agster27 commented on GitHub (Feb 1, 2025):

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.

@agster27 commented on GitHub (Feb 1, 2025): 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.
deekerman commented 2026-02-20 00:14:31 -05:00
Author
Owner
Copy link

@Hylas01 commented on GitHub (Feb 19, 2025):

Still an issue here as well.

@Hylas01 commented on GitHub (Feb 19, 2025): Still an issue here as well.
deekerman commented 2026-02-20 00:14:32 -05:00
Author
Owner
Copy link

@SeadogsBooty commented on GitHub (Jul 15, 2025):

Seeing this issue still - July 2025
However, it doesn't seem to affect the import and song being added to the destination.

2025-07-15T20:42:47.093771751Z [Info] ImportDecisionMaker: Reading file 1/1
2025-07-15T20:42:47.102378662Z [Info] TrackGroupingService: Grouping 1 tracks
2025-07-15T20:42:47.102881623Z [Info] IdentificationService: Identifying album 1/1
2025-07-15T20:42:47.135631241Z [Info] ImportApprovedTracks: Importing album 1/1
2025-07-15T20:42:48.613860939Z [Info] ImportApprovedTracks: Importing 1 tracks
2025-07-15T20:43:00.467717724Z [Info] ImportDecisionMaker: Reading file 1/10
2025-07-15T20:43:00.543355666Z [Info] ImportDecisionMaker: Reading file 2/10
2025-07-15T20:43:00.564582193Z [Info] ImportDecisionMaker: Reading file 3/10
2025-07-15T20:43:00.581328413Z [Info] ImportDecisionMaker: Reading file 4/10
2025-07-15T20:43:00.596965239Z [Info] ImportDecisionMaker: Reading file 5/10
2025-07-15T20:43:00.607524138Z [Info] ImportDecisionMaker: Reading file 6/10
2025-07-15T20:43:00.627974001Z [Info] ImportDecisionMaker: Reading file 7/10
2025-07-15T20:43:00.645916416Z [Info] ImportDecisionMaker: Reading file 8/10
2025-07-15T20:43:00.670737695Z [Info] ImportDecisionMaker: Reading file 9/10
2025-07-15T20:43:00.692650404Z [Info] ImportDecisionMaker: Reading file 10/10
2025-07-15T20:43:00.699506229Z [Info] TrackGroupingService: Grouping 10 tracks
2025-07-15T20:43:00.700013971Z [Info] IdentificationService: Identifying album 1/1
2025-07-15T20:43:00.743536058Z [Info] ImportApprovedTracks: Importing album 1/1
2025-07-15T20:43:03.496268919Z [Info] ImportApprovedTracks: Importing 10 tracks
2025-07-15T20:43:07.741210009Z [Error] LyricExtractor.bash: jq: error: writing output failed: Broken pipe
2025-07-15T20:43:10.939939508Z [Error] ArtworkExtractor.bash: jq: error: writing output failed: Broken pipe
2025-07-15T20:43:12.046877708Z [Error] BeetsTagger.bash: jq: error: writing output failed: Broken pipe

@SeadogsBooty commented on GitHub (Jul 15, 2025): Seeing this issue still - July 2025 However, it doesn't seem to affect the import and song being added to the destination. 2025-07-15T20:42:47.093771751Z [Info] ImportDecisionMaker: Reading file 1/1 2025-07-15T20:42:47.102378662Z [Info] TrackGroupingService: Grouping 1 tracks 2025-07-15T20:42:47.102881623Z [Info] IdentificationService: Identifying album 1/1 2025-07-15T20:42:47.135631241Z [Info] ImportApprovedTracks: Importing album 1/1 2025-07-15T20:42:48.613860939Z [Info] ImportApprovedTracks: Importing 1 tracks 2025-07-15T20:43:00.467717724Z [Info] ImportDecisionMaker: Reading file 1/10 2025-07-15T20:43:00.543355666Z [Info] ImportDecisionMaker: Reading file 2/10 2025-07-15T20:43:00.564582193Z [Info] ImportDecisionMaker: Reading file 3/10 2025-07-15T20:43:00.581328413Z [Info] ImportDecisionMaker: Reading file 4/10 2025-07-15T20:43:00.596965239Z [Info] ImportDecisionMaker: Reading file 5/10 2025-07-15T20:43:00.607524138Z [Info] ImportDecisionMaker: Reading file 6/10 2025-07-15T20:43:00.627974001Z [Info] ImportDecisionMaker: Reading file 7/10 2025-07-15T20:43:00.645916416Z [Info] ImportDecisionMaker: Reading file 8/10 2025-07-15T20:43:00.670737695Z [Info] ImportDecisionMaker: Reading file 9/10 2025-07-15T20:43:00.692650404Z [Info] ImportDecisionMaker: Reading file 10/10 2025-07-15T20:43:00.699506229Z [Info] TrackGroupingService: Grouping 10 tracks 2025-07-15T20:43:00.700013971Z [Info] IdentificationService: Identifying album 1/1 2025-07-15T20:43:00.743536058Z [Info] ImportApprovedTracks: Importing album 1/1 2025-07-15T20:43:03.496268919Z [Info] ImportApprovedTracks: Importing 10 tracks 2025-07-15T20:43:07.741210009Z [Error] LyricExtractor.bash: jq: error: writing output failed: Broken pipe 2025-07-15T20:43:10.939939508Z [Error] ArtworkExtractor.bash: jq: error: writing output failed: Broken pipe 2025-07-15T20:43:12.046877708Z [Error] BeetsTagger.bash: jq: error: writing output failed: Broken pipe
deekerman commented 2026-02-20 00:14:32 -05:00
Author
Owner
Copy link

@p4p4j0hn commented on GitHub (Oct 23, 2025):

I noticed that /universal/functions.bash uses xq in getArrAppInfo, however, xq is missing in the apk installation section of setup.bash for each 'arr.

@p4p4j0hn commented on GitHub (Oct 23, 2025): I noticed that /universal/functions.bash uses `xq` in `getArrAppInfo`, however, `xq` is missing in the apk installation section of setup.bash for each 'arr.
deekerman commented 2026-02-20 00:14:33 -05:00
Author
Owner
Copy link

@rijndael86 commented on GitHub (Jan 5, 2026):

I'm still suffering this issue on a fresh install, I've already checked that lidarr was using the setup.bash script with the xq package in the requirements:

lidarr  | [Info] ImportDecisionMaker: Reading file 13/13
lidarr  | [Info] TrackGroupingService: Grouping 13 tracks
lidarr  | [Info] IdentificationService: Identifying album 1/1
lidarr  | [Info] ImportApprovedTracks: Importing album 1/1
lidarr  | [Info] ImportApprovedTracks: Importing 13 tracks
lidarr  | [Error] LyricExtractor.bash: jq: error: writing output failed: Broken pipe
lidarr  | [Error] ArtworkExtractor.bash: jq: error: writing output failed: Broken pipe
lidarr  | [Error] BeetsTagger.bash: jq: error: writing output failed: Broken pipe
@rijndael86 commented on GitHub (Jan 5, 2026): I'm still suffering this issue on a fresh install, I've already checked that lidarr was using the setup.bash script with the xq package in the requirements: ``` lidarr | [Info] ImportDecisionMaker: Reading file 13/13 lidarr | [Info] TrackGroupingService: Grouping 13 tracks lidarr | [Info] IdentificationService: Identifying album 1/1 lidarr | [Info] ImportApprovedTracks: Importing album 1/1 lidarr | [Info] ImportApprovedTracks: Importing 13 tracks lidarr | [Error] LyricExtractor.bash: jq: error: writing output failed: Broken pipe lidarr | [Error] ArtworkExtractor.bash: jq: error: writing output failed: Broken pipe lidarr | [Error] BeetsTagger.bash: jq: error: writing output failed: Broken pipe ```
deekerman commented 2026-02-20 00:14:33 -05:00
Author
Owner
Copy link

@tboucher204 commented on GitHub (Jan 25, 2026):

I'm still suffering this issue on a fresh install, I've already checked that lidarr was using the setup.bash script with the xq package in the requirements:

lidarr  | [Info] ImportDecisionMaker: Reading file 13/13
lidarr  | [Info] TrackGroupingService: Grouping 13 tracks
lidarr  | [Info] IdentificationService: Identifying album 1/1
lidarr  | [Info] ImportApprovedTracks: Importing album 1/1
lidarr  | [Info] ImportApprovedTracks: Importing 13 tracks
lidarr  | [Error] LyricExtractor.bash: jq: error: writing output failed: Broken pipe
lidarr  | [Error] ArtworkExtractor.bash: jq: error: writing output failed: Broken pipe
lidarr  | [Error] BeetsTagger.bash: jq: error: writing output failed: Broken pipe

I have the same issue as well. Additionally, I did exec into the container and verify xq is installed and is version 3.4.3

@tboucher204 commented on GitHub (Jan 25, 2026): > I'm still suffering this issue on a fresh install, I've already checked that lidarr was using the setup.bash script with the xq package in the requirements: > > ``` > lidarr | [Info] ImportDecisionMaker: Reading file 13/13 > lidarr | [Info] TrackGroupingService: Grouping 13 tracks > lidarr | [Info] IdentificationService: Identifying album 1/1 > lidarr | [Info] ImportApprovedTracks: Importing album 1/1 > lidarr | [Info] ImportApprovedTracks: Importing 13 tracks > lidarr | [Error] LyricExtractor.bash: jq: error: writing output failed: Broken pipe > lidarr | [Error] ArtworkExtractor.bash: jq: error: writing output failed: Broken pipe > lidarr | [Error] BeetsTagger.bash: jq: error: writing output failed: Broken pipe > ``` I have the same issue as well. Additionally, I did exec into the container and verify xq is installed and is version 3.4.3
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
Needs Triage

   
Not Reproducible

   
Upstream Issue

   
User Error

   
bug

   
documentation

   
enhancement

   
good first issue

   
help wanted

   
invalid

   
lidarr

   
lidarr

   
question

   
radarr

   
readarr

   
sabnzbd

   
sonarr

   
synology (host)

   
unraid (host)

   
waiting for logs

   
wontfix
No labels
Needs Triage
Not Reproducible
Upstream Issue
User Error
bug
documentation
enhancement
good first issue
help wanted
invalid
lidarr
lidarr
question
radarr
readarr
sabnzbd
sonarr
synology (host)
unraid (host)
waiting for logs
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/arr-scripts#59
No description provided.