Core 133 test
mentalic at cox.net
Mon Jun 17 15:20:01 BST 2019
It had hours on one build, half hour or more on another two builds using the
updated 133 iso (b8de67b19eff2cd3735729b2c7441476 MD5).
So it looks to be something besides not waiting for geoip to unpack.
Typically I see 2-3 min of cpu load on a new build and its all set when cpu
I have a few geioIP groups configured which load from the backup before I
let the machine access internet.
Repeated ip tables error last sentence: "Couldn't load match 'geoip':No such
file or directory"
From: Arne Fitzenreiter [mailto:Arne.Fitzenreiter at ipfire.org]
Sent: Monday, June 17, 2019 2:18 AM
Cc: 'IPFire: Development-List'
Subject: Re: Core 133 test
On 2019-06-17 07:13, Mentalic wrote:
> Installed fresh iso x86_64. Restored backup from 132 system. Geoip is
> having a problem, countries show up in setting gui but nothing is
> actually being blocked. When booting there are many Geoip directory
> not found errors on screen.
GeoIP need to download and convert a Database before it is useable. It
should retry this after a while.
More information about the Development