Jump to content

ERA server installation in CentOS 7


kk654321
 Share

Recommended Posts

Hi all,

I had installed ERA server in VM - CentOS 7, the License was well added.

The config is:

Server: VMWare + CentOS 7 (IP: 192.168.180.128)

 

I found 2 issues there.

1. It failed to install ESET Antivirus for Linux to itself.

Error: Task failed, try to install software manually. SoftwareInstallation: Failed to install binary package '/tmp/bcd4-fcd9-8f8f-4f06/ueavbe_x86_64_enu.linux' with exit code: 64, stdout: , stderr: 

Screen Capture:

screenshot_20180116_143641.png.4d1a42dccd951ab3ad3120e99cb0e2f4.png

screenshot_20180116_144928.thumb.png.3d05d24b5ab88f8ced25e12c021d9e7b.png

2. It cannot connect other client even Agent was installed in client, e.g. connect Ubuntu 16.04 server (IP: 192.168.180.132).

screenshot_20180116_144103.png.c839e80c030f9a9ee747f48effc1889c.png

screenshot_20180116_144618.thumb.png.9691000ca53496c8d5a5ba10ca0e1564.png

screenshot_20180116_145247.png.394cf78e2e06343820050b177d8182b4.png

 

Status Log.

screenshot_20180116_145607.thumb.png.08247fdb62c0720d00d5b2b86c5eda8b.png

 

Any tips are welcome.

 

 

 

 

Edited by kk654321
Link to comment
Share on other sites

  • ESET Staff

Regarding your issues:

  1. first issue seems to be problem with missing dependencies. When installing package from ERA, package dependencies are not resolved automatically. You have not specified version or product type, but there are few dependencies of ESET security product for linux, which may not be expected. As an example, 32bit version of libraries are required to properly install this product on x64 based linux system. Unfortunately ERA reporting does not provide more relevant information in this case -> I would recommend to check, whether it is possible to install this product manually on target machine. There should be also list of required dependencies in ESET documentation for product you selected.
  2. For further analysis, status.html log from client machine will be required (the one you attached seems to be from ERA Server). I would also recommend to check whether AGENT is actually running (sudo service eraagent status or similar command depending on your linux distribution). More details with trace and statu logs location on client machine can be found in relevant documentation page.
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

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