Context:
Had an issue where a proxy of mine had its proxy process crash every 2 minutes. As a result of this, housekeeper wasn't running (it holds off for 30 minutes when the process is first started before running).
Didn't notice for a week when the zabbix.db file had ballooned big enough to take up the entire drive.https://discord.software/ FetLife vshare
Expanded the drive to get the proxy running again, fixed the crash issue, housekeeper has been running again, and is back to clearing the correct amount of rows per run now that it's caught up.
However, the zabbix.db file has not shrunk. It's still sitting around 16 gigabytes, whereas our other proxy DBs are roughly 250MB for a similar amount of hosts.
Is there a way to force zabbix to give up that space it's grabbed, or do I need to just delete the file and put a new proxy DB out there, since it's shipping off all of its data to the server anyway.
Had an issue where a proxy of mine had its proxy process crash every 2 minutes. As a result of this, housekeeper wasn't running (it holds off for 30 minutes when the process is first started before running).
Didn't notice for a week when the zabbix.db file had ballooned big enough to take up the entire drive.https://discord.software/ FetLife vshare
Expanded the drive to get the proxy running again, fixed the crash issue, housekeeper has been running again, and is back to clearing the correct amount of rows per run now that it's caught up.
However, the zabbix.db file has not shrunk. It's still sitting around 16 gigabytes, whereas our other proxy DBs are roughly 250MB for a similar amount of hosts.
Is there a way to force zabbix to give up that space it's grabbed, or do I need to just delete the file and put a new proxy DB out there, since it's shipping off all of its data to the server anyway.