Fix Archivist service startup failure due to port conflict#1491
Fix Archivist service startup failure due to port conflict#1491LokiMetaSmith wants to merge 1 commit intomainfrom
Conversation
Added logic to `pipecatapp/start_archivist.sh` to check if `ARCHIVIST_PORT` is in use using `lsof` and kill the owning process before starting `uvicorn`. This resolves the `[Errno 98] address already in use` error observed during deployments where previous instances were not correctly cleaned up. Co-authored-by: LokiMetaSmith <5054116+LokiMetaSmith@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
The Archivist service was failing to start with
[Errno 98] address already in usebecause the port was still occupied by a previous process (likely due to Nomad's raw_exec driver leaving orphaned processes or fast restarts).This change updates the
start_archivist.shscript to:lsofis available.lsofto detect ifARCHIVIST_PORTis in use.kill -9) the process(es) holding the port.This ensures the new
uvicorninstance can bind to the port successfully.PR created automatically by Jules for task 16090273670481981710 started by @LokiMetaSmith