Centos / RHEL / CloudLinux / AlmaLinux
/usr/local/psa/admin/bin/modules/sentinel/install.sh
Debian / Ubuntu
/opt/psa/admin/bin/modules/sentinel/install.sh
Centos / RHEL / CloudLinux / AlmaLinux
// maldet restart
systemctl restart maldet
// maldet log file
tail -f /usr/local/maldetect/logs/event_log
// clamav restart
systemctl restart clamd@scan
// clamav log file
tail -f /var/log/clamd.scan
// freshclam restart (Centos/RHEL/Cloudlinux/AlmaLinux 8 only)
systemctl restart clamav-freshclam
// freshclam log file
tail -f /var/log/freshclam.log
Debian / Ubuntu
// maldet restart
systemctl restart maldet
// maldet log file
tail -f /usr/local/maldetect/logs/event_log
// clamav restart
systemctl restart clamav-daemon
// clamav log file
tail -f /var/log/clamav/clamav.log
// freshclam restart
systemctl restart clamav-freshclam
// freshclam log file
tail -f /var/log/clamav/freshclam.log
Wrong time on the server
Make sure that the date and time on the server is correct. The wrong date and time will cause the SSL certificate connections that the installer uses to fail. You can sync your server time using the command:
// sync the time
/usr/sbin/ntpdate -b -s time.nist.gov
// re-run the installer and check for errors
/usr/local/psa/admin/bin/modules/sentinel/install.sh
Not enough memory to start the ClamAV daemon:
If you see Cannot allocate memory
in your ClamAV daemon logs this means that you do not have enough free memory in order to start the ClamAV daemon. Free up some memory on your server or upgrade your system memory then restart the Anti-virus service.
// Centos / RHEL / CLoudLinux / AlmaLinux
# grep 'Cannot allocate memory' /var/log/clamd.scan
// Debian / Ubuntu
# grep 'Cannot allocate memory' /var/log/clamav/clamav.log
Sun Feb 10 03:15:52 2019 -> ERROR: daemonize() failed: Cannot allocate memory
Sun Feb 10 03:25:51 2019 -> ERROR: daemonize() failed: Cannot allocate memory
Sun Feb 10 03:32:12 2019 -> ERROR: daemonize() failed: Cannot allocate memory
Incorrect permissions your /var/tmp or /tmp directories used by the ClamAV
If you see Failed to create temporary file
in your ClamAV daemon logs this means that your /var/tmp
or /tmp
permissions are not writable by the ClamAV daemon.
# grep 'Failed to create temporary file' /var/log/clamd.scan
// Debian / Ubuntu
# grep 'Failed to create temporary file' /var/log/clamav/clamav.log
Thu Apr 18 22:31:55 2019 -> ERROR: Failed to create temporary file
Thu Apr 18 22:31:55 2019 -> ERROR: Failed to create temporary file
To fix the tmp permissions change the permissions then restart the ClamAV daemon service:
chmod 777 /var/tmp /tmp
You can run the uninstaller from the command line to completely remove the extension:
/usr/local/psa/bin/extension --uninstall sentinel
If you still have problems just open a support ticket in our client area to have an experienced technician diagnose and fix the problem for you.