cancel
Showing results for 
Search instead for 
Did you mean: 
tassha
Level 9
Report Inappropriate Content
Message 1 of 15

McAfee Agent can't find valid repository

Jump to solution

So I uninstall the McAfee Agent using the removal tool (McAfeeEndpointProductRemoval). I have to use to tool because hosts are not communicating with ePO, so a command from the ePO console wont work and HIP is blocking the uninstall using command line and I cant turn HIP off for reasons already stated.

I reboot!

So I go to reinstall by using a framepkg.exe downloaded from the ePO server. It reinstalls just fine, or so it seems. When I click the "Collect and Send Props" it works 50% of the time. So then I try to force an update of the DAT file for VSE by opening the VSE console and right clicking Auto Update and clicking start. It will hang for a bit then give me the error "unable to contact valid repository". I notice a then a serversitelist.xml does not exist on the host.

I remove the Agent again, reboot. Reinstall using the command "framepkg.exe /install=agent /siteinfo=C:\(path to xml)\serversitelist.xml". Again appears to work, again doesnt. 

When  I review the mmcscript.log I see it is failing to download the sitestat.xml file. The only information I could find on McAfee points to proxy settings, but we dont use proxy here.

So now I am stuck. Any help??

1 Solution

Accepted Solutions
tassha
Level 9
Report Inappropriate Content
Message 9 of 15

Re: McAfee Agent can't find valid repository

Jump to solution

I couldnt make any of these solutions work so I uninstalled and reinstalled the McAfee Agent on hosts. Then, for some reason, after the first reinstall I had to install the Agent AGAIN on top of the previous install. For some reason that worked.

14 Replies

Re: McAfee Agent can't find valid repository

Jump to solution

What versions of EPO / Agent 

What does the repository list have in it EPO / Distributed repo / Local Repos.

Assuming its a 5.x agent there is a section in the Mcscript.log file starting " tying the repository xxxxxx" its worth showing us the next 20-30 lines of the log.

 

tassha
Level 9
Report Inappropriate Content
Message 3 of 15

Re: McAfee Agent can't find valid repository

Jump to solution

Hey thanks for the reply!

Ok ePO is 5.3.1 and the Agent is 5.0.6.491.

The repository list has several Agent Handlers, SADRs, and finally the ePO Server. The server actually manages 1000's of systems world wide so there are many many handlers.

I had to strip some details from the log portion requested but please see below.  Also if you could tell me what specifically you are looking for that would be great as I am trying my best to learn.

2018-08-08 12:38:56 I #7208 creposi Trying the repository ePOSA_XXXXXXXXXXX
2018-08-08 12:38:56 I #7208 downloader Downloading file from http://xxx.xxx.xxx.xxx:591/Software/SiteStat.xml to C:\WINDOWS\TEMP\SiteStat.xml
2018-08-08 12:38:56 I #7208 network URL(http://xxx.xxx.xxx.xxx:591/Software/SiteStat.xml) request submitting
2018-08-08 12:38:57 I #7208 network URL(http://xxx.xxx.xxx.xxx:591/Software/SiteStat.xml) request, failed with curl error 7, Response 0, Connect code 0,
2018-08-08 12:38:57 E #7208 downloader Error trace:
2018-08-08 12:38:57 E #7208 Thread [Main thread]->
2018-08-08 12:38:57 E #7208 SessMgr [initializeScript]->
2018-08-08 12:38:57 E #7208 creposi [setNextRepositoryToUse]->
2018-08-08 12:38:57 E #7208 creposi [downloadFile,SiteStat.xml,C:\WINDOWS\TEMP]->
2018-08-08 12:38:57 E #7208 downloader Downloading file from http://xxx.xxx.xxx.xxx:591/Software/SiteStat.xml to C:\WINDOWS\TEMP\SiteStat.xml failed.
2018-08-08 12:38:57 I #7208 downloader Downloading file from http://xxxxx.xxxx.xxx:591/Software/SiteStat.xml to C:\WINDOWS\TEMP\SiteStat.xml
2018-08-08 12:38:57 I #7208 network URL(http://xxxxx.xxxx.xxx:591/Software/SiteStat.xml) request submitting
2018-08-08 12:38:57 I #7208 network URL(http://xxxxx.xxxx.xxx:591/Software/SiteStat.xml) request, failed with curl error 6, Response 0, Connect code 0,
2018-08-08 12:38:57 E #7208 downloader Error trace:
2018-08-08 12:38:57 E #7208 Thread [Main thread]->
2018-08-08 12:38:57 E #7208 SessMgr [initializeScript]->
2018-08-08 12:38:57 E #7208 creposi [setNextRepositoryToUse]->
2018-08-08 12:38:57 E #7208 creposi [downloadFile,SiteStat.xml,C:\WINDOWS\TEMP]->
2018-08-08 12:38:57 E #7208 downloader Downloading file from http://xxxxx.xxxx.xxx:591/Software/SiteStat.xml to C:\WINDOWS\TEMP\SiteStat.xml failed.
2018-08-08 12:38:57 I #7208 downloader Downloading file from http://xxxxx.xxxx.xxx:591/Software/SiteStat.xml to C:\WINDOWS\TEMP\SiteStat.xml
2018-08-08 12:38:57 I #7208 network URL(http://xxxxx.xxxx.xxx:591/Software/SiteStat.xml) request submitting
2018-08-08 12:38:59 I #7208 network URL(http://xxxxx.xxxx.xxx:591/Software/SiteStat.xml) request, failed with curl error 6, Response 0, Connect code 0,
2018-08-08 12:38:59 E #7208 downloader Error trace:
2018-08-08 12:38:59 E #7208 Thread [Main thread]->
2018-08-08 12:38:59 E #7208 SessMgr [initializeScript]->
2018-08-08 12:38:59 E #7208 creposi [setNextRepositoryToUse]->
2018-08-08 12:38:59 E #7208 creposi [downloadFile,SiteStat.xml,C:\WINDOWS\TEMP]->
2018-08-08 12:38:59 E #7208 downloader Downloading file from http://xxxxx.xxxx.xxx:591/Software/SiteStat.xml to C:\WINDOWS\TEMP\SiteStat.xml failed.
2018-08-08 12:38:59 I #7208 creposi Repository ePOSA_XXXXXXXXXXXXX is not usable for the current update session.

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 4 of 15

Re: McAfee Agent can't find valid repository

Jump to solution

What we look for is the specific response code or error getting to a repository or pulling files from it.  In your case, you are getting curl error 6 and 7, which means couldn't resolve host and failed to connect to host respectively.  Those can occur of there are dns issues

Once test is to take the url found in the log and put it in the client browser to see if it can pull up the sitestat.xml - http://xxxxx.xxxx.xxx:591/Software/SiteStat.xml as example.

The sitestat.xml file just contains catalog version and whether the site is enabled or disabled.  If the browser is able to pull the file, is the browser set to use a proxy?  If so and you disable using the proxy, can the system still get to it?  If not, you need to add proxy info to the agent policy for the agent to use the proxy. 

If it can't get to it in browser at all, then there are some network issues that need resolved, or the server is legitimately not reachable for one reason or another.

I would also suggest testing the 5.5.1 or 5.5.2 agent, as the 5.0.6 agent had some issues and other hotfixes beyond what version you have.

 

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?

tassha
Level 9
Report Inappropriate Content
Message 5 of 15

Re: McAfee Agent can't find valid repository

Jump to solution

I can get to that repository via web browser which is good.


I know we wont be enabling proxy and we dont need it on other hosts that dont have proxy enabled.

Also since we are on a DoD network I cant just use a newer version of Agent.

McAfee Employee rgc
McAfee Employee
Report Inappropriate Content
Message 6 of 15

Re: McAfee Agent can't find valid repository

Jump to solution

I suspect, there is a problem on the source side [SADR repository].

Moreover, as per your statement sitestat.xml is able to download through a browser.

To confirm this, we need to follow a few steps, 

 

1. Create a new MA -> repository policy & enable ONLY ePO from the list and fallback as McAfee HTTP and assign this policy to the client machine and enforce with confirmation from VSE console it updated


2. Enable debug logging for MASVC & McScript as per KB82170 for one problem machine & ensure it is writing in debug from the log, by doing collect & send props from agent monitor.

 

3. Create a new test product update task with customized name & schedule it with Run immediately  & do the ASCI from agent monitor and see what it reflects from agent monitor.

If this fails, immediately copy the McAfee\Agent\logs folder to desktop with the time stamp and the task name enforced.

This logs folder will give us more insight into debugging to find the cause.

 

NOTE: If the dat update is successful with reaching ePO, this clarifies there is no problem with MA / VSE on client machine with the scheduler component and update invoke is working.

 

Then, the next action plan to enable the debugging on super agent & verify it is with Lazy Caching / Replication [ENabled BOTH not recommended].

We need to check with the new task by changing policy to contact only super agent & re-initiate with run immediately, by enabled debug on client and superagent [MA debugging] and capture the logs from both the sides after issue reproduced.

If possible, run wireshark from super agent and client at the same time issue re-produced and get all data to find the cause.

 

 

 


Raghavendra GC
McAfee Technical Support – APAC
Customer Success Group
www.mcafee.com

Re: McAfee Agent can't find valid repository

Jump to solution

I agree with RGC a connectivity issue is indicated to that repository.

When 1 repo fails the agent should try the next and yours has failed them all. So RGC is wanting to test EPO only. 

However I have a couple of other questions.

1. With agent 5.0.x Peer 2 Peer was enabled by Default do you have it enabled or disabled.

2. Moving down the log ( Search for Trying ) to where it is trying EPO does it successfully download the sitestat.xml from EPO and if so does it also successfully download replica.log and catalog.z which are the next 2 required files.

3. In the Agent Repository policy there is a list of repositories which are either global ( Managed ) or local ( Unmanaged ). The local repositories are editable and if you edit them you can see what Type they are. They can be set to FTP or HTTP or UNC or Local. Do you have any that are set to local. If so copy the policy and change them to UNC and test on a machine with it set to UNC.

 

Regards Captain 

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 8 of 15

Re: McAfee Agent can't find valid repository

Jump to solution

Can other systems update from the same repository?  If peer to peer is enabled, test by disabling it.  We are seeing some issues with update failures with that enabled.

For your SADR's, you can look at the macmnsvc log to see if the server is having any issues delivering up content.

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?

tassha
Level 9
Report Inappropriate Content
Message 9 of 15

Re: McAfee Agent can't find valid repository

Jump to solution

I couldnt make any of these solutions work so I uninstalled and reinstalled the McAfee Agent on hosts. Then, for some reason, after the first reinstall I had to install the Agent AGAIN on top of the previous install. For some reason that worked.

BabuC
Level 7
Report Inappropriate Content
Message 10 of 15

Re: McAfee Agent can't find valid repository

Jump to solution

Hi, Are you using Windows10 OS with Dual Network adapters?

If so, Please make sure installation steps are dones via Primary network only, Installation on Secondary network may have problem like this so try performing installation only on primary network and check the Agent status monitor window for the sucessfull steps.

Thanks.

More McAfee Tools to Help You

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community