ESET Command Line 3.0.22 Error Code 127

Discussion in 'ESET NOD32 Antivirus' started by Johneh, Aug 4, 2011.

Thread Status:
Not open for further replies.
  1. Johneh

    Johneh Registered Member

    Joined:
    Aug 4, 2011
    Posts:
    6
    We're getting the error code 127 from the ESET Command Line Scanner version 3.0.22, but I can't find any documentation on what that actually means?

    Is there a definitive list of error/exit codes from the scanner?

    The only ones I've found are from the --help option, which show:

    Exit codes:
    0 no threat found
    1 threat found and cleaned
    10 some files could not be scanned (may be threats)
    50 threat found
    100 error

    Thanks in advance (also apologies if this is in the wrong section!)
    John
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Ain't it the command line scanner from the obsolete version 3.0.22?
     
  3. Johneh

    Johneh Registered Member

    Joined:
    Aug 4, 2011
    Posts:
    6
    Quite possible that the version is out of date, the only error codes I've found on the help sections of the eset site referred to versions 3 & 4, these error codes seem to match up with the version 4 page though rather than the version 3, which I found strange.

    V3:
    http://kb.eset.com/esetkb/index?page=content&id=SOLN565
    0 no threat found
    1 threat found but not cleaned
    10 some infected files were not cleaned
    101 archive error
    102 access error
    103 internal error

    V4:
    http://kb.eset.com/esetkb/index?page=content&id=SOLN2285
    0 no threat found
    1 threat found and cleaned
    10 some files could not be scanned (may be threats)
    50 threat found
    100 error


    Yet nothing about the code 127, and we've got this several times with different files now. I wondered if anyone knew what the code actually meant? (Surely one of the developers must know.. as it must be a meaningful number to them?!)
     
  4. Johneh

    Johneh Registered Member

    Joined:
    Aug 4, 2011
    Posts:
    6
    Can no-one help with this then? We're now getting an error code 2 on some of the files?
     
  5. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    Have you tried scanning with a newer version of ESET's software? Version updates are free, but you would likely have to download the newest version manually from http://www.eset.com/download.

    Regards,

    Aryeh Goretsky
     
  6. Johneh

    Johneh Registered Member

    Joined:
    Aug 4, 2011
    Posts:
    6
    I can attempt to, however the software is installed on a remote server, so makes it a bit trickier to re-install.

    Does the newer version have better help that gives a list of all the possible exit codes then?
     
  7. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    Because that is such an old version, it is difficult to determine what its behavior might be. With a current version of the software, if there is a problem, it is easy to begin an investigation.

    Regards,

    Aryeh Goretsky
     
  8. Johneh

    Johneh Registered Member

    Joined:
    Aug 4, 2011
    Posts:
    6
    I've checked and we're definitely using the latest version of the software.
    Product name is 'ESET File Security for Linux/BSD/Solaris', and the latest release is '3.0.22.0'
    Thanks again
     
  9. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    I've inquired the devs about the meaning of the 2 exit codes. As for the code 127, it is returned by shell when the specified command was not found / recognized. As for the code 2, it's nowhere in the resource files so we strongly doubt it could be returned by esets_scan. Could you provide us with an evidence where you see it?
     
  10. Johneh

    Johneh Registered Member

    Joined:
    Aug 4, 2011
    Posts:
    6
    Hi,
    Thanks for that, looks like we were being stupid and leaving random characters in the filemame and not quoting it.

    For future reference anyone else with this problem:
    127 came from ampersands: '&' symbols in the filename
    and
    2 came from brackets '()' in the filename


    Thanks for helping us get to this conclusion guys :D
     
  11. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    Ah, I didn't realize you were running the UNIX version. Thank you for letting us know.

    Regards,

    Aryeh Goretsky
     
Thread Status:
Not open for further replies.