Jump to content

Mirrortool updating both repository and updates fail


Recommended Posts

  • Most Valued Members

Hi,

I don't know if these two issues are one in the same; but I'm having difficulties with both the updates and repository mirroring.

Firstly, the repository mirroring script fails with the following error:

Quote


Error: Downloading file : http://repository.eset.com/v1/com/eset/apps/business/es/ms_sharepoint/v6/6.5.15015.2/eshp_nt32_enu.msi failed with : GetFile: Host 'repository.eset.com' not found [error code: 20002]
Downloading file : http://repository.eset.com/v1/com/eset/apps/business/esm/linux/v1/1.6.10/esm_x86_64_enu.bin failed with : GetFile: Host 'repository.eset.com' not found [error code: 20002]

 

It's ok with the other files.  Just not this one.  

With the updates, I get:

Quote


Error: Perform full mirror failed with error: Undocumented serious error. Error code is: 4122
Error occured.

 

There's no apparent errors shown.

 

Any help appreciated.

Ed

Link to comment
Share on other sites

  • ESET Staff

Could you possibly verify there is no problem with internet connectivity? Errors from download of repository packages indicates some network related issue, maybe even DNS related . Is it possible to download manually file from repository.eset.com mentioned in error?
Unfortunately I cannot currently verify error generated during creation of update mirror, but there is a high probability it is also network-related -> might be clearly visible from network capture, for example using tools like wireshark.

Link to comment
Share on other sites

  • Most Valued Members

@MartinK  Thanks for the suggestion.  I think you're right in that there is something not quite right with the network.  I can download that file manually so I'm sure why it's doing that it if can download the other updates/repository files.  

Link to comment
Share on other sites

  • Most Valued Members

@MartinK are there built in retries in the MirrorTool?  Like after going through the list of files required to be downloaded, MirrorTool would go over the failed downloads again.   I've tried running mirrortool on two different linux systems and both give me different file failures, so I'm guessing some transient network hiccups.

Btw, how do I find the version of MirrorTool?

Thanks

 

Edited by ewong
added another question
Link to comment
Share on other sites

  • ESET Staff
19 hours ago, ewong said:

@MartinK are there built in retries in the MirrorTool?  Like after going through the list of files required to be downloaded, MirrorTool would go over the failed downloads again.   I've tried running mirrortool on two different linux systems and both give me different file failures, so I'm guessing some transient network hiccups.

Btw, how do I find the version of MirrorTool?

Thanks

 

We do currently track improvement for reporting version - which is currently not available especially on Linux. On Windows, there is at least possibility to check version as shown in executable file details.

If I recall correctly, creating update mirror does not uses any retry mechanisms, but downloading of repository packages should use some basic retry mechanisms and also "continuation" type of download, which should be able to continue failed download and re-use already downloaded data.
Regardless of that, MirrorTool was designed in a way that it should download only incremental changes, so it might be called repeatedly. Or problem is that even repeated calls which are supposed to not download much data are failing?
Also note there is possibility to use HTTP proxy in between MirrorTool and internet as an additional caching layer, which might helps in case of network instability and often failures.

Link to comment
Share on other sites

  • Most Valued Members
4 hours ago, MartinK said:

We do currently track improvement for reporting version - which is currently not available especially on Linux. On Windows, there is at least possibility to check version as shown in executable file details.

If I recall correctly, creating update mirror does not uses any retry mechanisms, but downloading of repository packages should use some basic retry mechanisms and also "continuation" type of download, which should be able to continue failed download and re-use already downloaded data.
Regardless of that, MirrorTool was designed in a way that it should download only incremental changes, so it might be called repeatedly. Or problem is that even repeated calls which are supposed to not download much data are failing?
Also note there is possibility to use HTTP proxy in between MirrorTool and internet as an additional caching layer, which might helps in case of network instability and often failures.

Hi @MartinK, 

A workaround that I noticed was downloading whatever version that's online and find the hash of both.  Though this doesn't tell which is newest, at least I know it's different and probably get the latest off the site.

As for the http proxy,  I'll have a look at that option.  Thanks!

Edmund

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...