Since the beginning of this month the update-location-database script runs hourly and isn't waiting for the expected next 7 day interval.
I am not getting the expected "The database has been updated recently" message in /var/log/messages since Dec 1 05:06:32
On my development box IPFire 2.27 (x86_64) - Core-Update 170 . . Nov 30 22:38:14 ipfire-dev2 The database has been updated recently Nov 30 23:33:19 ipfire-dev2 The database has been updated recently Dec 1 00:24:50 ipfire-dev2 The database has been updated recently Dec 1 01:30:08 ipfire-dev2 The database has been updated recently Dec 1 02:14:32 ipfire-dev2 The database has been updated recently Dec 1 03:52:51 ipfire-dev2 The database has been updated recently Dec 1 04:09:29 ipfire-dev2 The database has been updated recently Dec 1 05:06:32 ipfire-dev2 The database has been updated recently
and also on my production box IPFire 2.27 (x86_64) - Core Update 168 . . Nov 30 22:45:58 griffith6 The database has been updated recently Nov 30 23:22:58 griffith6 The database has been updated recently Dec 1 00:53:45 griffith6 The database has been updated recently Dec 1 01:53:41 griffith6 The database has been updated recently Dec 1 02:45:16 griffith6 The database has been updated recently Dec 1 03:20:54 griffith6 The database has been updated recently Dec 1 04:34:41 griffith6 The database has been updated recently Dec 1 05:48:56 griffith6 The database has been updated recently Dec 1 06:28:10 griffith6 The database has been updated recently
There doesn't seem to affect performance other than the location ipsets are being updated every hour.
location version is being set to the last update time: # location version Fri, 02 Dec 2022 15:17:42 GMT
Could this be caused by the leading blank space in the day column after the month change from November to December ?
Rob