You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Andrushika (via GitHub)" <gi...@apache.org> on 2026/09/05 15:57:06 UTC
[PR] Show which processes hold the Breeze UI ports when start-airflow fails [airflow]
Andrushika opened a new pull request, #72564:
URL: https://github.com/apache/airflow/pull/72564
## Why
Follow-up of #71241: `breeze start-airflow --dev-mode` fails early when port 5173 or 5174 is taken. But the message only says the port is in use. Users then need to run `lsof` themselves to see which processes hold the ports before they can stop them, which is a bit annoying. Most of the time it is just a stale Vite dev server left over from a previous breeze run.
## What
Look up the listening process with psutil and print its PID and command line, plus a `kill <pid>` hint. If the listener cannot be found (for example no permission), the old message is kept. psutil is bumped to `>=6.0.0` because `Process.net_connections()` was added there.
Before:
```
Cannot start UI development servers because the following local port(s) are already in use: 5173, 5174.
Stop the processes using these ports and try again.
```
Now:
```
Cannot start UI development servers because the following local port(s) are already in use: 5173, 5174.
Port 5173 is used by PID 5771: node /Users/andrewchang/Dev/github.com/airflow/airflow-core/src/airflow/ui/node_modules/.bin/../vite/bin/vite.js —port 5173 —strictPort
Port 5174 is used by PID 5793: node /Users/andrewchang/Dev/github.com/airflow/airflow-core/src/airflow/api_fastapi/auth/managers/simple/ui/node_modules/.bin/../vite/bin/vite.js —port 5174 —strictPort
Stop the processes using these ports (for example kill 5771 5793) and try again.
```
related: #71241
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Code (Fable 5.1)
Generated-by: Claude Code (Fable 5.1) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Show which processes hold the Breeze UI ports when start-airflow fails [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk merged PR #72564:
URL: https://github.com/apache/airflow/pull/72564
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Show which processes hold the Breeze UI ports when start-airflow fails [airflow]
Posted by "Andrushika (via GitHub)" <gi...@apache.org>.
Andrushika commented on PR #72564:
URL: https://github.com/apache/airflow/pull/72564#issuecomment-5553588535
Added a test: `test_find_local_port_listeners_skips_processes_that_cannot_be_inspected`, thanks for reviewing!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Show which processes hold the Breeze UI ports when start-airflow fails [airflow]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #72564:
URL: https://github.com/apache/airflow/pull/72564#issuecomment-5574920362
### Backport failed to create: v3-3-test. View the failure log <a href='https://github.com/apache/airflow/actions/runs/34155880149'> Run details </a>
Note: As of [Merging PRs targeted for Airflow 3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.
In matter of doubt please ask in [#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) Slack channel.
<table>
<tr>
<th>Status</th>
<th>Branch</th>
<th>Result</th>
</tr>
<tr>
<td>❌</td>
<td>v3-3-test</td>
<td><a href="https://github.com/apache/airflow/commit/ec71f28f2dba324d7398db3712d5764d774752b0"><img src='https://img.shields.io/badge/Commit-ec71f28-red' alt='Commit Link'></a></td>
</tr>
</table>
You can attempt to backport this manually by running:
```bash
cherry_picker ec71f28 v3-3-test
```
This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.
After you have resolved the conflicts, you can continue the backport process by running:
```bash
cherry_picker --continue
```
If you don't have cherry-picker installed, see the [installation guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org