Jump to content

zhopkins

Members
  • Posts

    24
  • Joined

  • Last visited

  • Days Won

    2

Kudos

  1. Upvote
    zhopkins received kudos from Peter Randziak in Server Security v9   
    For what its worth, we tested the updated 9.0.12013 client on one of our AWS VMs, and it came back up successfully after a reboot.
  2. Upvote
    zhopkins received kudos from FRiC in Server Security v9   
    For what its worth, we tested the updated 9.0.12013 client on one of our AWS VMs, and it came back up successfully after a reboot.
  3. Upvote
    zhopkins received kudos from kurco in EFS for Linux issue - eset_rtp(ertp_wait_for_reply) - Ubuntu 21.04   
    Peter,
    I was able to spin up a fresh VM and do some additional testing.  ESET Server Security v8.1.565.0 immediately starts logging eset_rtp errors in the main "messages" log file (even on a blank VM with just our base OS install).  The slightly newer version, v8.1.685.0, does not seem to cause these error messages.
    With the latest version (8.1.685.0), I have noticed a strange behavior with the 'less' command, and I am trying to do some additional investigating to see if that issue is still related to the issue in this thread.  The less command (literally "less /var/log/messages") triggers a "Waiting for data... (interrupt to abort)" message on nearly every open of the log file.  This behavior is abnormal in our environment, so I want to be sure that the newer version of the antivirus is still not causing issues or delays when opening files.
  4. Upvote
    zhopkins received kudos from kurco in EFS for Linux issue - eset_rtp(ertp_wait_for_reply) - Ubuntu 21.04   
    Peter,
    Some examples for you -
    RHEL6 / Oracle / EXT4 local disks / CIFS remote shares RHEL7 / Oracle / EXT4 local disks / No remote shares RHEL7 / Icinga2 / EXT4 local disks / No remote shares RHEL8 / DNSMasq / XFS local disks / No remote shares I'm fairly certain that we are not using EDTD, since that is a separately licensed product?  It does not appear in the "Products & Licenses" section for the machines in the ESET PROTECT console.
    Overall, I believe most of the servers (some physical, most virtual) managed to get through with only minor slowdowns, however, the server that runs our Icinga monitoring became extremely unresponsive, to the point where I was unable to login via SSH or the console (even with root credentials).  I had to push a task through the ESET Management Agent to stop the EFS daemon before I could log in.
×
×
  • Create New...