IMPORTANT ANNOUNCEMENT: On May 6, 2024, Carbon Black User eXchange (UeX) and Case Management will move to a new platform!
The Community will be in read-only mode starting April 19th, 7:00 AM PDT. Check out the blog post!
You will still be able to use the case portal to create and interact with your support cases until the transition, view more information here!

Server Communication Status shows error and future timestamp

Server Communication Status shows error and future timestamp

Version

Cb Response 5.x and 6.x

Issue

Error code: XXX at <Future Date> being shown in the Server Communication Status section of the Server Dashboard

Symptoms

The XXX error code number depends on the failure and may need investigation, however, the <Future Date> timestamp is cause for concern since that timestamp is taken from the server (master in a cluster) and it will not clear until the <Future Date> has passed.

Cause

Issue caused by incorrect Response server/cluster timestamp.  It is critically important for the server/cluster to maintain correct time.

Solution

Cleanly stop the Response server/cluster and update the server (master and minions in case of a cluster) time if it is not correct.  We recommend that the servers been time synced via ntp. 

To clear the future date error, execute the following as root on the Response server (against master in a cluster), the servers must be running prior to executing this:

psql -d cb -p 5002 -c "delete from allianceclient_comm_history where timestamp>now()"

Labels (1)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎05-04-2017
Views:
781
Contributors