usageStats ( stadistics) problem with update ojs 2.4.8 to 3.0.2

Hello Community:

First info my sytem:

Info server:
Plataforma SO Linux
Versión PHP 5.6.30-0+deb8u1
Versión Apache Apache/2.4.10 (Debian)
Driver de la base de datos postgres
Versión del servidor de bases de datos PostgreSQL 9.6.3 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609, 64-bit

OJS: → base_url (base url after update)

All folder have correct permissions read/write

  • files_dir= /home/alopez/ojs/ojs-files
  • public_files_dir= public
  • ojs3

also put in /ojs3/plugins/generic/usageStats/GeoLiteCity.dat (before run Update)

ok now → My problems is Statistics. Script update run fine and show message “Successfully upgraded to version” at the end, but Statistics not update fine.
After update script Statistics “generador de informes personalizados”
It does not work well (There are data not shown).
In /home/alopez/ojs/ojs-files/usageStats
-archive: 1 file
-reject: 1 file

E read a post (I can not find the post now) that the problem is the records that I have in reject folder.
Some lines of the file log in reject folder - - “2017-05-10 00:00:33” 200 “Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36” - - “2017-05-10 00:00:39” 200 “Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36”

I think the problem comes because
base_url = (base url after update)
base_url = (base url before update)

But I do not know how to solve it. I can’t run update in the production server, I am doing a test of migration.

Regards Cristian

The base_url in your must match the base_url in your logs for the statistics to process.

You will need to fully process any statistics generated under the old base_url, then change the base_url when you are ready to gather new statistics.

Speaking of changing, if you change the base URL, you will break any existing links from external sites. You might want to leave “/ojs248” in your URL unless you are ready to change to a URL without specifying the software and version in the URL (which would be preferable).