EPO 5.10 Update 13: no valid Repository, can´t rollout new agent 5.6.7

[MIJ]

Last Month we updated EPO 5.10 Update 13, today we wanted to rollout new agent version 5.7.6 to our test clients. He saw that no server updated to the new version. After litte investigation we noticed that every agent failed to download from repository. In the agent logs it says. The repository is not valid, agent failed to update because the files couldn´t be downloaded. 2022-04-28 14:49:16 I #8060 ScrptExe Failed to get the files from the server. Setting bOk to FALSE DAT,MEDDATS Updates are no problem to distribute. I our Repository damaged? Does anybody knows how to fix this?

2022-04-28 15:10:05 I #14836 curl rcv head 36 HTTP/1.1 500 Internal Server Error
2022-04-28 15:10:05 I #14836 curl rcv head 37 Date: Thu, 28 Apr 2022 13:10:05 GMT
2022-04-28 15:10:05 I #14836 curl rcv head 16 Server: Apache
2022-04-28 15:10:05 I #14836 curl rcv head 64 Strict-Transport-Security: max-age=31536000; includeSubDomains
2022-04-28 15:10:05 I #14836 curl rcv head 19 Content-Length: 1
2022-04-28 15:10:05 I #14836 curl rcv head 19 Connection: close
2022-04-28 15:10:05 I #14836 curl rcv head 45 Content-Type: text/html; charset=iso-8859-1
2022-04-28 15:10:05 I #14836 curl rcv head 2
2022-04-28 15:10:05 I #14836 curl text 21 Closing connection 0
2022-04-28 15:10:05 I #14836 curl text 45 TLSv1.2 (IN), TLS alert, close notify (256):
2022-04-28 15:10:05 I #14836 curl text 46 TLSv1.2 (OUT), TLS alert, close notify (256):
2022-04-28 15:10:05 I #14836 curl text 47 TLSv1.2 (IN), TLS handshake, Server hello (2):
2022-04-28 15:10:05 E #14836 downloader Error trace:
2022-04-28 15:10:05 E #14836 Thread [Main thread]->
2022-04-28 15:10:05 E #14836 SessMgr [SessionManager::runScript:C:\ProgramData\McAfee\Agent\update\InstallMain.McS]->
2022-04-28 15:10:05 E #14836 ScrptExe [Executing section ScriptMain]->
2022-04-28 15:10:05 E #14836 ScrptExe [Call]->
2022-04-28 15:10:05 E #14836 ScrptExe [Executing section InstallAllProducts]->
2022-04-28 15:10:05 E #14836 ScrptExe [LoopIf]->
2022-04-28 15:10:05 E #14836 ScrptExe [Executing section InstallProduct]->
2022-04-28 15:10:05 E #14836 ScrptExe [CallIf]->
2022-04-28 15:10:05 E #14836 ScrptExe [Executing section ContinueProductInstallation]->
2022-04-28 15:10:05 E #14836 ScrptExe [Call]->
2022-04-28 15:10:05 E #14836 ScrptExe [Executing section GetProductCatalog]->
2022-04-28 15:10:05 E #14836 ScrptExe [GetFiles]->
2022-04-28 15:10:05 E #14836 creposi [

[cdinet]

Is the internal server error from a distributed repository, epo or agent handler?  If epo or ah, restart apache (server service) and see if that clears that up.  Most likely that server log might be showing a failed to initialize error.  If it is a superagent, try pointing to a different repository and you then might want to open ticket to troubleshoot that repository.

[MIJ]

Hi,

we rebooted the server without any difference. The Server internal server error is still alive.

Any other idea?

[aguevara]

Just clarifying, have you rebooted the repository where those files are been downloaded from? 

[MIJ]

Yes, we only have one EPO Server. What we see is that the status of datum last repository.

Is that normal? Repository Task is running every day.

[aguevara]

probably is failing to update too, maybe it is best to get an MER from the server on log level 8 (KB56207) and open a service request with support after reproducing the problem

Regards

Alejandro

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?

[MIJ]

Thank you, I opened up a ticket with logs of server and client.