Page MenuHomePhabricator

Blast of broken pipe errors from catalyst-api container log stream
Closed, ResolvedPublic1 Estimated Story Points

Description

I've seen the following several times from my catalyst-api process while testing patchdemo locally:

[catalyst-api][GIN] 2026/02/13 - 21:55:06 | 200 |         1m59s |     10.244.0.22 | GET      "/api/environments/4/logs?stream=mediawiki/install-mediawiki"
[catalyst-api]Error #01: write tcp 10.244.0.42:8080->10.244.0.22:58182: write: broken pipe
[catalyst-api]Error #02: write tcp 10.244.0.42:8080->10.244.0.22:58182: write: broken pipe
[catalyst-api]Error #03: write tcp 10.244.0.42:8080->10.244.0.22:58182: write: broken pipe
[catalyst-api]Error #04: write tcp 10.244.0.42:8080->10.244.0.22:58182: write: broken pipe
[catalyst-api]Error #05: write tcp 10.244.0.42:8080->10.244.0.22:58182: write: broken pipe
[catalyst-api]Error #06: write tcp 10.244.0.42:8080->10.244.0.22:58182: write: broken pipe
[catalyst-api]Error #07: write tcp 10.244.0.42:8080->10.244.0.22:58182: write: broken pipe
...hundreds more...
[catalyst-api]Error #594: write tcp 10.244.0.42:8080->10.244.0.22:58182: write: broken pipe

Details

Related Changes in GitLab:
TitleReferenceAuthorSource BranchDest Branch
detect broken connection when streaming container logsrepos/test-platform/catalyst/catalyst-api!168jnucheT417689main
Add test case for broken pipe errorsrepos/test-platform/catalyst/catalyst-api!160dancymain-I0aa84f43c8e2412747eafff74f3567bcb52b6144main
Customize query in GitLab

Event Timeline

jnuche set the point value for this task to 1.