Core 134 Geoip had the same string of geoip boot errors as Core update 133 does. Tried the missing folder fix I found for core update 133 but if fails on to fix core update 134. So somewhat different problem.
Regards
Wayne
On 2019-06-27 01:43, Mentalic wrote:
Core 134 Geoip had the same string of geoip boot errors as Core update 133 does. Tried the missing folder fix I found for core update 133 but if fails on to fix core update 134. So somewhat different problem.
If you have installed core134 before the kernel update to 4.14.131 the geoip modules was still missing and the old 4.14.121 modules from older cores will not work with 4.14.129... so reinstall the update by setting /opt/pakfire/db/core/mine back to 133
Right, I had updated my test box as soon as it was posted. No problems with it.
Wayne
-----Original Message----- From: Arne Fitzenreiter [mailto:Arne.Fitzenreiter@ipfire.org] Sent: Wednesday, July 3, 2019 4:08 AM To: Mentalic Cc: 'IPFire: Development-List' Subject: Re: Core 134 test
On 2019-06-27 01:43, Mentalic wrote:
Core 134 Geoip had the same string of geoip boot errors as Core update 133 does. Tried the missing folder fix I found for core update 133 but if fails on to fix core update 134. So somewhat different problem.
If you have installed core134 before the kernel update to 4.14.131 the geoip modules was still missing and the old 4.14.121 modules from older cores will not work with 4.14.129... so reinstall the update by setting /opt/pakfire/db/core/mine back to 133
-
Arne Fitzenreiter -
Mentalic