bug(agent): not picking up TCP port check results #929

New issue

Open

opened 2026-03-28 04:29:59 +00:00 by mfreeman451 · 1 comment

mfreeman451 commented

2026-03-28 04:29:59 +00:00

Owner

Imported from GitHub.

Original GitHub issue: #2628
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2628
Original created: 2026-01-31T03:15:57Z

Describe the bug
https://demo.serviceradar.cloud/devices/sr%3A47564b95-7b8f-4751-99c2-eb63c20bc3c8

The TCP scan should have picked up port 8080 being open every scan.

Time | Agent | Status | Response | Ports
-- | -- | -- | -- | --
2026-01-31 03:12 | agent-dusk | Available | 7ms | —
2026-01-31 03:07 | agent-dusk | Available | 7ms | —
2026-01-31 03:06 | k8s-agent | Available | 1ms | —
2026-01-31 03:02 | agent-dusk | Available | 7ms | 8080
2026-01-31 03:01 | k8s-agent | Available | 1ms | —

k8s-agent is blocked by a firewall

To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
A clear and concise description of what you expected to happen.

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: #2628 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2628 Original created: 2026-01-31T03:15:57Z --- **Describe the bug** https://demo.serviceradar.cloud/devices/sr%3A47564b95-7b8f-4751-99c2-eb63c20bc3c8 <img width="1221" height="724" alt="Image" src="https://github.com/user-attachments/assets/6214b87e-664b-47e2-ac14-3946203cf436" /> The TCP scan should have picked up port 8080 being open every scan. ``` Time | Agent | Status | Response | Ports -- | -- | -- | -- | -- 2026-01-31 03:12 | agent-dusk | Available | 7ms | — 2026-01-31 03:07 | agent-dusk | Available | 7ms | — 2026-01-31 03:06 | k8s-agent | Available | 1ms | — 2026-01-31 03:02 | agent-dusk | Available | 7ms | 8080 2026-01-31 03:01 | k8s-agent | Available | 1ms | — ``` k8s-agent is blocked by a firewall **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Expected behavior** A clear and concise description of what you expected to happen. **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.

mfreeman451 added this to the 1.1.1 milestone

2026-03-28 04:29:59 +00:00

mfreeman451 commented

2026-03-28 04:29:59 +00:00

Author

Owner

Imported GitHub comment.

Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2628#issuecomment-3829047989
Original created: 2026-01-31T18:49:28Z

I think this is a bit stale now, we're seeing TCP ports getting checked again, but it is not consistent. We have a server that is reliable/stable and responds to a bunch of port checks, but sometimes the UI shows only certain ports being available vs others, what also could be happening is in the scanner we might just be dropping things to save time/be fast.. I think we originally just designed the scanner so that it was super fast and would quickly tell us if a host was up or not, not necessarily always accurately report open/available ports.

Imported GitHub comment. Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2628#issuecomment-3829047989 Original created: 2026-01-31T18:49:28Z --- I think this is a bit stale now, we're seeing TCP ports getting checked again, but it is not consistent. We have a server that is reliable/stable and responds to a bunch of port checks, but sometimes the UI shows only certain ports being available vs others, what also could be happening is in the scanner we might just be dropping things to save time/be fast.. I think we originally just designed the scanner so that it was super fast and would quickly tell us if a host was up or not, not necessarily always accurately report open/available ports.