Local Server Mirror Update NOD32 v2.7
Click the slider bar next to Create update mirror to enable it. We recommend that you also set a Username and Password for clients to access the update mirror. Click OK when you are finished.
Local Server Mirror Update NOD32 v2.7
Copy the IP address or fully qualified domain name (FQDN) of the client computer where you created the update mirror. You will use this information to configure policy settings so that other clients will download updates from this mirror. Proceed to part II when you have copied this information.
Under Modules Updates, deselect the check box next to Choose automatically. In the Custom server field, type the IP address of the client where you created a mirror, followed by a colon and the port used (for example, :2221). If you defined a username and password for clients to access the mirror, type them into the appropriate fields.
There is a local mirror update setting in ESET Endpoint for Android policy in ERA, how to use it (hxxp://mirror server ip:2221)? Update from mirror created using ESET Endpoint AV in Windows? Seems doesn't work
In this example, we will modify an existing policy. If you are creating a new policy, you must enter information about your server (mirror server IP address, for example). If you are using HTTP Proxy for distributing updates, you do not need to specify any of this information in your policy.
You just needed to update ca-certificates package. Before that just disable all repos with https that are failing.That's why solution with commenting mirrorlist or using http instead https would work also.
ESET Smart Security Business Edition and ESET NOD32 Antivirus Business Edition client solutions can be configured to store copies of virus signature update files, much like a standard Mirror server. These virus signature files can then be used to update other workstations that are running ESET Smart Security or ESET NOD32 Antivirus. A version 4.x or version 3.0 ESET client solution that is configured as a Mirror server cannot be used to update ESET NOD32 Antivirus 2.7 clients.
From this point you can configure the Mirror to provide updates via an internal HTTP server, or via a shared network folder. To provide updates via an internal HTTP server, perform the following steps directly below (to provide updates via a shared network folder, click here):
If you are looking for instructions on configuring an ESET client solution to access a Mirror server for virus signature and program component updates, please see sections 3.2 and 5.1 in the ESET Remote Administrator Guide.
It depends on the latency and performance between the VDA and the file server. Apps assume that AppData is local and thus they do not optimize their I/O to AppData. When I tried in the past the performance was not good.
Quick fix:[me@work]$ sudo sed -i 's/serverURL=https:/serverURL=http:/g' /etc/sysconfig/rhn/up2date; sudo yum update yum* nss* ; sudo sed -i 's/serverURL=http:/serverURL=https:/g' /etc/sysconfig/rhn/up2date
$ yum update yumLoaded plugins: product-id, security, subscription-managerSetting up Update Processrhel-6-server-eus-rpms 3.5 kB 00:00rhel-6-server-eus-rpms/primary_db 48 MB 00:04rhel-6-server-rpms 3.5 kB 00:00rhel-6-server-rpms/primary_db 51 MB 00:06rhel-server-dts-6-rpms 4.0 kB 00:00rhel-server-dts-6-rpms/primary_db 45 kB 00:00rhel-server-dts2-6-rpms 3.2 kB 00:00rhel-server-dts2-6-rpms/primary_db 166 kB 00:00 _64/sjis/debug/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"Trying other mirror.Error: Cannot retrieve repository metadata (repomd.xml) for repository: rhel-sjis-for-rhel-6-server-eus-debug-rpms. Please verify its path and try again