Logs flooded when using incorrect Upload URL
Just installed v3.8.0 on a fresh install of Debian 11. I have a network wide DNS Server (AdGuard Home) that is performing a DNS rewrite from atlasapi.myacurite.com
to the internal IP of my Proxmox CT running Acuparse. Everything functions normally and as expected.
However, without noticing that I needed to change the MyAcuRite Upload URL to the secondary URL (acuparse.com), the log files were flooded with errors. Example:
Oct 30 18:25:20 Acuparse acuparse(3.8.0): (ACCESS){ATLAS}[SQL ERROR]:Duplicate entry '2021-10-30 22:25:00' for key 'PRIMARY'
Oct 30 18:25:20 Acuparse acuparse(3.8.0): (ACCESS){LIGHTNING}<ATLAS>[SQL ERROR]: Failed inserting with no existing data. Details: Duplicate entry '2021-10-30' for key 'PRIMARY'
Oct 30 18:25:20 Acuparse acuparse(3.8.0): (ACCESS){LIGHTNING}<ATLAS>: No Lightning Detected | Count: 0 | Interference = 0 | Last Strike = | Distance =
Oct 30 18:25:20 Acuparse acuparse(3.8.0): (ACCESS){MyAcuRite}[WARN]: MyAcuRite Offline - Generating Access Response
Obviously, these errors would be expected with this behaviour.
However, the loop that is created generates so many errors that the log files quickly balloon in size (e.g. within a few hours the log files were over 6GB). Since the default settings seems to be enable MyAcuRite upload on the primary server, it is possible that this can be missed. I'm not sure ideal solution (rate limit? identification of loop?), but as a new user I was not able to notice the problem until my disk was filled and thought I would report the issue here.