inotify process not found

[rfxn]

inotify process not found

[jcarnus]

Seems to works well finally. Any option to send email of delete notification when occuring ?

[rfxn]

@jcarnus there is usually a delay for inotify to startup before files start being tracked, this may have been the issue you experienced.

The inotify monitor mode sends alerts daily, if your email address is configured in /usr/local/maldetect/conf.maldet and email_alerts=1. You can also check for quarantine events in /usr/local/maldetect/logs/event_log.

[jcarnus]

I try with an EICAR file, file get delete in almost realtime, but I didn"t received any email to inform me. I received email alert running a -r

[MaykBr]

After upgrading to version 1.5 the monitor does not work anymore

maldet --monitor users
Linux Malware Detect v1.5
(C) 2002-2015, R-fx Networks [email protected]
(C) 2015, Ryan MacDonald [email protected]
This program may be freely redistributed under the terms of the GNU GPL v2

maldet(742228): {mon} set inotify max_user_watches to 19709952
maldet(742228): {mon} added /home/abc/public_html to inotify monitoring array
maldet(742228): {mon} added /tmp to inotify monitoring array
maldet(742228): {mon} starting inotify process on 1191 paths, this might take awhile...
maldet(742228): {mon} no inotify process found, check /usr/local/maldetect/logs/inotify_log for errors.

I tried reinstalling the glibc package but not resolved.

[gerhard59]

Hi,

Just found this conversation and have the same issue with the installation.
Same error: {mon} no inotify process found, check /usr/local/maldetect/logs/inotify_log for errors.

Is there someone who has solved this issue already?

[ovizii]

same issue here, running Debian Jessie in case it helps

[agarzon]

Same issue here, 14.04 LTS

maldet(30639): {mon} no inotify process found, check /usr/local/maldetect/logs/inotify_log for errors.

But the log is always empty.

inotify-tools was installed and reinstalled.

[duanebc]

Same issue here

When previously working
Jan 05 20:59:02 aws maldet(24075): {mon} added /tmp to inotify monitoring array Jan 05 20:59:02 aws maldet(24075): {mon} starting inotify process on 448 paths, this might take awhile... Jan 05 20:59:04 aws maldet(24075): {mon} inotify startup successful (pid: 31116) Jan 05 20:59:04 aws maldet(24075): {mon} inotify monitoring log: /usr/local/maldetect/logs/inotify_log Jan 05 20:59:35 aws maldet(24075): {mon} warning clamd service not running; force-set monitor mode file scanning to every 120s Jan 05 20:59:35 aws maldet(24075): {mon} scanned 0 new/changed files with native engine

During current failure
Feb 08 18:54:18 aws maldet(15376): {mon} added /tmp to inotify monitoring array Feb 08 18:54:18 aws maldet(15376): {mon} starting inotify process on 456 paths, this might take awhile... Feb 08 18:54:20 aws maldet(15376): {mon} inotify startup successful (pid: 22373) Feb 08 18:54:20 aws maldet(15376): {mon} inotify monitoring log: /usr/local/maldetect/logs/inotify_log Feb 08 18:54:50 aws maldet(15376): {mon} warning clamd service not running; force-set monitor mode file scanning to every 120s Feb 08 18:54:50 aws maldet(15376): {mon} scanned 0 new/changed files with native engine Feb 08 18:56:50 aws maldet(15376): {mon} scanned 0 new/changed files with native engine

CPanel System running CentOS 6, and latest inotify via yum

# rpm -qa | grep inotify inotify-tools-devel-3.14-1.el6.x86_64 inotify-tools-3.14-1.el6.x86_64

maldet 1.5, manually tested inotify. I know the issue seems to be with inotify though looking to see if anyone found a solution here.

Seems a solution was found here for an issue involving 32 bit and Ubuntu though. #88