Skip to content

FSB relay reports hubConnected: false despite listener on 127.0.0.1:7225, causing dev agent to be unresponsive #48383

Description

@DiazOlveraCo

The FSB (File System Bridge) relay shows hubConnected: false in fsb_doctor output, even though netstat shows a listener on 127.0.0.1:7225. Attempts to connect via nc or /dev/tcp fail. The dev agent Java process (development-agent.jar) is running but cannot receive MCP commands due to the broken hub-relay connection.

fsb_doctor output:
{
"topology" : {
"instanceId" : "java-e8e84b6aae5b",
"mode" : "relay",
"hubHost" : "127.0.0.1",
"hubPort" : 7225,
"hubConnected" : false,
"extensionConnected" : true,
"relayCount" : 1,
"pendingRequestCount" : 0,
"activeHubInstanceId" : "java-f38d3556154f",
"lastExtensionHeartbeatAt" : 1789035909156,
"lastDisconnectReason" : "Lost connection to hub"
},
"agentId" : null,
"extensionAttached" : true,
"advice" : "Extension attached — tools should work."
}

netstat:
tcp6 0 0 127.0.0.1:7225 :::* LISTEN 208246/java

Connection test:
timeout 1 bash -c "cat < /dev/tcp/127.0.0.1/7225" 2>&1 && echo success || echo fail
=> fail

Steps to reproduce:

  1. Observe that the dev agent is unresponsive to MCP commands.
  2. Run fsb_doctor and note hubConnected: false.
  3. Verify that a process is listening on 127.0.0.1:7225.
  4. Attempt to connect to that port; connection fails.

Expected behavior:
The relay should establish a connection to the hub, allowing the dev agent to function.

Environment:

  • The session is not related to jumpstart, zv-prep, zv-login, or glab-auth.
  • The issue appears to be purely with the FSB hub-relay connectivity.

Please investigate why the listener on 127.0.0.1:7225 does not accept connections from the relay, and suggest steps to restore the hub-relay link.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions