Jump to content

eset_rtp: wait for scanner reply timeout, path: exec.log.1 (deleted), event: CLOSE


Recommended Posts

Posted (edited)

OS : Debian 10
Eset version : ESET Server Security for Linux 9.1.98.0

----------
Hello

I have the same issue than this previous topics :

The "eset_rtp" process has stucked on one file (results of thousand of lines in the syslog) :

Jun 19 15:10:12 server kernel: [8961889.944731] eset_rtp: wait for scanner reply timeout, path: /var/log/proftpd/exec.log.1 (deleted), event: CLOSE, id: 16853740 pid: 28572

I think this file has been rotated by logrotate , but still in memory (kernel status CLOSED, but not really freeied), and the eset_rtp has lost is mind.
Then our server has crashed (out of memory).

Our log rotations (logrotate) took place at 6:25AM, then old files are moved (mv command) to an archive directory every day at 00:00AM.


So maybe looking  on the Linux kernel on file events ?

Thanks.
Gabriel

Edited by GabrielEset
typo correction
  • Administrators
Posted

If excluding the folder "/var/log/proftpd/*" doesn't make a difference, please raise a support ticket.

  • 2 weeks later...
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...