Jump to content

Malzahn

Members
  • Content Count

    7
  • Joined

  • Last visited

  • Days Won

    1

Malzahn last won the day on November 26

Malzahn had the most liked content!

Profile Information

  • Location
    Germany

Recent Profile Visitors

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

  1. Uninstall and reinstall worked for me, too. While working, this is not a satisfactory solution since I had to redo all the configuration. And as Cybertooth pointed out - let's see how long it lasts.
  2. Concretely I've done the following: sudo systemctl stop esets sudo rm /var/opt/eset/esets/lib/* sudo rm -r /var/opt/eset/esets/lib/data/updfiles/* sudo systemctl start esets Result in a a few minutes of downloading data (network load) etc with no terminal output followed by: Job for esets.service failed because a timeout was exceeded. See "systemctl status esets.service" and "journalctl -xe" for details. sudo systemctl status esets Results in the following terminal output: ● esets.service - ESET NOD32 Antivirus Loaded: loaded (/lib/systemd/system/esets
  3. Hi @Marcos, Your previous suggestions didn't work for me or @Cybertooth as posted by both of us on Friday. We also could not completely execute them, since we don't have an esets_update program. Maybe these instructions are for a different linux software version (e.g. the buisiness version)? We also provided additional information on Friday in case they might be useful. Please advice how to proceed.
  4. I could not see a "modules" directory in /var/opt/eset/esets/lib/ . The only directory is data Neither removing only the *.dat and files in /var/opt/eset/esets/lib/data/updfiles/ (one machine) nor removing everything in lib (other machine) resulted in success. I do not have a /opt/eset/esets/sbin/esets_update file the only files in sbin are esets_daemon esets_scan esets_set Restarting with sudo systemctl start esets resulted in: Job for esets.service failed because the control process exited with error code. See "systemctl status esets.service" and "journalctl -xe" for details.
  5. For clarification this was the status before trying marcos steps.
  6. For further info: /opt/eset/esets/sbin/esets_daemon --version returns 4.0.95 And insepcting/var/log/syslog shows many messages like the following: Nov 20 08:37:29 mertins007 systemd[1]: Failed to start ESET NOD32 Antivirus. Nov 20 08:37:30 mertins007 systemd[1]: esets.service: Service hold-off time over, scheduling restart. Nov 20 08:37:30 mertins007 systemd[1]: esets.service: Scheduled restart job, restart counter is at 2943. Nov 20 08:37:30 mertins007 systemd[1]: Stopped ESET NOD32 Antivirus. in between these there is this message: Nov 20 08:32:04 mertins007
  7. I had the excact same problem yesterday on two kubuntu 18.04 machines, also Plasma 5.12.9. Absolutely blocked system (only occasionally reaction slightly) with red ESET notifcation icon. Hard reboot, followed by normally working system but not ESET gui icon. /opt/eset/esets/bin/esets_gui --version returns 4.0.95 for me. libappindicator1 was already installed package version 12.10.1+18.04.20180322.1-0ubuntu1 The indicator and gui was also working till yesterday earlier.
×
×
  • Create New...