barb 0 Posted May 23, 2013 Share Posted May 23, 2013 I've receiving this Warning in my ERAC Event Log. It happens multiple times for each of my installed Linux clients all at the same time (e.g. "11 hours ago"). The message also reports this warning for /dev/fd/14 and /dev/fd/16. Any idea what this is? Thanks, barb Link to comment Share on other sites More sharing options...
Administrators Marcos 4,929 Posted May 24, 2013 Administrators Share Posted May 24, 2013 I assume you have ESET NOD32 Antivirus Business Edition for Linux Desktop 4.0.79 installed on clients, do you? What Linux distribution do you use? Also post the output of running "uname -a". Link to comment Share on other sites More sharing options...
barb 0 Posted May 24, 2013 Author Share Posted May 24, 2013 Thanks for your reply. Yes, running 4.0.79. Most of the affected computers are running Fedora 12. # uname -aLinux hellfish 2.6.32.26-175.fc12.i686.PAE #1 SMP Wed Dec 1 21:45:50 UTC 2010 i686 i686 i386 GNU/Linux Link to comment Share on other sites More sharing options...
alexanderv 0 Posted November 5, 2013 Share Posted November 5, 2013 Hi all, I got the same issue on a centOS 6.4: cat /var/log/messages Nov 5 03:06:02 [servername] esets_daemon[17163]: warning[430b0000]: Cannot canonicalize /dev/fd/15: No such file or directory Nov 5 03:06:02 [servername] esets_daemon[17163]: warning[430b0275]: Cannot canonicalize /dev/fd/15: No such file or directory Nov 5 03:06:02 [servername] esets_daemon[17163]: summ[430b0275]: vdb=15752, agent=pac, name="/dev/fd/15", virus="", action="", info="Event occurred on a newly created file.", avstatus="not scanned", hop="accepted" #uname -a: Linux [servername] 2.6.32-358.23.2.el6.x86_64 #1 SMP Wed Oct 16 18:37:12 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Do you have any solutions yet? Kind regards, Alexander Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 1,084 Posted November 5, 2013 ESET Moderators Share Posted November 5, 2013 Hello Alexander, this error means that we caught access to some file, but it was not possible to scan it. For example the file could have been opened only with write permission, or it has been already deleted as far it was just temp file. So it is nothing you should worry about. Link to comment Share on other sites More sharing options...
alexanderv 0 Posted November 5, 2013 Share Posted November 5, 2013 Ok, thanks for the fast response! Link to comment Share on other sites More sharing options...
limepo 0 Posted July 7, 2016 Share Posted July 7, 2016 I have same problem. See below. esets_daemon[1810]: warning[07120000]: Nie je absolútna cesta: Jul 7 10:07:48 notebook esets_daemon[1810]: warning[07120142]: Nie je absolútna cesta: Jul 7 10:07:48 notebook esets_daemon[1810]: summ[07120142]: vdb=30030, agent=pac, name="", virus="", action="", info="Táto udalosť bola zistená na novovytvorenom súbore.", avstatus="not scanned", hop="accepted" Linux notebook 4.5.0-0.bpo.2-amd64 #1 SMP Debian 4.5.4-1~bpo8+1 (2016-05-13) x86_64 GNU/Linux Link to comment Share on other sites More sharing options...
Recommended Posts