Jump to content

Antivirus client update inconsistency


solas
 Share

Recommended Posts

I am still battling with client update inconsistency.  Sometimes they fail and then I try again a few minutes later and they are successful without any changes being made.  Agent trace logs are showing the messages below  and the ESMC console shows Failed to synchronize package repository. See trace message for more details.  The name of the server resolves accurately on the client and I have windows firewall rules to allow the ESMC server on all ports.

2019-10-18 17:00:44 Error: CReplicationModule [Thread 167c]: CAgentReplicationManager: Replication finished unsuccessfully with message: InitializeConnection: Initiating replication connection to 'host: "era001.corp.company.com" port: 2222' failed with: Request: Era.Common.Services.Replication.CheckReplicationConsistencyRequest on connection: host: "era001.corp.company.com" port: 2222 with proxy set as: Proxy: Connection: :3128, Credentials: Name: , Password: ******, Enabled:0, EnabledFallback:1, failed with error code: 2, error message:  Failed to create subchannel, and error details: Replication details: [Task: CReplicationConsistencyTask, Scenario: Automatic replication (REGULAR), Connection: era001.corp.company.com:2222, Connection established: false, Replication inconsistency detected: false, Server busy state detected: false, Realm change detected: false, Realm uuid: 79983a6a-b3d1-4533-9469-4bcea77e58bd, Sent logs: 0, Cached static objects: 50, Cached static object groups: 9, Static objects to save: 0, Static objects to delete: 0, Modified static objects: 0]
2019-10-18 17:01:44 Error: CSystemConnectorModule [Thread 1690]: CDeviceSnapshotWinLoaderUtils::ReadDiskDriveIDs: calling funtion=[CreateFile] for volume=[\\?\Volume{258f614d-f0e0-11e9-9fe9-9cebe8762ed0}] failed, error=[5]
2019-10-18 17:01:44 Error: CNetworkGrpcModule [Thread 31a0]: GRPC:Failed to resolve: era001.corp.company.com:2222
2019-10-18 17:01:44 Error: CReplicationModule [Thread 167c]: InitializeConnection: Initiating replication connection to 'host: "era001.corp.company.com" port: 2222' failed with: Request: Era.Common.Services.Replication.CheckReplicationConsistencyRequest on connection: host: "era001.corp.company.com" port: 2222 with proxy set as: Proxy: Connection: :3128, Credentials: Name: , Password: ******, Enabled:0, EnabledFallback:1, failed with error code: 2, error message: Failed to create subchannel, and error details: 
2019-10-18 17:01:44 Warning: CReplicationModule [Thread 167c]: InitializeConnection: Not possible to establish any connection (Attempts: 1)
2019-10-18 17:01:44 Error: CReplicationModule [Thread 167c]: InitializeFailOverScenario: Skipping fail-over scenario (stored replication link is the same as current)
2019-10-18 17:01:44 Error: CReplicationModule [Thread 167c]: CAgentReplicationManager: Replication finished unsuccessfully with message: InitializeConnection: Initiating replication connection to 'host: era001.corp.company.com port: 2222' failed with: Request: Era.Common.Services.Replication.CheckReplicationConsistencyRequest on connection: host: "era001.corp.company.com" port: 2222 with proxy set as: Proxy: Connection: :3128, Credentials: Name: , Password: ******, Enabled:0, EnabledFallback:1, failed with error code: 2, error message:  Failed to create subchannel, and error details: Replication details: [Task: CReplicationConsistencyTask, Scenario: Automatic replication (REGULAR), Connection: era001.corp.company.com:2222, Connection established: false, Replication inconsistency detected: false, Server busy state detected: false, Realm change detected: false, Realm uuid: 79983a6a-b3d1-4533-9469-4bcea77e58bd, Sent logs: 0, Cached static objects: 50, Cached static object groups: 9, Static objects to save: 0, Static objects to delete: 0, Modified static objects: 0]

 

Edited by solas
Link to comment
Share on other sites

  • ESET Staff

Hello @solas,

Do you refer to "updates" (module updates of products) or to "upgrades" (installation of a new version of agent / endpoint).  As package repository is needed only for the second one. 

Thanks,

Michal

Link to comment
Share on other sites

  • ESET Staff

The error you have passed is not from the failure of the particular component upgrade task, rather from the failed replication attempts. How is your repository configured in both agent policy and server settings? Did you configure it for autoselect, or you specified a specific repository address ? 

Link to comment
Share on other sites

  • ESET Staff

As already mentioned, there are multiple critical/fatal errors in trace log you provided. For example:

Error: CNetworkGrpcModule [Thread 31a0]: GRPC:Failed to resolve: <esmccompanyhostname>.com:2222

indicates that it is not possible to resolve DNS name of where ESMC is supposed to be running.

Link to comment
Share on other sites

On 10/23/2019 at 10:59 AM, MichalJ said:

The error you have passed is not from the failure of the particular component upgrade task, rather from the failed replication attempts. How is your repository configured in both agent policy and server settings? Did you configure it for autoselect, or you specified a specific repository address ? 

The repository is set for autoselect

23 hours ago, MartinK said:

As already mentioned, there are multiple critical/fatal errors in trace log you provided. For example:


Error: CNetworkGrpcModule [Thread 31a0]: GRPC:Failed to resolve: <esmccompanyhostname>.com:2222

indicates that it is not possible to resolve DNS name of where ESMC is supposed to be running.

While the log says that it cannot be resolved, I am able to nslookup the hostname of the server from the client and it responds correctly.  I can also nslookup the name of the client from the ESMC and it responds correctly.  I have firewall rules to allow the ip of the ESMC inbound on all ports.  The client is currently reporting in tot he ESMC just fine and has the most up to date version of the agent.  I am just unable to install the latest AV client. 

Edited by solas
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...