fix(deploy): restart orphaned podcast worker + prevent start-limiter wedge#115
Merged
Merged
Conversation
…wedge The bittorrented-podcast-worker systemd service is a separate long-running process that `next start` does not recreate. When it crash-looped during the June-7 mise/pnpm path drift it hit systemd's start limiter, went `failed`, and stayed dead for ~2 weeks: podcast episode ingestion stopped on 2026-06-07 because deploy-droplet.yml only restarts the main app + iptv worker, never the podcast worker, and its unit lacked StartLimitIntervalSec=0. - deploy-droplet.yml: reset-failed + restart bittorrented-podcast-worker on every deploy (and reset-failed the iptv worker for parity); report its status. - setup-server.sh: add StartLimitIntervalSec=0 to the podcast worker unit so a transient crash self-heals instead of wedging permanently. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Podcast episode ingestion stopped on 2026-06-07 (confirmed via
max(podcast_episodes.created_at)on the bittorrented Supabase project) — ~2 weeks with no new episodes for subscribers.bittorrented-podcast-workeris a separate long-running systemd process (pnpm podcast-worker) thatnext startdoes not recreate. During the June-7 mise/pnpm path drift it crash-looped, hit systemd's start limiter, wentfailed, and stayed dead — becausedeploy-droplet.ymlonly restarts the main app + iptv worker, never the podcast worker, and its unit lackedStartLimitIntervalSec=0.Fix
reset-failed+restart bittorrented-podcast-workeron every deploy (plusreset-failedfor the iptv worker for parity); report its status in the verify step.StartLimitIntervalSec=0to the podcast worker unit so a transient crash self-heals instead of wedging permanently.Note on live recovery
This restores the worker automatically on the next deploy. To recover prod immediately without waiting, run on the droplet:
🤖 Generated with Claude Code