Jump to content

Eset command line scanner gives error code 139


Jefims
 Share

Go to solution Solved by Marcos,

Recommended Posts

Our company uses eset command line scanner + PHP to scan files:

exec("/opt/eset/esets/sbin/esets_scan --clean-mode=none " . $fileToScan . " 2>&1", $output, $scanReturnCode);

 

From yesterday (19.11.2020) this command suddenly stopped working with error code ($scanReturnCode): 139.

 

What do this error code means, what is code description? I was unnable to find any information about this code in google.

Why the problem might be appeared suddenly and how to fix it?

Link to comment
Share on other sites

  • Administrators
  • Solution

Please try the following:

  1. Stop the esets service : systemctl stop esets
  2. Delete content of modules directory in /var/opt/eset/esets/lib/
  3. Delete content of update cache directory in /var/opt/eset/esets/lib/data/updfiles/
  4. Run update manually : sudo /opt/eset/esets/sbin/esets_update --verbose
  5. Deleted modules will be replaced with fresh
  6. Start esets service, the issue should disappear : systemctl start esets
Link to comment
Share on other sites

54 minutes ago, Marcos said:

Please try the following:

  1. Stop the esets service : systemctl stop esets
  2. Delete content of modules directory in /var/opt/eset/esets/lib/
  3. Delete content of update cache directory in /var/opt/eset/esets/lib/data/updfiles/
  4. Run update manually : sudo /opt/eset/esets/sbin/esets_update --verbose
  5. Deleted modules will be replaced with fresh
  6. Start esets service, the issue should disappear : systemctl start esets

Thanks a lot, it helped to fix the problem🙂 Anyway, it's interesting, what was the possible error cause?

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...