"The remote collector has not acknowledged 2284010 bytes of data sent by the local agent over the secure connection."

+1 vote
asked Sep 6 in EventSentry by msimmons13 (570 points)
I've been receiving a few of these lately, not sure if I should be concerned or not. The full message is:

The remote collector has not acknowledged 2284010 bytes of data sent by the local agent over the secure connection. This may indicate high latency or an issue with the remote collector, it's recommended that you ensure that data sent from this host is present in the web reports. The agent will now throttle data sent to the collector until the collector acknowledges receipt of sent data.

Please let me know if there is more data I can provide to assist in assisting,

Thanks!

1 Answer

+1 vote
answered Sep 6 by Ingmar (5,820 points)
selected Sep 10 by msimmons13
 
Best answer
The client to collector transmission protocol was slightly adapted in 3.5 to allow for a faster throughput, in most cases this message can be ignored. Repeated occurrence may indicate a connectivity problem though.

Are the agents where this is logged on the same subnet as the collector?

Are multiple agents logging this, or only a specific agent?
commented Sep 7 by Ingmar (5,820 points)
OK great. Please open the management console and then follow these steps:

1. Expand the "Actions" node and click the first action. If it has the "Use Collector" check box checked, then uncheck that box. This will configure the action NOT to use the collector.
2. Repeat this for all the other actions
3. Click on "Services" and stop the Agent and Collector
4. Click on the "Collector" icon (home -> collector) and change the startup type to Manual (click on the "Manual" button) to ensure the collector won't start after the next reboot.
5. Save the configuration
6. Click on "Services" again but this time start the agent again
7. Everything should work as before, except that the agent won't be using the collector anymore. I would recommend you test the basic functionality with a test event or similar.

Let me know if you have any questions!
commented Sep 7 by msimmons13 (570 points)
Thanks, when I went to do that I saw there was an update. I did the update, and your instructions, and now I'm getting the following:


    The following errors or warnings occurred within the last 5 minutes while communicating with the database:

Primary Database: OdbcExpandError: [42703] ERROR: column "checksum" of relation "espstracking" does not exist;
Error while executing the query (7)
Primary Database: OdbcExpandError: [23503] ERROR: insert or update on table "esperformance" violates foreign key constraint "esperformance_instance_fkey";
Error while executing the query (7)
Primary Database: OdbcExpandError: [42P01] ERROR: relation "eventsentry.eschecksum" does not exist;
Error while executing the query (7)
Primary Database: OdbcExpandError: [42703] ERROR: column "tsadded" of relation "esperformanceinstance" does not exist;
Error while executing the query (7)
Primary Database: OdbcExpandError: [23503] ERROR: insert or update on table "esperformancemapping" violates foreign key constraint "esperformancemapping_instance_fkey";
Error while executing the query (7)
Primary Database: OdbcExpandError: [42703] ERROR: column "tsadded" of relation "esperformanceinstance" does not exist;
Error while executing the query (7)
Primary Database: OdbcExpandError: [42703] ERROR: column "tsadded" of relation "esperformanceinstance" does not exist;
Error while executing the query (7)
Primary Database: OdbcExpandError: [42703] ERROR: column "checksum" of relation "espstracking" does not exist;
Error while executing the query (7)
Primary Database: OdbcExpandError: [42P01] ERROR: relation "eventsentry.eschecksum" does not exist;
Error while executing the query (7)
Primary Database: OdbcExpandError: [23503] ERROR: insert or update on table "esperformance" violates foreign key constraint "esperformance_instance_fkey";
Error while executing the query (7)

 
     If you have Extended Error Logging enabled, event ID 532 indicates the agent can connect to the database but cannot write data. Event 530 is enabled by default and indicates that the agent cannot connect to the database.
commented Sep 7 by Ingmar (5,820 points)
It looks like the database schema wasn't updated when you upgraded to v3.5. I'm not sure how that is possible, since the database update routine is launched automatically after the setup has completed.

To update the database please do the following:

1. Open the management console
2. Under actions, locate the database action
3. On the action dialog, click the "Initialize or Update Database" button.

After that completes successfully, navigate to "Services" on the top left and restart all currently running services - that should take care of the issues. Please let us know if that resolves it.
commented Sep 7 by msimmons13 (570 points)
Everything appears to be correct now, thank you for all the assistance!
commented Sep 10 by Ingmar (5,820 points)
Great, thanks for letting us know. Please vote correct answers up - thank you!
Welcome to EventSentry Q&A, where you can ask questions and receive answers from other members of the community.
...