I upgraded to 26.1 a couple of hours ago and suddenly got a warning that the disk is close to full.
It is caused by hostwatch db growing rapidly:
root@xxx:~ # ll -h /var/db/hostwatch/
total 6392960
-rw-r--r-- 1 hostd hostd 4.0M Jan 30 10:25 hosts.db
-rw-r--r-- 1 hostd hostd 12M Jan 30 10:25 hosts.db-shm
-rw-r--r-- 1 hostd hostd 6.1G Jan 30 10:25 hosts.db-wal
I have rebooted but still same filesize
Disable hostwatch for the time being.
Interfaces: Neighbors: Automatic discovery
You can also try the latest test version as we already found the auto-vacuum doesn't always trigger:
# opnsense-revert -z hostwatch
# service hostwatch restart
Cheers,
Franco
Same issue observed with 26.1. Resolved by the latest test version, here's the before and after:
total 2286624
-rw-r--r-- 1 hostd hostd 4.2M Jan 30 04:47 hosts.db
-rw-r--r-- 1 hostd hostd 4.3M Jan 30 04:47 hosts.db-shm
-rw-r--r-- 1 hostd hostd 2.2G Jan 30 04:47 hosts.db-wal
root@www:~ # ll -h /var/db/hostwatch/
total 139904
-rw-r--r-- 1 hostd hostd 4.2M Jan 30 04:47 hosts.db
-rw-r--r-- 1 hostd hostd 4.3M Jan 30 04:47 hosts.db-shm
-rw-r--r-- 1 hostd hostd 128M Jan 30 04:47 hosts.db-wal
root@www:~ # ll -h /var/db/hostwatch/
Quote from: franco on Today at 10:55:03 AMYou can also try the latest test version as we already found the auto-vacuum doesn't always trigger:
# opnsense-revert -z hostwatch
# service hostwatch restart
Cheers,
Franco
Thank you. The test version worked fine. Same sizes as avove.
With the help of your feedback we decided to hotfix the .11 as well in 2-3 hours.
Cheers,
Franco
Thank you for this post. I had three instances that almost ran out of diskspace. Was able to fix it because of this in a couple of minutes.
Hotfix is available now for everyone. Make sure to restart hostwatch to ensure the correct version is running since there is no reboot.
Cheers,
Franco