Getting erro while monitoring servers

[gseckin]

When I check server tab, I see these errors.

The detail error is: 

The underlying connection was closed: An unexpected error occurred on a send. Authentication failed because the remote party has closed the transport stream.

How can we fix this error?

Thanks

[cassie2698bratt]

---

@gseckinmarykayintouch wrote:

When I check server tab, I see these errors.

The detail error is: 

The underlying connection was closed: An unexpected error occurred on a send. Authentication failed because the remote party has closed the transport stream.

How can we fix this error?

Thanks

---

Hello,

The error message "The underlying connection was closed: An unexpected error occurred on a send. Authentication failed because the remote party has closed the transport stream" indicates an issue with establishing a secure connection between your monitoring tool and the server it's trying to monitor. Here are some steps you can take to diagnose and fix the error:

1. Check Server Status:

Ensure the server you're trying to monitor is operational and accepting connections. Try accessing the server directly (if possible) to verify its functionality.
2. Verify Authentication Credentials:

Double-check that the username and password (or API key) used by your monitoring tool are correct and have the necessary permissions to access the server.
3. Review Network Connectivity:

Make sure there are no firewalls or network restrictions blocking communication between the monitoring tool and the server. You can try temporarily disabling firewalls on both ends to isolate the issue (not recommended for production environments).
4. Check Monitoring Tool Configuration:

Ensure the monitoring tool is configured correctly for the specific server type and protocol it's trying to access. Consult the documentation for your monitoring tool for detailed configuration instructions.
5. Update Monitoring Tool (if applicable):

Outdated versions of monitoring tools might have bugs or compatibility issues. Check for updates and install the latest version if available.
6. Server-Side Issues:

In some cases, the error might originate from the server itself. Check the server logs for any relevant error messages that might provide more context about the connection issue.
Additional Tips:

If you're still encountering issues, consider searching online forums or communities for similar error messages related to your specific monitoring tool and server combination.

Contact the support team of your monitoring tool provider for further assistance. They might have additional troubleshooting steps or insights specific to their software.

By systematically checking these potential causes, you should be able to identify the root of the connection error and fix it to successfully monitor your server.

I hope the information may help you. 

[ltf]

Hi @gseckin,

Thank you for contacting us through Qlik community

First, I would suggest you to check

1. When you run test connection on the Replicate server in QEM, is the connection successful?

2. Did you run telnet from the QEM Server to ping the Replicate server to check for traffic responses?

3. Was there any patching or changes done for the server recently?

4. Please check if you have clear the browser cache because sometimes HTTP handlers did not clear which were no longer used

>> If the disconnects continue, it would be recommended to ping/telnet the connection to ensure connectivity isn't disrupted

>> If that does not helps please open case and share the repsrv logs

Let us know if you have any further questions.

Best Regards,
Faariha

[Kent_Feng]

Hi @gseckin 

Where is your screenshot from? Did you snap it from QEM's interface or from a log file? If it is from your QEM GUI you may try clear the browser cache.

[sureshkumar]

Hello @gseckin 

As mentioned earlier, the issue could be connection issue, kindly ping Replicate Server ip address in the QEM Server.

Kindly enable SERVER component to VERBOSE in QEM log and test the connection. Now check in the QEM logs why its failing.

Regards,

Suresh

[SushilKumar]

Hello @gseckin 

Request you to Check following things. These errors mainly pertain to fact that sometime QEM Send ping or check the Replicate server for status. Sometime due to response from Replicate server is not completed within defied time. hence you got these error. 

Make sure use the name in the qem monitoring which hostname or machine name shown as on the replicate server name in the upper right corner. 

make sure port 443 and 3550 and 3552 open for incoming and outgoing on participating server and on the network firewall.

Regards,

Sushil Kumar

[john_wang]

Hello @gseckin ,

Did you ever upgrade Replicate server (whatever the major changed or not)? If yes then please upgrade QEM version as well. This is one possibility.

Hope this helps.

John.