Dear list, For the record, I have just hit this bug on a new deployment of our DSpace 5.8 code base today. After a few hours of troubleshooting I realized that the issue with Solr not logging VIEW events is a side effect of the deprecation of the GeoLite v1 database by MaxMind in 2019-01¹. Frustratingly, the absence of this database causes DSpace to silently drop VIEW events with no warning or error in the dspace or solr logs. DSpace 5.10 solves this by migrating to GeoLite2, but as our code base is stuck on DSpace 5.8 for now, I found a copy of the GeoLite v1 database (GeoLiteCity.dat) on an older server and copied it to the [dspace]/config directory. Now my VIEW events are being logged properly.
Hope this helps someone, ¹ https://support.maxmind.com/geolite-legacy-discontinuation-notice/ ² https://jira.duraspace.org/browse/DS-4020 On Tue, Aug 21, 2018 at 7:21 PM Bill T <[email protected]> wrote: > OK, see https://github.com/DSpace/DSpace/pull/2177 > > Hopefully I have followed the procedures correctly -- you can also > followup on slack... > > On Tuesday, August 21, 2018 at 9:09:32 AM UTC-5, Bill T wrote: >> >> I submit a patch asap -- later today. >> >> On Tuesday, August 21, 2018 at 8:09:00 AM UTC-5, Mark H. Wood wrote: >>> >>> On Monday, August 20, 2018 at 3:35:08 PM UTC-4, Bill T wrote: >>>> >>>> Testing that latest upgrade, I do not see any views getting logged in >>>> solr statistics. >>>> >>>> I think this may be a result of this code in SolrLogger.java >>>> >>>> String dbPath = >>>> ConfigurationManager.getProperty("usage-statistics.dbfile"); >>>> >>>> at line 173. This should be >>>> >>>> String dbPath = >>>> ConfigurationManager.getProperty("usage-statistics", "dbfile"); >>>> >>>> right? Else dbPath is null resulting in dbFile == null as well. >>>> >>>> if dbFile is null, then postView() returns immediately. (There may be >>>> other repercussions as well...) >>>> >>>> If this looks like a a bug (and an unreported one) let me know and I >>>> will submit a patch. At least it fixed the problem for me. >>>> >>>> >>> >>> Yes, the first form would have results identical to the second in DSpace >>> v6 but not in v5. (There was much rewriting of the configuration service >>> in v6.) It's a bug. >>> >> -- > All messages to this mailing list should adhere to the DuraSpace Code of > Conduct: https://duraspace.org/about/policies/code-of-conduct/ > --- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- Alan Orth [email protected] https://picturingjordan.com https://englishbulgaria.net https://mjanja.ch "In heaven all the interesting people are missing." ―Friedrich Nietzsche -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
