Changes

From SME Server
Jump to navigationJump to search

GeoIP (view source)

Revision as of 23:20, 5 January 2019

1,463 bytes added ,  23:20, 5 January 2019
no edit summary
Line 1: Line 1:  
{{Languages}}
 
{{Languages}}
 
=== Maintainer ===
 
=== Maintainer ===
 +
[[User:ReetP|john crisp]]
 +
 
[mailto:stephdl@de-labrusse.fr stephdl] Stéphane de Labrusse AKA [[User:stephdl|Stephdl]]<br />
 
[mailto:stephdl@de-labrusse.fr stephdl] Stéphane de Labrusse AKA [[User:stephdl|Stephdl]]<br />
 
=== Version ===
 
=== Version ===
Line 11: Line 13:  
{{Note box|Maxmind have removed support for their legacy v1 DBs and an update to v2 DBs is required. Please see the bugtracker link to bug #9033 below for more information }}
 
{{Note box|Maxmind have removed support for their legacy v1 DBs and an update to v2 DBs is required. Please see the bugtracker link to bug #9033 below for more information }}
   −
+
=== Installation of legacy geoip v1 db ===
   −
===Installation and Updating===
+
those are still available for few time only for back compatibility purpose and to avoid a yum update mess, or if you do not trust third party repo, but be aware thos db are not updated anymore since April 2018 and were already only 80% accurate then.
 +
yum install smeserver-geoip --enablerepo=smecontribs
 +
config set UnsavedChanges no
 +
signal-event geoip-update
 +
 
 +
==== update of geoip v1 db ====
 +
if you have smeserver-geoip-1.1.2-7 already installed,  this will keep you on the legacy version, only change new plugin comaptible with v1 and removal of cron update.
 +
yum update --enablerepo=smecontribs
 +
 
 +
===Installation and Updating of geoip v2 db===
    
Because the databases have been updated new perl modules are required to support GeoIP v2. The core modules have a large number of dependencies and we have decided that it is not practical for the Koozali team to maintain them all.
 
Because the databases have been updated new perl modules are required to support GeoIP v2. The core modules have a large number of dependencies and we have decided that it is not practical for the Koozali team to maintain them all.
Line 21: Line 32:  
  signal-event yum-modify  
 
  signal-event yum-modify  
 
  config set UnsavedChanges no
 
  config set UnsavedChanges no
−
 
+
====Updating to v2 with v1 DBs installed====
−
=====Updating with v1 DBs installed=====
   
If you have the v1 DBs package smeserver-geoip-1.1.2-7 already installed and do not wish to update to v2 DBs you may perform updates safely, after making sure your smeserver-extrarepositories-openfusion is the latest, the following:
 
If you have the v1 DBs package smeserver-geoip-1.1.2-7 already installed and do not wish to update to v2 DBs you may perform updates safely, after making sure your smeserver-extrarepositories-openfusion is the latest, the following:
   −
  yum update --enablerepo=smecontribs,openfusion 
+
To carry out an install or update of the new v2 DBs you are required to firstly remove the exclude statement from the openfusion repo db
 +
db yum_repositories delprop openfusion Exclude
 +
  signal-event yum-modify
   −
only produces a normal update, no extras from openfusion, trying to do an update of smeserver-geoip to a v2 status with excludes included produces depends errors and a failed update
+
Then remove the smeserver-geoip v1 db package
   −
If you do not want to update you will need to follow something like this:
+
yum remove smeserver-geoip
 +
You may then go ahead with the following to either install or update a v2 DB package
 +
yum install smeserver-geoip2 --enablerepo=smecontribs,openfusion
 +
yum update --enablerepo=smecontribs,openfusion
 +
config set UnsavedChanges no
   −
db yum_repositories setprop smecontribs Exclude smeserver-geoip
+
====Fresh Installation of geoip v2 DBs====
−
signal-even yum-modify
  −
 
  −
====Installation/Update v2 DBs====
   
To carry out an install or update of the new v2 DBs you are required to firstly remove the exclude statement from the openfusion repo db
 
To carry out an install or update of the new v2 DBs you are required to firstly remove the exclude statement from the openfusion repo db
 
  db yum_repositories delprop openfusion Exclude  
 
  db yum_repositories delprop openfusion Exclude  
Line 41: Line 54:  
You may then go ahead with the following to either install or update a v2 DB package
 
You may then go ahead with the following to either install or update a v2 DB package
   −
  yum install smeserver-geoip --enablerepo=smecontribs,openfusion
+
  yum install smeserver-geoip2 --enablerepo=smecontribs,openfusion
−
  yum update smeserver-geoip --enablerepo=smecontribs,openfusion (preferred method)
+
  yum update --enablerepo=smecontribs,openfusion
 +
config set UnsavedChanges no
 +
 
 +
==== I installed the beta versions of smeserver-geoip v2 ====
 +
if you installed smeserver-geoip-1.2-1, smeserver-geoip-1.2-2, smeserver-geoip-1.2-3, then you have already a v2, but you still need to do as you were with legacy  version and want to upgrade to v2. Otherwise you will not have the db updated anymore
 +
 
 +
db yum_repositories delprop openfusion Exclude
 +
signal-event yum-modify
 +
 
 +
Then remove the smeserver-geoip v1 db package
 +
 
 +
yum remove smeserver-geoip
 +
You may then go ahead with the following to either install or update a v2 DB package
 +
yum install smeserver-geoip2 --enablerepo=smecontribs,openfusion
 
  yum update --enablerepo=smecontribs,openfusion
 
  yum update --enablerepo=smecontribs,openfusion
 
  config set UnsavedChanges no
 
  config set UnsavedChanges no
    
==== Update the db ====
 
==== Update the db ====
 +
(only working for geoip2 from 2019/01/03)
 
  signal-event geoip-update
 
  signal-event geoip-update
  
Unnilennium
Super Admin, Wiki & Docs Team, Bureaucrats, Interface administrators, Administrators
3,254

edits

Retrieved from "https://wiki.koozali.org/Special:MobileDiff/37817"

Navigation menu