The maldet real-time monitoring daemon will not start. How can I fix this?

1. Double check that the default_monitor_mode is set:

Edit /usr/local/maldetect/conf.maldet and find and set:

default_monitor_mode="/usr/local/maldetect/monitor_paths"

2. Some users may also need to increase their inotify file watch limit on their systems before the maldet monitoring daemon will start.

To view your current limit:

cat /proc/sys/fs/inotify/max_user_watches

To raise your limit:

echo fs.inotify.max_user_watches=524288 > /etc/sysctl.d/sentinel.conf
sysctl -p /etc/sysctl.d/sentinel.conf

Start the service:

service maldet restart

  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

Does Sentintel Anti-malware scan my email?

No Sentinel Anti-malware is not designed to be an email scanner. Sentinel Anti-malware is...

How can I fix the daily cron error: /etc/cron.daily/maldet: line 69: [: ==: unary operator expected?

There is a bug in the Linux Malware Detect v1.6.4 daily cron script. You can fix the error by...

How can I fix the error: The file index.php is part of Plesk distribution. It cannot be run outside of the Plesk environment?

Plesk recently updated the PHP encoder that they use to protect Plesk extensions and you will get...