nwb

Thanks for your prompt reply OK, I can see the logs now that you have directed me And I'm now getting the exit code in the terminal on completion, I don't know why I wasn't earlier. Showed as 10 (see attachment) So cross fingers, all looks like it's working OK Cheers nwb

Hello When I run a manual scan, eg. sudo /opt/eset/eea/bin/odscan --scan --profile="@Smart scan" /home/* I can see the hard disk humming away for a while and then the terminal reverts back to the prompt My question is, where is the exit code? I thought it might appear in the terminal after the scan, but no. Is there a log somewhere that shows it? At the very least I should see a 0 somewhere? How do I know the scan has completed successfully? It seems pretty fast compared to the old NOD 32 process I have attached a couple of screenshots of the terminal Thanks nwb

Hello Wondering if you've had a chance to look at this problem yet? Still happening on scan attempt logd[13010]: ESET Endpoint Antivirus Error: Cannot create temporary file: Permission denied logd[13010]: ESET Endpoint Antivirus Error: Cannot create new scan log: Too many scan logs are open simultaneously Thanks nwb

sorry, should have edited to just show from installation of 8.1.4.0 neil list logs after reinstallation.txt

Further to this, I've attached what happens when I request a list of logs Might give a clue to what is happening.. It's like something isn't set up properly Cheers N neil list logs.txt

Thanks for looking at this I've uninstalled, rebooted, and then reinstalled. Definitely now on 8.1.4.0 But I still have the same problem when I attempt to run a scan: logd[2657]: ESET Endpoint Antivirus Error: Cannot create temporary file: Permission denied logd[2657]: ESET Endpoint Antivirus Error: Cannot create new scan log: Too many scan logs are open A bit frustrating. I've attached the latest logs. And the gui This scan issue, is this just for manual scans or would it be affecting the auto scanning of incoming files as well? Cheers nwb eea_logs.tar.zip

Thanks for replying /tmp folder had permission 1777 so OK /eset/eea/ods/ folders in /var/log/ didn't even exist. So I added them and set the permission of the ods folder to 700 But I still have the same issue when I try to run a scan. I've attached the log files. They downloaded as a .tar.gz so I had to convert it to .zip for attachment, hope it's OK Cheers nwb eea_logs.tar.zip

When I try to run a scan from terminal eg. sudo /opt/eset/eea/bin/odscan --scan --profile="@Smart scan" /folder structure to scan/ I get the following error messages logd[2660]: ESET Endpoint Antivirus Error: Cannot create temporary file: Permission denied logd[2660]: ESET Endpoint Antivirus Error: Cannot create new scan log: Too many scan logs are open simultaneously I can't find anything documented to sort this. It's probably something simple. Any help or pointing in the right direction would be appreciated Thanks

Odd. I purchased the license Feb 2018, renewed Feb 2021 with expiry 2024 Nowhere was it stated this product has EOL Q2/21. I'm assuming there is an updated or alternative product available after the expiry?

My issue has previously been raised, but this thread was halted so no replies or additions are possible Why does ESET NOD 32 AV have to be repaired after file cleaning? By IanSL, August 11, 2020 in ESET NOD32 Antivirus for Linux Desktop I have the same issue as this original post, whenever my temporary files are cleaned up I need to 'repair' ESET NOD32 in order to get it to auto start at each boot again. I too find the response to this original post somewhat underwhelming. I've paid the licence fee after all ... There is obviously a minor fault, some file or other it needs to run is probably stored in the temporary area and is being deleted during file clean up. The 'repair' obviously re-instates whatever it is. Shouldn't be that hard to sort? Apart from that, it's a great product Cheers N