bug(flowgger): crashes if it can't reach NATS #557

New issue

Closed

opened 2026-03-28 04:25:43 +00:00 by mfreeman451 · 0 comments

mfreeman451 commented

2026-03-28 04:25:43 +00:00

Owner

Imported from GitHub.

Original GitHub issue: #1760
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/1760
Original created: 2025-10-14T18:48:45Z

Describe the bug
Starting ServiceRadar Flowgger with config: /etc/serviceradar/flowgger.toml
Flowgger 0.0.0

thread '' panicked at cmd/flowgger/src/flowgger/output/nats_output.rs:139:44:
NATS connection failed: Error { kind: Io, source: Some(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Flowgger should either fully crash so k8s can try and restart it, or implement some kinda exponential backoff to reconnect to NATS

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Imported from GitHub. Original GitHub issue: #1760 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/1760 Original created: 2025-10-14T18:48:45Z --- **Describe the bug** Starting ServiceRadar Flowgger with config: /etc/serviceradar/flowgger.toml Flowgger 0.0.0 thread '<unnamed>' panicked at cmd/flowgger/src/flowgger/output/nats_output.rs:139:44: NATS connection failed: Error { kind: Io, source: Some(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }) } note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Expected behavior** Flowgger should either fully crash so k8s can try and restart it, or implement some kinda exponential backoff to reconnect to NATS **Screenshots** If applicable, add screenshots to help explain your problem. **Desktop (please complete the following information):** - OS: [e.g. iOS] - Browser [e.g. chrome, safari] - Version [e.g. 22] **Smartphone (please complete the following information):** - Device: [e.g. iPhone6] - OS: [e.g. iOS8.1] - Browser [e.g. stock browser, safari] - Version [e.g. 22] **Additional context** Add any other context about the problem here.