RCC connection errors

kb · Post by kb » Wed Jan 13, 2021 2:45 am

Since updating HostMonitor to v12.64 we get the message "Error(RR): Cannot read data" when connecting via RCC for the first time in a while.
Disconnecting and reconnecting without closing RCC then works, any subsequent logins within a short time frame work as well.

HostMonitor 12.64 running on Windows 2019
RCC 7.64 running on Windows 10
Both OS are fully patched

RCC is started with the parameters "-uniqueprofiles -storepassword -autoconnect"

Any ideas?

KS-Soft · Post by **KS-Soft** » Wed Jan 13, 2021 3:02 am

Slow network with too short timeout?
What timeout have you set for RCC connection?

May be HostMonitor system busy and does not respond well?
Have you checked resource usage (CPU load, memory usage, handles)?

Does HostMonitor show some errors (menu View->Auditing Tool)?

Regards
Alex

kb · Post by kb » Wed Jan 13, 2021 3:24 am

Thanks for your fast reply.

Clients and server have a 1G connection and the load on the server is pretty low. We have HostMonitor running on this virtual host for 2 months now and did not have the problem before v12.64.
Auditing does not show any errors, just a few warnings about weak passwords (remote access is purely internal, IT only) and about backup location (server VM is snapshotted daily).

I set the RCC/RCI timeout from 1 second to 5 seconds and we will monitor whether the error persists.

Thanks again and have nice day.

KS-Soft · Post by **KS-Soft** » Wed Jan 13, 2021 6:45 am

We don't see how HostMonitor update can lead to such problem.
What version have you used before update?
May be you changed some settings, e.g. added SLA reports with charts or started more RCC/Web Service clients?

1 sec is not enough in many cases.

Regards
Alex

kb · Post by kb » Wed Jan 13, 2021 6:50 am

We came from version 12.60.
The only change I can remember is using a different SQL ODBC as backup log, which works flawlessly. That was changed right after updating.

So far the timeout change seems to have fixed the problem.
I will reply here if the error returns.

Thanks.

KS-Soft · Post by **KS-Soft** » Wed Jan 13, 2021 8:04 am

We change nothing related to HostMonitor<->RCC communication since version 12.60.

The only change I can remember is using a different SQL ODBC as backup log, which works flawlessly

What exactly ODBC driver do you use?
Some drivers have many bugs and lead to various errors (especially Oracle drivers)

Regards
Alex

kb · Post by kb » Thu Jan 14, 2021 1:52 am

We are using Windows Server 2019 builtin Microsoft SQL 10.00.17763.01 againt SQL 2014.
So far everything is fine with the raised timeout.