Hi Walter, All I meant is that the "solr" webapp that DSpace creates needs to be available/deployed to Tomcat. So, for example, if Tomcat is running on http://localhost:8080, then Solr should be accessible on something like http://localhost:8080/solr/
In other words, the only way DSpace can properly communicate with Solr (to send/query statistics) is if it's available in Tomcat. The full path to Solr in Tomcat should also be configured in your installed [dspace]/config/modules/solr-statistics.cfg: https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace/config/modules/solr-statistics.cfg#L12 If DSpace is unable to find/communicate with Solr, you likely would see errors appearing in your logs. - Tim On Tue, Oct 9, 2018 at 2:04 PM <wlrutherf...@alaska.edu> wrote: > Thank you Tim. I didn't notice anything in the logs that seemed to point > to a problem with Solr > or the statistics. I'll look again to make sure I haven't overlooked > something. Also checking the > troubleshooting page you linked. > > I'm not sure what you mean by the DSpace Solr webapp, *must* be installed > into Tomcat. Are > you talking about during the build it must be configured with Tomcat or > that it is configured in > the [dspace]/webapps/solr directory after DSpace has been built? > > Walter R. > > > On Tuesday, October 9, 2018 at 10:28:53 AM UTC-8, Tim Donohue wrote: > >> Hi Walter, >> >> I'd recommend checking your logs for any errors or warnings. We have a >> guide for doing so at: >> https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error >> >> DSpace does *require* using Solr for Statistics. However, the required >> "solr" webapp is provided out-of-the-box with DSpace (it is built into the >> [dspace]/webapps/solr/ directory), so you do not need to install Apache >> Solr separately. That DSpace Solr webapp *must* be installed into Tomcat >> (alongside your UI, either XMLUI or JSPUI) for Statistics to work properly. >> >> Any errors that are occurring with accessing or logging statistics should >> be logged in your dspace.log file (or, occasionally, in the Tomcat logs). >> >> In the XMLUI, blank pages usually mean something went wrong. Most of the >> time, you should have more information in your logs. However, if no >> information is found there, it's always possible that the problem is in >> your *theme* (XSLTs or similar). So, if you get stuck, you may also want >> to try temporarily switching to a default DSpace theme, to ensure your >> custom theme is not causing issues. >> >> If you have more information to share, or start to figure out what might >> be to blame, please let us know on this mailing list. Currently, though, >> it doesn't look like we have enough information to provide help (unless >> someone else on this mailing list has seen this exact same behavior before). >> >> Tim >> >> On Mon, Oct 8, 2018 at 5:12 PM <wlruth...@alaska.edu> wrote: >> > >>> I'm still having problems with the statistics in DSpace. I have an older >>> server running DSpace3.1 which is >>> a "copy" of the original system. The statistics apparently haven't >>> worked since the system moved. The 2nd >>> system is running DSpace5.5. On both systems there is a "View Usage >>> Statistics" link on the Home page >>> but following the link gives a valid, live page but with no numbers. The >>> Search and Workflow statistic links >>> give identical error messages on both systems. >>> >>> I have gone through the manual and tried enabling all of the >>> configuration parameters mentioned but with >>> no luck. I even tried a few which didn't at first seem necessary but >>> couldn't hurt. Still nothing. >>> >>> The manual says that DSpace uses Apache Solr and there is no need to >>> download any separate software. >>> But something isn't working. Do I really need to install and run Apache >>> Solr? What I'm I misconfiguring? >>> >>> Does this look familiar to anyone? >>> >>> DSpace3.1 system: https://scholarworks.alaska.edu/statistics-home >>> (may be behind firewall) >>> DSpace5.5 system: >>> https://dspace36a.library.uaf.edu/xmlui/statistics-home >>> >>> Thank you, >>> >>> Walter Rutherford >>> >>> -- >>> 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 dspace-tech...@googlegroups.com. >>> To post to this group, send email to dspac...@googlegroups.com. >> >> >>> Visit this group at https://groups.google.com/group/dspace-tech. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> Tim Donohue >> Technical Lead for DSpace & DSpaceDirect >> DuraSpace.org | DSpace.org | DSpaceDirect.org >> > -- > 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 dspace-tech+unsubscr...@googlegroups.com. > To post to this group, send email to dspace-tech@googlegroups.com. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
