Upon further look, the issue is not particular to update-location-database.
Running command, firewallctrl, also results in the same set of error indications.

-cab

On 4/18/2022 8:12 AM, Charles Brown wrote:

Hi Stefan, Tim, Rob

I manually updated my location database at ssh shell prompt with command, update-location-database.
It appears to present some possible conflicts.  Or perhaps, is this purely informational? See following.

-Charles

-----------------------------------------------------------------------------------------------------------------------------------------

[root@ipfire ~]# update-location-database
Downloaded new database from Mon, 18 Apr 2022 05:52:42 GMT
Reloading firewall
ipset v7.11: Error in line 3: Set cannot be created: set with the same name already exists
ERROR: ipset restore -f /var/lib/ipblocklist/BLOCKLIST_DE.conf
ipset v7.11: Error in line 3: Set cannot be created: set with the same name already exists
ERROR: ipset restore -f /var/lib/ipblocklist/BOGON_FULL.conf
ipset v7.11: Error in line 3: Set cannot be created: set with the same name already exists
ERROR: ipset restore -f /var/lib/ipblocklist/EMERGING_COMPROMISED.conf
ipset v7.11: Error in line 3: Set cannot be created: set with the same name already exists
ERROR: ipset restore -f /var/lib/ipblocklist/FEODO_AGGRESIVE.conf
ipset v7.11: Error in line 3: Set cannot be created: set with the same name already exists
ERROR: ipset restore -f /var/lib/ipblocklist/SHODAN.conf
ipset v7.11: Error in line 3: Set cannot be created: set with the same name already exists
ERROR: ipset restore -f /var/lib/ipblocklist/SPAMHAUS_EDROP.conf
ipset v7.11: Error in line 3: Set cannot be created: set with the same name already exists
ERROR: ipset restore -f /var/lib/ipblocklist/TOR_ALL.conf                                                             
[  OK  ]