cancel
Showing results for 
Search instead for 
Did you mean: 
Reliable Contributor haaris
Reliable Contributor
Report Inappropriate Content
Message 11 of 18

Re: EPO superagent repository replication failed

Jump to solution

Hi,

I dont know what errors are,this repository was working fine but now its creating problem.Below are some error showing in the log

2018-04-05 21:35:53.754 macmnsvc(5892.5700) http_server.Info: ma_http_connection_t(000000000198F980) ma_http_connection_send_stock_response, response(403 Forbidden)
2018-04-05 21:35:53.754 macmnsvc(5892.5700) msgbus.Error: UV connect Failed - uv error <34> <no such file or directory>
2018-04-05 21:35:53.754 macmnsvc(5892.5700) msgbus.Error: Connection Failed
2018-04-05 21:35:53.754 macmnsvc(5892.5700) msgbus.Error: Unable to send the service <ma.service.logger> pipe name request msg to broker

 

There is no connection issue .I checked everything on network part.Also tried to uninstall and reinstall agent two times but still getting same error

Highlighted
McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 12 of 18

Re: EPO superagent repository replication failed

Jump to solution

What version of the agent?  It appears some of the services aren't functioning properly.  When you removed the agent and reinstalled, did you delete the directory that the repo is set to use?  If you didn't, that needs to be completely removed so the agent superagent conversion process creates that itself.

Otherwise I would recommend opening a ticket with McAfee.

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?

Reliable Contributor haaris
Reliable Contributor
Report Inappropriate Content
Message 13 of 18

Re: EPO superagent repository replication failed

Jump to solution

Version of the agent is 5.0.6.

We have not removed the directory that repository is set to use on supergene server.

You mean to say we completely need to remove the superagent replication folder and start a fresh replication on that server from start.

Reliable Contributor haaris
Reliable Contributor
Report Inappropriate Content
Message 14 of 18

Re: EPO superagent repository replication failed

Jump to solution

Hi,

So in that case I need to replicate all packages from master repository since it will be fresh and also needs to do at off hours as there will be bandwidth issue.

 

 

Reliable Contributor haaris
Reliable Contributor
Report Inappropriate Content
Message 15 of 18

Re: EPO superagent repository replication failed

Jump to solution

Hi,

Thanks a lot for instance support and providing the solution.I am really thankful to you as you provided amazing support..

I have removed the repository and created a new repository and now the replication is successful and also there is 403 forbidden error.

Excellent support...

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 16 of 18

Re: EPO superagent repository replication failed

Jump to solution

So glad that worked for you!  Glad to help.

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?

Re: EPO superagent repository replication failed

Jump to solution

Rather than create another post, I am adding here. There is a solution to another issue above this post. I have an issue with replicating agent 5.6.1U4 and now 5.6.2 to some superagent repos. I have an SR open and McAfee have looked at wiresharks. They say it is a network/firewall/proxy type issue. Our network team say it is not. Some files in the package DO replicate. Daily replication to the same SAR works fine. Replication of the same package works to other SARS. Replication of the same package to the same, failing SAR, also fails from another ePO server if I make it a SAR for that instead. This is the error seen in the local logs

2019-09-11 01:41:12.077 macmnsvc(7888.6212) http_server.Info: ma_http_connection_t(000000000244CAD0) accepting tcp connection from 10.203.195.87:62011

2019-09-11 01:41:12.077 macmnsvc(7888.6212) http_server.Debug: ma_http_connection_t(000000000244CAD0) ma_http_connection_prepare_request

2019-09-11 01:41:12.108 macmnsvc(7888.6212) http_server.Debug: SA active connection(2 / 1024)

2019-09-11 01:41:12.108 macmnsvc(7888.6212) http_server.Info: ma_http_connection_t(000000000244CFE0) ma_http_connection_send_stock_response, response(503 Service Unavailable)

2019-09-11 01:41:12.108 macmnsvc(7888.6212) http_server.Debug: ma_http_connection_t(000000000244CFE0) now associated with request_handler(0000000002753700) for url

2019-09-11 01:41:12.108 macmnsvc(7888.6212) http_server.Debug: ma_http_connection_t(000000000244CFE0) ma_uv_write_cb, status(0)

2019-09-11 01:41:12.108 macmnsvc(7888.6212) http_server.Debug: Http connection(000000000244CFE0) stopping, current state (1)

2019-09-11 01:41:12.108 macmnsvc(7888.6212) http_server.Debug: ma_http_repository_handler_t(0000000002753700) stop

2019-09-11 01:41:12.108 macmnsvc(7888.6212) http_server.Debug: Http connection(000000000244CFE0) close cb

2019-09-11 01:41:12.108 macmnsvc(7888.6212) http_server.Debug: Http connection(000000000244CFE0) timer close cb

2019-09-11 01:41:12.108 macmnsvc(7888.6212) http_server.Debug: ma_http_connection_t(000000000244CFE0)::destroy()

2019-09-11 01:41:12.108 macmnsvc(7888.6212) http_server.Debug: ma_http_repository_handler_t(0000000002753700)  release

2019-09-11 01:41:12.327 macmnsvc(7888.6212) http_server.Debug: ma_http_request_t(000000000244CCC8) authorization status (1) in spipe handler factory

2019-09-11 01:41:12.358 macmnsvc(7888.6212) http_server.Debug: ma_spipe_handler_t(00000000024400B0) start

2019-09-11 01:41:12.358 macmnsvc(7888.6212) http_server.Debug: ma_http_connection_t(000000000244CAD0) now associated with request_handler(00000000024400B0) for url

2019-09-11 01:41:13.528 macmnsvc(7888.6212) http_server.Warning: ma_http_connection(000000000244CAD0) socket read handler error: 'connection reset by peer' ECONNRESET

 

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 18 of 18

Re: EPO superagent repository replication failed

Jump to solution
2019-09-11 01:41:12.108 macmnsvc(7888.6212) http_server.Info: ma_http_connection_t(000000000244CFE0) ma_http_connection_send_stock_response, response(503 Service Unavailable) Are there errors in any other log around that time, or any services crashing or throwing exception?

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?

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