Reducing logging to /var/log/auth.log generated by internal HestiaCP housekeeping tasks

Community Support
13

I chose the quick and dirty way out, by suppressing those logs with rsyslog (rather than reconfiguring PAM & sudo) using :msg, contains, "session xyz" stop

Btw is it normal for v-update-sys-queue to run so often?

tail -f /var/log/cron.log 
Dec 13 22:24:01 myserver CRON[29784]: (admin) CMD (sudo /usr/local/hestia/bin/v-update-sys-queue restart)
Dec 13 22:25:01 myserver CRON[29813]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Dec 13 22:25:01 myserver CRON[29814]: (admin) CMD (sudo /usr/local/hestia/bin/v-update-sys-rrd)
Dec 13 22:25:01 myserver CRON[29815]: (admin) CMD (sudo /usr/local/hestia/bin/v-update-sys-queue backup)
Dec 13 22:26:01 myserver CRON[30165]: (admin) CMD (sudo /usr/local/hestia/bin/v-update-sys-queue restart)
Dec 13 22:28:01 myserver CRON[30193]: (admin) CMD (sudo /usr/local/hestia/bin/v-update-sys-queue restart)
Dec 13 22:30:01 myserver CRON[30238]: (admin) CMD (sudo /usr/local/hestia/bin/v-update-sys-queue backup)
Dec 13 22:30:01 myserver CRON[30239]: (admin) CMD (sudo /usr/local/hestia/bin/v-update-sys-rrd)
Dec 13 22:30:01 myserver CRON[30240]: (admin) CMD (sudo /usr/local/hestia/bin/v-update-sys-queue restart)
Dec 13 22:32:01 myserver CRON[30518]: (admin) CMD (sudo /usr/local/hestia/bin/v-update-sys-queue restart)
^C