[solved] cron flooded logs

[seed]

I just updated to 19.7 and noticed something odd in the logs:

Jul 17 20:22:00    /usr/sbin/cron[26623]: (root) CMD ((/usr/local/opnsense/scripts/nginx/ngx_autoblock.php) > /dev/null)
Jul 17 20:22:00    /usr/sbin/cron[20311]: (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 17 20:22:00    /usr/sbin/cron[1899]: (operator) CMD (/usr/libexec/save-entropy)
Jul 17 20:21:00    /usr/sbin/cron[52381]: (root) CMD ((/usr/local/opnsense/scripts/nginx/ngx_autoblock.php) > /dev/null)
Jul 17 20:21:00    /usr/sbin/cron[40616]: (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 17 20:20:00    /usr/sbin/cron[64764]: (root) CMD ((/usr/local/sbin/ping_hosts.sh) > /dev/null)
Jul 17 20:20:00    /usr/sbin/cron[56496]: (root) CMD ((/usr/local/opnsense/scripts/nginx/ngx_autoblock.php) > /dev/null)
Jul 17 20:20:00    /usr/sbin/cron[52717]: (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 17 20:20:00    /usr/sbin/cron[28957]: (root) CMD (/usr/libexec/atrun)
Jul 17 20:19:00    /usr/sbin/cron[22484]: (root) CMD ((/usr/local/opnsense/scripts/nginx/ngx_autoblock.php) > /dev/null)
Jul 17 20:19:00    /usr/sbin/cron[21863]: (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 17 20:18:00    /usr/sbin/cron[21749]: (root) CMD ((/usr/local/opnsense/scripts/nginx/ngx_autoblock.php) > /dev/null)
Jul 17 20:18:00    /usr/sbin/cron[17841]: (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 17 20:17:00    /usr/sbin/cron[52045]: (root) CMD ((/usr/local/opnsense/scripts/nginx/ngx_autoblock.php) > /dev/null)
Jul 17 20:17:00    /usr/sbin/cron[48558]: (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 17 20:16:00    /usr/sbin/cron[70849]: (root) CMD ((/usr/local/sbin/ping_hosts.sh) > /dev/null)
Jul 17 20:16:00    /usr/sbin/cron[58180]: (root) CMD ((/usr/local/opnsense/scripts/nginx/ngx_autoblock.php) > /dev/null)
Jul 17 20:16:00    /usr/sbin/cron[54549]: (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 17 20:15:00    /usr/sbin/cron[33348]: (root) CMD ((/usr/local/opnsense/scripts/nginx/ngx_autoblock.php) > /dev/null)
Jul 17 20:15:00    /usr/sbin/cron[31472]: (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)

Is this an error or just cosmetic? :o

[franco]

Syslog change seems to accept cron's log messages now. Some more chatter, but it's always been executed like this before. Not sure what to do with it yet. Not an operational issue though. :)


Cheers,
Franco