@itcrowdsource opened this Issue on December 14th 2018

After the 3.7.0 upgrade the real-time visitor map stopped working. See issue #13833 .The whole import process seems to be working properly. And I also can't find any errors during the import and in the logs.

python /.../.../.../.../.../import_logs.py --log-format-name=shoutcast --url=http://x.x.x.x --idsite=4 /.../.../sc_w3c.log
0 lines parsed, 0 lines recorded, 0 records/sec (avg), 0 records/sec (current)
Parsing log /.../.../sc_w3c.log...
1066 lines parsed, 200 lines recorded, 199 records/sec (avg), 200 records/sec (current)
1473 lines parsed, 600 lines recorded, 299 records/sec (avg), 400 records/sec (current)
1699 lines parsed, 800 lines recorded, 266 records/sec (avg), 200 records/sec (current)
1923 lines parsed, 1200 lines recorded, 299 records/sec (avg), 400 records/sec (current)
2346 lines parsed, 1400 lines recorded, 279 records/sec (avg), 200 records/sec (current)
2775 lines parsed, 1800 lines recorded, 299 records/sec (avg), 400 records/sec (current)
2986 lines parsed, 2000 lines recorded, 285 records/sec (avg), 200 records/sec (current)
3195 lines parsed, 2200 lines recorded, 274 records/sec (avg), 200 records/sec (current)
3611 lines parsed, 2600 lines recorded, 288 records/sec (avg), 400 records/sec (current)
3816 lines parsed, 2800 lines recorded, 279 records/sec (avg), 200 records/sec (current)
4244 lines parsed, 3200 lines recorded, 290 records/sec (avg), 400 records/sec (current)
4460 lines parsed, 3400 lines recorded, 283 records/sec (avg), 200 records/sec (current)
4668 lines parsed, 3600 lines recorded, 276 records/sec (avg), 200 records/sec (current)
5083 lines parsed, 4000 lines recorded, 285 records/sec (avg), 400 records/sec (current)
5289 lines parsed, 4200 lines recorded, 279 records/sec (avg), 200 records/sec (current)
5703 lines parsed, 4600 lines recorded, 287 records/sec (avg), 400 records/sec (current)
5906 lines parsed, 4800 lines recorded, 282 records/sec (avg), 200 records/sec (current)
6313 lines parsed, 5200 lines recorded, 288 records/sec (avg), 400 records/sec (current)
6516 lines parsed, 5400 lines recorded, 283 records/sec (avg), 200 records/sec (current)
6925 lines parsed, 5800 lines recorded, 289 records/sec (avg), 400 records/sec (current)
7129 lines parsed, 6000 lines recorded, 285 records/sec (avg), 200 records/sec (current)
7559 lines parsed, 6400 lines recorded, 290 records/sec (avg), 400 records/sec (current)
7771 lines parsed, 6600 lines recorded, 286 records/sec (avg), 200 records/sec (current)
8097 lines parsed, 7000 lines recorded, 291 records/sec (avg), 400 records/sec (current)
8406 lines parsed, 7200 lines recorded, 287 records/sec (avg), 200 records/sec (current)
8844 lines parsed, 7600 lines recorded, 291 records/sec (avg), 400 records/sec (current)
9061 lines parsed, 7800 lines recorded, 288 records/sec (avg), 200 records/sec (current)
9407 lines parsed, 8200 lines recorded, 292 records/sec (avg), 400 records/sec (current)
9702 lines parsed, 8400 lines recorded, 289 records/sec (avg), 200 records/sec (current)
10120 lines parsed, 8800 lines recorded, 293 records/sec (avg), 400 records/sec (current)
10336 lines parsed, 9000 lines recorded, 290 records/sec (avg), 200 records/sec (current)
10770 lines parsed, 9400 lines recorded, 293 records/sec (avg), 400 records/sec (current)
11204 lines parsed, 9800 lines recorded, 296 records/sec (avg), 400 records/sec (current)
11541 lines parsed, 10200 lines recorded, 299 records/sec (avg), 400 records/sec (current)
11848 lines parsed, 10400 lines recorded, 296 records/sec (avg), 200 records/sec (current)
12283 lines parsed, 10800 lines recorded, 299 records/sec (avg), 400 records/sec (current)
12495 lines parsed, 11000 lines recorded, 296 records/sec (avg), 200 records/sec (current)
12921 lines parsed, 11400 lines recorded, 299 records/sec (avg), 400 records/sec (current)
13349 lines parsed, 11800 lines recorded, 302 records/sec (avg), 400 records/sec (current)
13566 lines parsed, 12000 lines recorded, 299 records/sec (avg), 200 records/sec (current)
13996 lines parsed, 12400 lines recorded, 302 records/sec (avg), 400 records/sec (current)
14211 lines parsed, 12600 lines recorded, 299 records/sec (avg), 200 records/sec (current)
14425 lines parsed, 12800 lines recorded, 297 records/sec (avg), 200 records/sec (current)
14874 lines parsed, 13200 lines recorded, 299 records/sec (avg), 400 records/sec (current)
15083 lines parsed, 13400 lines recorded, 297 records/sec (avg), 200 records/sec (current)
15525 lines parsed, 13800 lines recorded, 299 records/sec (avg), 400 records/sec (current)
15770 lines parsed, 14200 lines recorded, 301 records/sec (avg), 400 records/sec (current)
16176 lines parsed, 14400 lines recorded, 299 records/sec (avg), 200 records/sec (current)
16602 lines parsed, 14800 lines recorded, 301 records/sec (avg), 400 records/sec (current)
16818 lines parsed, 15000 lines recorded, 299 records/sec (avg), 200 records/sec (current)
17269 lines parsed, 15400 lines recorded, 301 records/sec (avg), 400 records/sec (current)
17494 lines parsed, 15600 lines recorded, 299 records/sec (avg), 200 records/sec (current)
17929 lines parsed, 16000 lines recorded, 301 records/sec (avg), 400 records/sec (current)
18363 lines parsed, 16400 lines recorded, 303 records/sec (avg), 400 records/sec (current)
18584 lines parsed, 16600 lines recorded, 301 records/sec (avg), 200 records/sec (current)
19003 lines parsed, 17000 lines recorded, 303 records/sec (avg), 400 records/sec (current)
19307 lines parsed, 17400 lines recorded, 304 records/sec (avg), 400 records/sec (current)
19661 lines parsed, 17600 lines recorded, 303 records/sec (avg), 200 records/sec (current)
19885 lines parsed, 18000 lines recorded, 304 records/sec (avg), 400 records/sec (current)
20321 lines parsed, 18200 lines recorded, 302 records/sec (avg), 200 records/sec (current)
20539 lines parsed, 18400 lines recorded, 301 records/sec (avg), 200 records/sec (current)
20988 lines parsed, 18800 lines recorded, 302 records/sec (avg), 400 records/sec (current)
21434 lines parsed, 19200 lines recorded, 304 records/sec (avg), 400 records/sec (current)
21599 lines parsed, 19400 lines recorded, 302 records/sec (avg), 200 records/sec (current)
21599 lines parsed, 19800 lines recorded, 304 records/sec (avg), 400 records/sec (current)
21599 lines parsed, 20146 lines recorded, 304 records/sec (avg), 346 records/sec (current)

Logs import summary
-------------------

    20146 requests imported successfully
    0 requests were downloads
    1453 requests ignored:
        0 HTTP errors
        0 HTTP redirects
        0 invalid log lines
        0 filtered log lines
        0 requests did not match any known site
        0 requests did not match any --hostname
        1453 requests done by bots, search engines...
        0 requests to static resources (css, js, images, ico, ttf...)
        0 requests to file downloads did not match any --download-extensions

Website import summary
----------------------

    20146 requests imported to 1 sites
        1 sites already existed
        0 sites were created:

    0 distinct hostnames did not match any existing site:

Performance summary
-------------------

    Total time: 66 seconds
    Requests imported per second: 304.49 requests per second

Processing your log data
------------------------

    In order for your logs to be processed by Matomo, you may need to run the following command:
     ./console core:archive --force-all-websites --force-all-periods=315576000 --force-date-last-n=1000 --url='http://x.x.x.x'

+ cd /var/www/html
+ ./console core:archive --force-all-websites --force-all-periods=315576000 --force-date-last-n=1000 --url=http://x.x.x.x
INFO [2018-12-14 19:23:55] 19649  ---------------------------
INFO [2018-12-14 19:23:55] 19649  INIT
INFO [2018-12-14 19:23:55] 19649  Running Matomo 3.7.0 as Super User
INFO [2018-12-14 19:23:55] 19649  ---------------------------
INFO [2018-12-14 19:23:55] 19649  NOTES
INFO [2018-12-14 19:23:55] 19649  - If you execute this script at least once per hour (or more often) in a crontab, you may disable 'Browser trigger archiving' in Matomo UI > Settings > General Settings.
INFO [2018-12-14 19:23:55] 19649    See the doc at: https://matomo.org/docs/setup-auto-archiving/
INFO [2018-12-14 19:23:55] 19649  - Reports for today will be processed at most every 150 seconds. You can change this value in Matomo UI > Settings > General Settings.
INFO [2018-12-14 19:23:55] 19649  - Reports for the current week/month/year will be requested at most every 3600 seconds.
INFO [2018-12-14 19:23:55] 19649  - Archiving was last executed without error 18 min 35s ago
INFO [2018-12-14 19:23:55] 19649  - Will invalidate archived reports for 2018-12-06 for following websites ids: 4
INFO [2018-12-14 19:23:55] 19649  - Will invalidate archived reports for 2018-12-07 for following websites ids: 4
INFO [2018-12-14 19:23:55] 19649  - Will process 1 other websites because some old data reports have been invalidated (eg. using the Log Import script or the InvalidateReports plugin) , IDs: 4
INFO [2018-12-14 19:23:55] 19649  - Will process all 1 websites
INFO [2018-12-14 19:23:55] 19649  ---------------------------
INFO [2018-12-14 19:23:55] 19649  START
INFO [2018-12-14 19:23:55] 19649  Starting Matomo reports archiving...
INFO [2018-12-14 19:23:55] 19649  Will pre-process for website id = 4, period = day, date = last1000
INFO [2018-12-14 19:23:55] 19649  - pre-processing all visits
INFO [2018-12-14 19:28:10] 19649  Archived website id = 4, period = day, 0 segments, 14088 visits in last 1000 days, 0 visits today, Time elapsed: 254.881s
INFO [2018-12-14 19:28:10] 19649  Will pre-process for website id = 4, period = week, date = last1000
INFO [2018-12-14 19:28:10] 19649  - pre-processing all visits
INFO [2018-12-14 19:28:13] 19649  Archived website id = 4, period = week, 0 segments, 14088 visits in last 1000 weeks, 0 visits this week, Time elapsed: 3.070s
INFO [2018-12-14 19:28:14] 19649  Will pre-process for website id = 4, period = month, date = last1000
INFO [2018-12-14 19:28:14] 19649  - pre-processing all visits
INFO [2018-12-14 19:28:15] 19649  Archived website id = 4, period = month, 0 segments, 14088 visits in last 1000 months, 14088 visits this month, Time elapsed: 1.700s
INFO [2018-12-14 19:28:15] 19649  Will pre-process for website id = 4, period = year, date = last1000
INFO [2018-12-14 19:28:15] 19649  - pre-processing all visits
INFO [2018-12-14 19:28:16] 19649  Archived website id = 4, period = year, 0 segments, 14088 visits in last 1000 years, 14088 visits this year, Time elapsed: 1.202s
INFO [2018-12-14 19:28:16] 19649  Archived website id = 4, 4 API requests, Time elapsed: 260.876s [1/1 done]
INFO [2018-12-14 19:28:16] 19649  Done archiving!
INFO [2018-12-14 19:28:16] 19649  ---------------------------
INFO [2018-12-14 19:28:16] 19649  SUMMARY
INFO [2018-12-14 19:28:16] 19649  Total visits for today across archived websites: 0
INFO [2018-12-14 19:28:16] 19649  Archived today's reports for 1 websites
INFO [2018-12-14 19:28:16] 19649  Archived week/month/year for 1 websites
INFO [2018-12-14 19:28:16] 19649  Skipped 0 websites
INFO [2018-12-14 19:28:16] 19649  - 0 skipped because no new visit since the last script execution
INFO [2018-12-14 19:28:16] 19649  - 0 skipped because existing daily reports are less than 150 seconds old
INFO [2018-12-14 19:28:16] 19649  - 0 skipped because existing week/month/year periods reports are less than 3600 seconds old
INFO [2018-12-14 19:28:16] 19649  Total API requests: 4
INFO [2018-12-14 19:28:16] 19649  done: 1/1 100%, 0 vtoday, 1 wtoday, 1 wperiods, 4 req, 261026 ms, no error
INFO [2018-12-14 19:28:16] 19649  Time elapsed: 261.026s
INFO [2018-12-14 19:28:16] 19649  ---------------------------
INFO [2018-12-14 19:28:16] 19649  SCHEDULED TASKS
INFO [2018-12-14 19:28:16] 19649  Starting Scheduled tasks...
INFO [2018-12-14 19:28:16] 19649  done
INFO [2018-12-14 19:28:16] 19649  ---------------------------
@tsteur commented on December 15th 2018 Member

It works fine for us and we haven't heard any similar issue. Can you check the developer tools in the browser to see if there is a JavaScript error maybe?

@sgiehl commented on December 21st 2018 Member

@itcrowdsource Which version did you use before and did you maybe change any settings for geo location? Maybe the geolocation provider doesn't work anymore and thus the realtime map has no location data to display.

@itcrowdsource commented on December 21st 2018

@sgiehl @tsteur I found out that something went wrong in a replication process of the file being imported. So this isn't related to Matomo. My apologies for that.

This Issue was closed on December 21st 2018
Powered by GitHub Issue Mirror