Dwarfguard 2.0.1 released

The Dwarfguard 2.0.1 "Keeper patch1" fixes the following issues that were found in version 2.0.0:

• DCL DB export can be broken under some condition - if you have a deployment around and over 1000 devices, please see below
• Alert on missed contact metric using "greater than" operator is created as invalid
• Tunnel connect button for Webtunnel is not shown if Python extended libraries are not installed
• When updating license to another one with worse parameters (e.g. less devices, expires sooner etc.), GUI cannot be used for that.
• Log entries timestamps on device do not contain timezone

When the size of your deployment of Dwarfguard 2.0.0 reaches or exceeds 1000 devices, you are advised to upgrade to the patchlevel sooner rather than later. There is a corner case caused by specific device data that could break the DCL DB export. Next to the obvious impact (device history not being available in Changes Tracker (but available in FluxDB/Grafana just fine)), the DCL data are not freed from memory. According to our estimations, a deployment with 10 000 devices, regular traffic and 16 GiB RAM can run out of memory (DCL data growing, not being stored) in roughly 14 days. That would cause the operating system to kill some processes. While Dwarfguard would correctly restart itself with memory consumption back to minimal, the problems can arise when the OS decides to kill another running process/service, e.g. the database as that could cause more significant problems. In case your deployment falls into this category and you delay the upgrade to Dwarfguard 2.0.1 (which completely fixes this problem), you are advised to reboot the server once a week to prevent the described scenario.

Upgrade information: full upgrade supported from Dwarfguard 2.0.0

Underlaying OS support:

• Debian GNU/Linux 13
• Debian GNU/Linux 12