imunify360 constant cron job every minute

[jeffschips]

Hello.

Is it normal for the free version of imunify360 to produce cron logs showing activity every single minute as well as every 5 minutes as such:

May 31 07:30:01 xxxxxxxxxxxxxx CROND[6360]: (root) CMD (   imunify360-agent malware on-demand check-detached 2>&1 > /dev/null || :)
May 31 07:35:01 xxxxxxxxxxxxxx CROND[6631]: (root) CMD (   imunify360-agent malware on-demand check-detached 2>&1 > /dev/null || :)
May 31 07:40:01 xxxxxxxxxxxxxx CROND[6910]: (root) CMD (   imunify360-agent malware on-demand check-detached 2>&1 > /dev/null || :)
May 31 07:45:01 xxxxxxxxxxxxxx CROND[7102]: (root) CMD (   imunify360-agent malware on-demand check-detached 2>&1 > /dev/null || :)
May 31 07:50:01 xxxxxxxxxxxxxx CROND[7367]: (root) CMD (   imunify360-agent malware on-demand check-detached 2>&1 > /dev/null || :)
May 31 07:55:01 xxxxxxxxxxxxxx CROND[7620]: (root) CMD (   imunify360-agent malware on-demand check-detached 2>&1 > /dev/null || :)
May 31 08:00:01 xxxxxxxxxxxxxx CROND[7895]: (root) CMD (   imunify360-agent malware on-demand check-detached 2>&1 > /dev/null || :)
May 31 08:05:01 xxxxxxxxxxxxxx CROND[8134]: (root) CMD (   imunify360-agent malware on-demand check-detached 2>&1 > /dev/null || :)

May 31 04:15:01 xxxxxxxxxxxxxx CROND[28495]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
May 31 04:16:01 xxxxxxxxxxxxxx CROND[28626]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
May 31 04:17:01 xxxxxxxxxxxxxx CROND[28654]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
May 31 04:18:01 xxxxxxxxxxxxxx CROND[28687]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
May 31 04:19:01 xxxxxxxxxxxxxx CROND[28720]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
May 31 04:20:01 xxxxxxxxxxxxxx CROND[28767]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
May 31 04:21:01 xxxxxxxxxxxxxx CROND[28822]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
May 31 04:22:01 xxxxxxxxxxxxxx CROND[28934]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
May 31 04:23:01 xxxxxxxxxxxxxx CROND[28969]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
May 31 04:24:01 xxxxxxxxxxxxxx CROND[29000]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
May 31 04:25:01 xxxxxxxxxxxxxx CROND[29042]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
May 31 04:26:02 xxxxxxxxxxxxxx CROND[29092]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
May 31 04:27:01 xxxxxxxxxxxxxx CROND[29120]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)

 

[cPRex]

Hey there! I spoke with the Imunify team about this and they said it is fine to remove this cron if you have Imunify360 installed.

 

[jeffschips]

Thanks. But that's just it - there is no cron job in root or user having anything to do with imunify.

 

[cPRex]

Now *that* is interesting :D

If you're not seeing a cron there, it might be best to open a ticket and reference this thread.

 

[jeffschips]

Hello. I did submit a request and resolution on my end was to simply purge imunify360 from the server which also deleted the errant cron jobs associated with it. The errant cron job was listed in /etc/cron.d/ This was acceptable as I wasn't using the professional version and only getting full scans once a month. So problem solved and I would like to add that the technician was very thorough, quick and professional.

Thanks again Cpanel!

 

[cPRex]

Thanks for the follow-up post!