Jump to content

Nova

Members
  • Content Count

    3
  • Joined

  • Last visited

Profile Information

  • Location
    Austria
  1. Thank you J.J. that worked for 1 Server hopefully it will last for a while! On the second server it doesn't work with these instructions got "Error downloading update.." had to purge the deb packet. After reinstallation the update works but on the first server i had newer files: +-+--------------------+------------------------+------------------------+ | | Module | Available version | Installed version | +-+--------------------+------------------------+------------------------+ | | loader | 1072 (20180813) | 1072 (20180813) | | | perseus | 1551.1 (20190424) | 1551.1 (20190424) | |*| engine | 19412 (20190524) | 19411 (20190524) | | | archiver | 1287 (20190516) | 1287 (20190516) | | | heuristic | 1192 (20190204) | 1192 (20190204) | | | cleaner | 1192 (20190507) | 1192 (20190507) | +-+--------------------+------------------------+------------------------+ as on the backup server: Virus signature database has been updated successfully. ESETS Update utility +-+--------------------+------------------------+------------------------+ | | Module | Available version | Installed version | +-+--------------------+------------------------+------------------------+ | | loader | 1072 (20180813) | 1072 (20180813) | | | perseus | 1549.3 (20190326) | 1549.3 (20190326) | | | engine | 18779 (20190128) | 18779 (20190128) | | | archiver | 1285 (20190313) | 1285 (20190313) | | | heuristic | 1192 (20190204) | 1192 (20190204) | | | cleaner | 1183 (20190305) | 1183 (20190305) | +-+--------------------+------------------------+------------------------+ How to fix that without corrupting the installation again? thx
  2. Again, after sucessfull updates i see on my 2 Servers (Ubuntu Server 16.04) again errors in the syslog file that the update was not sucessfull. With manually started updates from the shell ./esets_update --verbose i get on both that 3 files are corrupted, after i got the updates fixed in the night after several times of manually start the update from the shell (./esets_update) - on both servers! As both servers are located in different data centers i believe your update files or servers are the reason, there is no proxy or something between my servers and the update servers. Over time it's annoying that this issue appears very often in some cases i could only fix it by copying the em*.dat files and whole lib folder from one server where the update is working to the other server where the update files are corrupted again. Re-installation of the ESET Gateway Security as descriped in your manual doesn't fix the issue. Removing/moving the emu and dup files doesn't fix the issue. Without regular updates the product is useless? What's the solution?
×
×
  • Create New...