"
Apologies for the necroposting, but I observed the same issue, and decided to find the cause. The problem seems to be that root crontab calls for netflow data backup every hour on the dot:
20-netflow script does stop/start cycle if flowd_aggregate is running, effectively restarting the process every hour at xx:00.
Might not be a big deal in the grand scheme of things, but it seems that there is some inconsistency with other parts of the code. flowd_aggregate tries to vacuum its sqlite DBs on start, and then every 8 hours while it's running. But restarting it every hour means that vacuum runs every hour, hitting disk IO more often than anticipated (vacuum is IO heavy). That's how I noticed this behavior in the first place :)
Code Select
#minute hour mday month wday command
0 */1 * * * (/usr/local/etc/rc.syshook.d/backup/20-netflow) > /dev/null
20-netflow script does stop/start cycle if flowd_aggregate is running, effectively restarting the process every hour at xx:00.
Might not be a big deal in the grand scheme of things, but it seems that there is some inconsistency with other parts of the code. flowd_aggregate tries to vacuum its sqlite DBs on start, and then every 8 hours while it's running. But restarting it every hour means that vacuum runs every hour, hitting disk IO more often than anticipated (vacuum is IO heavy). That's how I noticed this behavior in the first place :)
