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:
- Observe that the dev agent is unresponsive to MCP commands.
- Run
fsb_doctor and note hubConnected: false.
- Verify that a process is listening on 127.0.0.1:7225.
- 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.
The FSB (File System Bridge) relay shows
hubConnected: falseinfsb_doctoroutput, even thoughnetstatshows a listener on 127.0.0.1:7225. Attempts to connect viancor/dev/tcpfail. 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:
fsb_doctorand notehubConnected: false.Expected behavior:
The relay should establish a connection to the hub, allowing the dev agent to function.
Environment:
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.