cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Fadz
Level 8
Report Inappropriate Content
Message 1 of 4

Failed to replicate

Jump to solution

Hi

At distributed repository status , i got 13 Super Agent that fail.

Status : Last replication failed & Need first update.

Is there any workaround that i should do to get all 13 Super Agent successfully get update from my ePO?
The scenario is Super Agent is on MAN Scale.

I did ping check : Some is success and some are not .
Wake up agent: Majority is failed (Unknown error contacting agent).

Sorry for having bad english.

 

 

1 Solution

Accepted Solutions
McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 3 of 4

Re: Failed to replicate

Jump to solution

Has it ever worked?  When you created the superagents, did you pre-create the directory for the repo on the clients or did the superagent conversion process do that?  If you created them ahead of time,  that can cause failures.  Also, make sure lazy caching is not enabled in the agent policy if you are going to replicate.  You should use only one or the other.  As an alternative, you can try not replicating and enable lazy caching to see if the agents are able to pull content from the master repository.

On the sa repo, the macmnsvc log will show errors with the superagent functionality.  You would look for the time frame of replication attempt and search for a connection from the epo server.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

3 Replies
McAfee Employee hem
McAfee Employee
Report Inappropriate Content
Message 2 of 4

Re: Failed to replicate

Jump to solution

When ePO tries to replicate. It will connect SA repository on port 8081 with FQDN (can be verified in EpoApsvr.log). Make sure that we are able to connect to repository and should be able to connect on port 8081.

Was my reply helpful?

If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?please select Accept as Solution in my reply and together we can help other members?
McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 3 of 4

Re: Failed to replicate

Jump to solution

Has it ever worked?  When you created the superagents, did you pre-create the directory for the repo on the clients or did the superagent conversion process do that?  If you created them ahead of time,  that can cause failures.  Also, make sure lazy caching is not enabled in the agent policy if you are going to replicate.  You should use only one or the other.  As an alternative, you can try not replicating and enable lazy caching to see if the agents are able to pull content from the master repository.

On the sa repo, the macmnsvc log will show errors with the superagent functionality.  You would look for the time frame of replication attempt and search for a connection from the epo server.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Fadz
Level 8
Report Inappropriate Content
Message 4 of 4

Re: Failed to replicate

Jump to solution

Now it worked successfully .

The previous vendor pre-create the directory and some actually is not SA by right.

 

Thank you all 

More McAfee Tools to Help You
  • Subscription Service Notification (SNS)
  • How-to: Endpoint Removal Tool
  • Support: Endpoint Security
  • eSupport: Policy Orchestrator