Your Operating System and Version

Oct 13, 2025 by sorusgentrification.com 99 views

Introduction

Port forwarding is a crucial feature in Mirrord, allowing users to access remote services as if they were running locally. However, some users have reported experiencing connection reset issues when using the mirrord port-forward command. In this article, we will delve into the details of this issue, explore the possible causes, and provide a step-by-step guide to troubleshoot and resolve the problem.

Bug Description

The mirrord port-forward command is not forwarding properly, resulting in a connection reset error when attempting to reconnect to a Websocket. The error message indicates that the connection was reset due to a network error.

Steps to Reproduce

To reproduce this issue, follow these steps:

Clone the Mirrord Kafka debug example repository using the command git clone git@github.com:waveywaves/mirrord-kafka-debug-example.git.
Set up the Mirrord operator with the --kafka-splitting flag.
Run the mirrord port-forward command with the --port-mapping 8080:kafka-producer:9090 flag.
Visit http://localhost:8080/ in your web browser and open the inspector to view the Network tab.
To see the correct behavior, use the kubectl port-forward svc/kafka-producer 8080: command instead of Mirrord.

Backtrace

The backtrace is not provided in the original report, but it is likely related to the Mirrord port forwarding mechanism.

Mirrord Layer Logs

The Mirrord layer logs provide valuable information about the port forwarding process. Here are some excerpts from the logs:

2025-03-10T14:37:34.146201Z TRACE mirrord::port_forward: successful connection to remote address 10.96.147.109:9090, connection ID is 734
    at mirrord/cli/src/port_forward.rs:209
    in mirrord::port_forward::handle_msg_from_agent with TcpOutgoing(Connect(Ok(DaemonConnect { connection_id: 734, remote_address: Ip(10.96.147.109:9090), local_address: Ip(10.244.0.15:47166) })))

  2025-03-10T14:37:34.153810Z TRACE mirrord::port_forward: successful connection to remote address 10.96.147.109:9090, connection ID is 735
    at mirrord/cli/src/port_forward.rs:209
    in mirrord::port_forward::handle_msg_from_agent with TcpOutgoing(Connect(Ok(DaemonConnect { connection_id: 735, remote_address: Ip(10.96.147.109:9090), local_address: Ip(10.244.0.15:47180) })))

  2025-03-10T14:37:34.155188Z TRACE mirrord::port_forward: successful connection to remote address 10.96.147.109:9090, connection ID is 736
    at mirrord/cli/src/port_forward.rs:209
    in mirrord::port_forward::handle_msg_from_agent with TcpOutgoing(Connect(Ok(DaemonConnect { connection_id: 736, remote_address: Ip(10.96.147.109:9090), local_address: Ip(10.244.0.15:47192) })))

  2025-03-10T14:37:34.157431Z TRACE mirrord::port_forward: successful connection to remote address 10.96.147.109:9090, connection ID is 737
    at mirrord/cli/src/port_forward.rs:209
    in mirrord::port_forward::handle_msg_from_agent with TcpOutgoing(Connect(Ok(DaemonConnect { connection_id: 737, remote_address: Ip(10.96.147.109:9090), local_address: Ip(10.244.0.15:47194) })))

  2025-03-10T14:37:34.842277Z TRACE mirrord::port_forward: successful connection to remote address 10.96.147.109:9090, connection ID is 738
    at mirrord/cli/src/port_forward.rs:209
    in mirrord::port_forward::handle_msg_from_agent with TcpOutgoing(Connect(Ok(DaemonConnect { connection_id: 738, remote_address: Ip(10.96.147.109:9090), local_address: Ip(10.244.0.15:47198) })))

  2025-03-10T14:37:34.845336Z TRACE mirrord::port_forward: successful connection to remote address 10.96.147.109:9090, connection ID is 739
    at mirrord/cli/src/port_forward.rs:209
    in mirrord::port_forward::handle_msg_from_agent with TcpOutgoing(Connect(Ok(DaemonConnect { connection_id: 739, remote_address: Ip(10.96.147.109:9090), local_address: Ip(10.244.0.15:47208) })))

  2025-03-10T14:37:34.846258Z TRACE mirrord::port_forward: successful connection to remote address 10.96.147.109:9090, connection ID is 740
    at mirrord/cli/src/port_forward.rs:209
    in mirrord::port_forward::handle_msg_from_agent with TcpOutgoing(Connect(Ok(DaemonConnect { connection_id: 740, remote_address: Ip(10.96.147.109:9090), local_address: Ip(10.244.0.15:47216) })))

  2025-03-10T14:37:34.848897Z TRACE mirrord::port_forward: successful connection to remote address 10.96.147.109:9090, connection ID is 741
    at mirrord/cli/src/port_forward.rs:209
    in mirrord::port_forward::handle_msg_from_agent with TcpOutgoing(Connect(Ok(DaemonConnect { connection_id: 741, remote_address: Ip(10.96.147.109:9090), local_address: Ip(10.244.0.15:47228) })))

  2025-03-10T14:37:34.856448Z TRACE mirrord::port_forward: successful connection to remote address 10.96.147.109:9090, connection ID is 742
    at mirrord/cli/src/port_forward.rs:209
    in mirrord::port_forward::handle_msg_from_agent with TcpOutgoing(Connect(Ok(DaemonConnect { connection_id: 742, remote_address: Ip(10.96.147.109:9090), local_address: Ip(10.244.0.15:47244) })))

  2025-03-10T14:37:34.857216Z TRACE mirrord::port_forward: successful connection to remote address 10.96.147.109:9090, connection ID is 743
    at mirrord/cli/src/port_forward.rs:209
    in mirrord::port_forward::handle_msg_from_agent with TcpOutgoing(Connect(Ok(DaemonConnect { connection_id: 743, remote_address: Ip(10.96.147.109:9090), local_address: Ip(10.244.0.15:47256) })))

  2025-03-10T14:37:34.860744Z TRACE mirrord::port_forward: successful connection to remote address 10.96.147.109:9090, connection ID is 744
    at mirrord/cli/src/port_forward.rs:209
    in mirrord::port_forward::handle_msg_from_agent with TcpOutgoing(Connect(Ok(DaemonConnect { connection_id: 744, remote_address: Ip(10.96.147.109:9090), local_address: Ip(10.244.0.15:47266) })))

Mirrord Intproxy Logs

The Mirrord intproxy logs are not provided in the original report.

Mirrord Agent Logs

The Mirrord agent logs are not provided in the original report.

Mirrord Config

The Mirrord config is not provided in the original report.

Mirrord CLI Version

The Mirrord CLI version is 3.134.2.

Mirrord-Agent Version

The Mirrord-agent version is not provided in the original report.

Mirrord-Operator Version (if relevant)

The Mirrord-operator version is not provided in the original report.

Plugin Kind and Version (if relevant)

The plugin kind and version are not provided in the original report.

Your Operating System and Version

The operating system is MacOS 15.3.1.

Local Process

The local process is not provided in the original report.

Local Process Version

The local process version is not provided in the original report.

Additional Info

The problem was observed on both Kind and Docker-Desktop clusters.

Troubleshooting Steps

To troubleshoot this issue, follow these steps:

**Check the Mir
Port Forwarding Connection Reset Issue: Troubleshooting and Resolution ====================================================================

Q: What is the port forwarding connection reset issue?

A: The port forwarding connection reset issue is a problem that occurs when using the mirrord port-forward command, resulting in a connection reset error when attempting to reconnect to a Websocket.

Q: What are the symptoms of the port forwarding connection reset issue?

A: The symptoms of the port forwarding connection reset issue include:

Connection reset error when attempting to reconnect to a Websocket
Successful connections to the remote address, but subsequent connections are reset
No error messages or logs indicating the cause of the issue

Q: What are the possible causes of the port forwarding connection reset issue?

A: The possible causes of the port forwarding connection reset issue include:

Network issues: Problems with the network connection, such as packet loss or corruption, can cause the connection to be reset.
Mirrord configuration issues: Incorrect or incomplete configuration of the Mirrord operator or agent can cause the connection to be reset.
Plugin issues: Problems with the plugin used for port forwarding can cause the connection to be reset.
Operating system issues: Issues with the operating system, such as kernel bugs or driver problems, can cause the connection to be reset.

Q: How can I troubleshoot the port forwarding connection reset issue?

A: To troubleshoot the port forwarding connection reset issue, follow these steps:

Check the Mirrord logs: Review the Mirrord logs to see if there are any error messages or warnings indicating the cause of the issue.
Check the network connection: Verify that the network connection is stable and not experiencing any issues.
Check the Mirrord configuration: Review the Mirrord configuration to ensure that it is correct and complete.
Check the plugin: Verify that the plugin used for port forwarding is up-to-date and functioning correctly.
Check the operating system: Verify that the operating system is up-to-date and not experiencing any issues.

Q: How can I resolve the port forwarding connection reset issue?

A: To resolve the port forwarding connection reset issue, follow these steps:

Update the Mirrord operator and agent: Ensure that the Mirrord operator and agent are up-to-date with the latest versions.
Update the plugin: Update the plugin used for port forwarding to the latest version.
Check and fix the network connection: Verify that the network connection is stable and not experiencing any issues.
Check and fix the Mirrord configuration: Review the Mirrord configuration to ensure that it is correct and complete.
Check and fix the operating system: Verify that the operating system is up-to-date and not experiencing any issues.

Q: What are the best practices for preventing the port forwarding connection reset issue?

A: To prevent the port forwarding connection reset issue, follow these best practices:

Regularly update the Mirrord operator and agent: Ensure that the Mirrord operator and agent are up-to-date with the latest versions.
Regularly update the plugin: Update the plugin used for port forwarding to the latest version.
Monitor the network connection: Verify that the network connection is stable and not experiencing any issues.
Monitor the Mirrord configuration: Review the Mirrord configuration to ensure that it is correct and complete.
Monitor the operating system: Verify that the operating system is up-to-date and not experiencing any issues.

By following these troubleshooting steps and best practices, you can resolve the port forwarding connection reset issue and ensure that your Mirrord setup is stable and functioning correctly.