starred/arr-scripts

Fork 0

mirror of https://github.com/RandomNinjaAtk/arr-scripts.git synced 2026-03-02 22:57:35 -05:00

[BUG] - Lidarr - BeetsTagger jq broken pipe #217

New issue

Open

opened 2026-02-20 00:18:09 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-20 00:18:09 -05:00

Owner

Originally created by @kaibagley on GitHub (Dec 11, 2025).

Application
Lidarr

Host platform
Ubuntu 24 with Docker

Script
BeetsTagger
ArtworkExtractor
LyricsExtractor

Script Version
latest

Describe the bug
Each of the scripts give an error:
jq: error: writing output failed: Broken pipe.

Expected behavior
No errors in thr log. I also have strangely tagged tracks that wont seem to go away, and this may be related.

Ive seen other issues with the same pipe error, but i don't think i have permission errors, and i believe i have the xq thing installed from the PR a while ago

Logs/Screenshots
Can provide if needed

Additional context
Add any other context about the problem here.

NOTE
Your request will not be addressed without proper detail and logs. Always make sure you have updated to the latest script versions before opening an issue or your issue will not be reviewed.

Originally created by @kaibagley on GitHub (Dec 11, 2025). **Application** Lidarr **Host platform** Ubuntu 24 with Docker **Script** BeetsTagger ArtworkExtractor LyricsExtractor **Script Version** latest **Describe the bug** Each of the scripts give an error: `jq: error: writing output failed: Broken pipe`. **Expected behavior** No errors in thr log. I also have strangely tagged tracks that wont seem to go away, and this may be related. Ive seen other issues with the same pipe error, but i don't think i have permission errors, and i believe i have the xq thing installed from the PR a while ago **Logs/Screenshots** Can provide if needed **Additional context** Add any other context about the problem here. **NOTE** Your request will not be addressed without proper detail and logs. Always make sure you have updated to the latest script versions before opening an issue or your issue will not be reviewed.

deekerman added the

Needs Triage

label

2026-02-20 00:18:09 -05:00

deekerman commented

2026-02-20 00:18:10 -05:00

Author

Owner

@Poisonsting commented on GitHub (Jan 26, 2026):

I'm also experiencing this issue, I can also provide logs if needed, but the logs do not appear to provide a trace for this error by default. Any way to increase verbosity for troubleshooting?

@Poisonsting commented on GitHub (Jan 26, 2026): I'm also experiencing this issue, I can also provide logs if needed, but the logs do not appear to provide a trace for this error by default. Any way to increase verbosity for troubleshooting?

deekerman commented

2026-02-20 00:18:11 -05:00

Author

Owner

@Poisonsting commented on GitHub (Feb 7, 2026):

I was able to solve this particular issue by running chmod +x scripts_init.bash

@Poisonsting commented on GitHub (Feb 7, 2026): I was able to solve this particular issue by running `chmod +x scripts_init.bash`

No milestone

No project

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#217

No description provided.

Rows
Columns