Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 10 days have passed, without an answer from the ESET staff. I've also raised a case with Business support, no help from there. This is really really disappointing. Apart from the bugs with ERA console, this is the second product we have issues with
  2. We're using ESET File Security for Linux with ERA 6.5. Installation of Agent and FS went without issues, but I have some smaller questions about the security product. 1. We're receiving e-mails for license expiration, but not when threat is found. Task for threat notifications is enabled (through ERA, same as the license expiry task, which is on by default). I've read in manual PDF and man files that mail_notification_script should be executed when this task is enabled, and I've added av_mail_notified_users in /opt/eset/esets/esets.cfg file (default file where I've defined con
  3. thanks Martin, that helped me a lot.
  4. Well, changing options on /tmp is out of the question, since our environment comes from a configuration management, and I really don't want to have exec on /tmp. How can I set up those variables? I was running installation and both the service starting manually from root account
  5. So far none, but on those Linux servers we want to put File Security for Linux for which we have licenses
  6. Hi Martin, Here is the content of the folder: total 9.1M drwxr-x--- 2 root root 4.0K Apr 6 12:48 . drwxr-x--- 5 root root 4.0K Apr 6 12:55 .. -rw-r----- 1 root root 68K Nov 4 07:46 em000_64.dat -rw-r----- 1 root root 877K May 28 2016 em001_64.dat -rw-r----- 1 root root 5.7M Feb 11 01:27 em017_64.dat -rw-r----- 1 root root 2.5M Feb 1 01:27 em039_64.dat SELinux is disabled on all of my servers This is an output from mount command mount /dev/vda2 on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type
  7. I've installed Agent 6.5 x86_64 version with shell script on my CentOS 6.8 systems. Installation proceeds fine (I tried both the server assisted with username/password and the offline with certificates), there are no errors during install, but the Agent never starts and registers with ERA Server. What I've noticed is that the files in /etc/init.d aren't created, so I cannot use service eraagent start (or stop, status etc) and the only way I can start Agent is if I run /opt/eset/RemoteAdministrator/Agent/ERAAgent --daemon --pidfile=/var/run/eraagent.pid from /etc/init/eraagent.conf Running
  • Create New...