From: Mentalic <mentalic@cox.net>
To: development@lists.ipfire.org
Subject: RE: Core 133 test
Date: Mon, 17 Jun 2019 09:20:01 -0500 [thread overview]
Message-ID: <000001d52517$c28fb0d0$47af1270$@net> (raw)
In-Reply-To: <2f9263832504ce325d9f232f60b9b45b@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
Arne,
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
load drops.
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"
Regards
Wayne
-----Original Message-----
From: Arne Fitzenreiter [mailto:Arne.Fitzenreiter(a)ipfire.org]
Sent: Monday, June 17, 2019 2:18 AM
To: Mentalic
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.
>
> Wayne
GeoIP need to download and convert a Database before it is useable. It
should retry this after a while.
next prev parent reply other threads:[~2019-06-17 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000001d524cb$5ef76410$1ce62c30$@net>
2019-06-17 7:17 ` Arne Fitzenreiter
2019-06-17 14:20 ` Mentalic [this message]
2019-06-17 16:02 ` Michael Tremer
2019-06-25 0:16 ` Mentalic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000001d52517$c28fb0d0$47af1270$@net' \
--to=mentalic@cox.net \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox