19.7.1: CRON-Job executed every minute spams log

[direx]

Hi,

after upgrading to 19.7 I have noticed an excessive amount of writes in system.log. The culprit is a cron job (flock), which is run every minute. This is a part of the system.log:

Code Select Expand


Jul 29 20:07:00 gate /usr/sbin/cron[65861]: (root) CMD ((/usr/local/bin/flock -n -E 0 -o /tmp/filter_update_tables.lock /usr/local/opnsense/scripts/filter/update_tables.py) > /dev/null)
Jul 29 20:08:00 gate /usr/sbin/cron[6378]: (root) CMD ((/usr/local/bin/flock -n -E 0 -o /tmp/filter_update_tables.lock /usr/local/opnsense/scripts/filter/update_tables.py) > /dev/null)
Jul 29 20:08:00 gate /usr/sbin/cron[97992]: (root) CMD ((/usr/local/sbin/ping_hosts.sh) > /dev/null)
Jul 29 20:09:00 gate /usr/sbin/cron[59705]: (root) CMD ((/usr/local/bin/flock -n -E 0 -o /tmp/filter_update_tables.lock /usr/local/opnsense/scripts/filter/update_tables.py) > /dev/null)
Jul 29 20:10:00 gate /usr/sbin/cron[86440]: (root) CMD (/usr/libexec/atrun)
Jul 29 20:10:00 gate /usr/sbin/cron[88207]: (root) CMD ((/usr/local/bin/flock -n -E 0 -o /tmp/filter_update_tables.lock /usr/local/opnsense/scripts/filter/update_tables.py) > /dev/null)
Jul 29 20:11:00 gate /usr/sbin/cron[17638]: (operator) CMD (/usr/libexec/save-entropy)
Jul 29 20:11:00 gate /usr/sbin/cron[38445]: (root) CMD ((/usr/local/bin/flock -n -E 0 -o /tmp/filter_update_tables.lock /usr/local/opnsense/scripts/filter/update_tables.py) > /dev/null)
Jul 29 20:12:00 gate /usr/sbin/cron[91071]: (root) CMD ((/usr/local/sbin/ping_hosts.sh) > /dev/null)
Jul 29 20:12:00 gate /usr/sbin/cron[42659]: (root) CMD ((/usr/local/bin/flock -n -E 0 -o /tmp/filter_update_tables.lock /usr/local/opnsense/scripts/filter/update_tables.py) > /dev/null)
Jul 29 20:13:00 gate /usr/sbin/cron[16179]: (root) CMD ((/usr/local/bin/flock -n -E 0 -o /tmp/filter_update_tables.lock /usr/local/opnsense/scripts/filter/update_tables.py) > /dev/null)
Jul 29 20:14:00 gate /usr/sbin/cron[52895]: (root) CMD ((/usr/local/bin/flock -n -E 0 -o /tmp/filter_update_tables.lock /usr/local/opnsense/scripts/filter/update_tables.py) > /dev/null)
Jul 29 20:15:00 gate /usr/sbin/cron[91449]: (root) CMD (/usr/libexec/atrun)
Jul 29 20:15:00 gate /usr/sbin/cron[32334]: (root) CMD ((/usr/local/bin/flock -n -E 0 -o /tmp/filter_update_tables.lock /usr/local/opnsense/scripts/filter/update_tables.py) > /dev/null)



That's the crontab:

Code Select Expand


crontab -l
# or /usr/local/etc/cron.d and follow the same format as
# /etc/crontab, see the crontab(5) manual page.
SHELL=/bin/sh
PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
#minute hour    mday    month   wday    command
1       *       *       *       *       (/usr/local/sbin/expiretable -v -t 3600 webConfiguratorlockout) > /dev/null
2       *       *       *       *       (/usr/local/sbin/expiretable -v -t 3600 sshlockout) > /dev/null
3       *       *       *       *       (/usr/local/sbin/expiretable -v -t 3600 virusprot) > /dev/null
5       *       *       *       *       (/usr/local/etc/rc.expireaccounts) > /dev/null
*/4     *       *       *       *       (/usr/local/sbin/ping_hosts.sh) > /dev/null
11      1       *       *       *       (/usr/local/etc/rc.dyndns) > /dev/null
1       3       1       *       *       (configctl filter schedule bogons) > /dev/null
*       *       *       *       *       (/usr/local/bin/flock -n -E 0 -o /tmp/filter_update_tables.lock /usr/local/opnsense/scripts/filter/update_tables.py) > /dev/null


My questions are:

• What does this job do? I did not notice it in 19.1.
• Does this job really have to be run every minute?

Thanks in advance,
direx

[franco]

Hi direx,

Should be this one for 19.7.2.

https://github.com/opnsense/core/commit/387d41d76


Cheers,
Franco