cancel
Showing results for 
Search instead for 
Did you mean: 

Agents unable to use Distributed Repository

Jump to solution

Hello McAfee community!  I'm having an issue with one of my SADRs.  It's replicating normally and everything looks okay from the ePO, but when I force an agent to use this repository, it always fails to download the sitelist.xml.  I'm going to include a snippet from the logs, any help decoding these errors would be greatly appreciated!

2019-09-19 16:06:55 I #5724 creposi Trying the repository ePOSA_CO1IMGTWMSA0001
2019-09-19 16:06:55 I #5724 downloader Downloading file from http://x.x.x.x:8081/Software/SiteStat.xml to C:\Windows\TEMP\SiteStat.xml with timeout 18000
2019-09-19 16:16:07 I #896 msgbus File watcher callback invoked on broker config change, file name <config.ini>
2019-09-19 16:16:07 I #896 msgbus File watcher callback invoked on broker config change, file name <config.ini>
2019-09-19 16:16:07 I #896 msgbus File watcher callback invoked on broker config change, file name <config.ini>
2019-09-19 16:16:07 I #896 msgbus File watcher callback invoked on broker config change, file name <config.ini>
2019-09-19 16:16:07 I #896 msgbus File watcher callback invoked on broker config change, file name <config.ini>
2019-09-19 16:16:08 I #896 msgbus Received Timer event to read msgbus config file
2019-09-19 16:16:56 I #5724 network URL(http://x.x.x.x:8081/Software/SiteStat.xml) request, failed with curl error 28, Response 0, Connect code 0,
2019-09-19 16:16:56 I #5724 curl text 23 Trying x.x.x.x...
2019-09-19 16:16:56 I #5724 curl text 16 TCP_NODELAY set
2019-09-19 16:16:56 I #5724 curl text 52 Connected to x.x.x.x (x.x.x.x) port 8081 (#0)
2019-09-19 16:16:56 I #5724 curl snd head 101 GET /Software/SiteStat.xml HTTP/1.1 Host: x.x.x.x:8081 User-Agent: McAfee Agent Accept: */*
2019-09-19 16:16:56 I #5724 curl text 75 Operation too slow. Less than 1 bytes/sec transferred the last 600 seconds
2019-09-19 16:16:56 I #5724 curl text 21 Closing connection 0
2019-09-19 16:16:56 E #5724 downloader Error trace:
2019-09-19 16:16:56 E #5724 Thread [Main thread]->
2019-09-19 16:16:56 E #5724 SessMgr [initializeScript]->
2019-09-19 16:16:56 E #5724 creposi [setNextRepositoryToUse]->
2019-09-19 16:16:56 E #5724 creposi [downloadFile,SiteStat.xml,C:\Windows\TEMP]->
2019-09-19 16:16:56 E #5724 downloader Downloading file from http://x.x.x.x:8081/Software/SiteStat.xml to C:\Windows\TEMP\SiteStat.xml failed.
2019-09-19 16:16:56 I #5724 downloader Downloading file from http://co1imgtwmsa0001.mgt.afsiep.net:8081/Software/SiteStat.xml to C:\Windows\TEMP\SiteStat.xml with timeout 18000
2019-09-19 16:16:56 I #5724 network URL(http://co1imgtwmsa0001.mgt.afsiep.net:8081/Software/SiteStat.xml) request, failed with curl error 0, Response 404, Connect code 0,
2019-09-19 16:16:56 I #5724 curl text 23 Trying x.x.x.x...
2019-09-19 16:16:56 I #5724 curl text 16 TCP_NODELAY set
2019-09-19 16:16:56 I #5724 curl text 72 Connected to co1imgtwmsa0001.mgt.afsiep.net (x.x.x.x) port 8081 (#0)
2019-09-19 16:16:56 I #5724 curl snd head 121 GET /Software/SiteStat.xml HTTP/1.1 Host: co1imgtwmsa0001.mgt.afsiep.net:8081 User-Agent: McAfee Agent Accept: */*
2019-09-19 16:16:56 I #5724 curl rcv head 24 HTTP/1.1 404 Not Found
2019-09-19 16:16:56 I #5724 curl rcv head 41 Content-Type: text/plain; charset=utf-8
2019-09-19 16:16:56 I #5724 curl rcv head 20 Content-Length: 13
2019-09-19 16:16:56 I #5724 curl rcv head 2
2019-09-19 16:16:56 I #5724 curl text 65 Connection #0 to host co1imgtwmsa0001.mgt.afsiep.net left intact
2019-09-19 16:16:56 E #5724 downloader Error trace:
2019-09-19 16:16:56 E #5724 Thread [Main thread]->
2019-09-19 16:16:56 E #5724 SessMgr [initializeScript]->
2019-09-19 16:16:56 E #5724 creposi [setNextRepositoryToUse]->
2019-09-19 16:16:56 E #5724 creposi [downloadFile,SiteStat.xml,C:\Windows\TEMP]->
2019-09-19 16:16:56 E #5724 downloader Downloading file from http://co1imgtwmsa0001.mgt.afsiep.net:8081/Software/SiteStat.xml to C:\Windows\TEMP\SiteStat.xml failed.

 

1 Solution

Accepted Solutions
Highlighted

Re: Agents unable to use Distributed Repository

Jump to solution

Thank you all for your replies and support.  I believe I have found what is causing this issue and wanted to post my findings here for anyone else who might be having the same issue.

 

Apparently there were open connections building on my repository.  When my agent tried to use this repo, it couldn't accept the connection and responded with a 403 error.  I ran a netstat -a on confirmed lots of connections with a CLOSED_WAIT status.  I stopped the McAfee Agent services, then restarted and confirmed the connections were gone.

My test agent was then able to use this repository.  I still need to watch for these connections to accumulate and then find out why that is happening, but that is a separate issue.  

6 Replies
McAfee Employee AdithyanT
McAfee Employee
Report Inappropriate Content
Message 2 of 7

Re: Agents unable to use Distributed Repository

Jump to solution

Hi @Surrogate77 

Thank you for your post here. Curl error 28 seems to point out time out failure here. I see 404 responses as well. I am wondering what happens when you try to reach out to the shared directory from this machine and view sitestat.xml using one of the URL (http://x.x.x.x:8081/Software/SiteStat.xml) in the log?

Also, I would recommend you to verify if the port is open by performing a telnet to the distributed repository Server. May I also confirm if there are nay machines that are able to successfully update from this Distributed repository. Please let us know how this goes!

Was my reply helpful?
If you find this post useful, Please give it a Kudos! Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!

Thanks and regards,
Adithyan T

Re: Agents unable to use Distributed Repository

Jump to solution

Hello Adithyan!

This first pic is looking at the URL from chrome and the second shows that 8081 is open using portqry from my client to the SADR.Capture.PNG

McAfee Employee AdithyanT
McAfee Employee
Report Inappropriate Content
Message 4 of 7

Re: Agents unable to use Distributed Repository

Jump to solution

Hi @Surrogate77 

Excellent! Thanks for your quick update. So there is no issue with reachability of the SADR from the endpoint. Do you have any endpoint Firewall or Defender Firewall active on either of the machines?

Also, as mentioned on my previous reply, do we have any other machine that can connect and fetch updates from this SADR?

Form what I see, It is not the connection but the download that seems to be interrupted. Since the SADR is being accessed by http here, does the download go through any scanning by an endpoint firewall or get routed to a gateway firewall before reaching the machines? I am suspecting issue from network end here. However if these don't help, I would recommend contacting our technical Support for raising a Service Request.

Was my reply helpful?
If you find this post useful, Please give it a Kudos! Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!

Thanks and regards,
Adithyan T
McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 5 of 7

Re: Agents unable to use Distributed Repository

Jump to solution

This seems to be the biggest problem I see.  Curl 28 is an operation timeout error, which is verified by the lines that follow.

2019-09-19 16:16:08 I #896 msgbus Received Timer event to read msgbus config file
2019-09-19 16:16:56 I #5724 network URL(http://x.x.x.x:8081/Software/SiteStat.xml) request, failed with curl error 28, Response 0, Connect code 0,
2019-09-19 16:16:56 I #5724 curl text 23 Trying x.x.x.x...
2019-09-19 16:16:56 I #5724 curl text 16 TCP_NODELAY set
2019-09-19 16:16:56 I #5724 curl text 52 Connected to x.x.x.x (x.x.x.x) port 8081 (#0)
2019-09-19 16:16:56 I #5724 curl snd head 101 GET /Software/SiteStat.xml HTTP/1.1 Host: x.x.x.x:8081 User-Agent: McAfee Agent Accept: */*
2019-09-19 16:16:56 I #5724 curl text 75 Operation too slow. Less than 1 bytes/sec transferred the last 600 seconds

You should be able to get to this in the browser:  http://x.x.x.x:8081/Software/SiteStat.xml.  If you can't, then there are network or sadr problems.

You can view the macmnsvc log on the sadr for any errors on the agent side.  That is located in c:\programdata\mcafee\agent\logs.

Be sure to also sanitize your entire log 🙂

2019-09-19 16:16:56 I #5724 curl text 72 Connected to co1imgtwmsa0001.mgt.afsiep.net (x.x.x.x) port 8081 (#0)
2019-09-19 16:16:56 I #5724 curl snd head 121 GET /Software/SiteStat.xml HTTP/1.1 Host: co1imgtwmsa0001.mgt.afsiep.net:8081 User-Agent: McAfee Agent Accept: */*
2019-09-19 16:16:56 I #5724 curl rcv head 24 HTTP/1.1 404 Not Found

The 404 error could be an issue with the agent (the log would show that) or the file isn't actually there.

 

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?

Highlighted

Re: Agents unable to use Distributed Repository

Jump to solution

Thank you all for your replies and support.  I believe I have found what is causing this issue and wanted to post my findings here for anyone else who might be having the same issue.

 

Apparently there were open connections building on my repository.  When my agent tried to use this repo, it couldn't accept the connection and responded with a 403 error.  I ran a netstat -a on confirmed lots of connections with a CLOSED_WAIT status.  I stopped the McAfee Agent services, then restarted and confirmed the connections were gone.

My test agent was then able to use this repository.  I still need to watch for these connections to accumulate and then find out why that is happening, but that is a separate issue.  

McAfee Employee AdithyanT
McAfee Employee
Report Inappropriate Content
Message 7 of 7

Re: Agents unable to use Distributed Repository

Jump to solution

Hi @Surrogate77 

Thank you for letting us know the solution. This helps other community members if they come across similar issues! Kudos to you!

Was my reply helpful?
If you find this post useful, Please give it a Kudos! Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!

Thanks and regards,
Adithyan T
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