Hi Sean,

Can you please check all your logs for any errors being reported (not just dspace.log.[date], but also Tomcat's logs and the DSpace solr.log)? I'm just curious if an error is being reported somewhere that could give us more information about the issue with these shards. It's possible they've become corrupted somehow, or it's also possible there's an (undiscovered) bug in DSpace causing this. It's hard to tell from the limited information, and if you can locate an error message it may help us.

As a sidenote, it's worth noting that DSpace 6.0 is not yet released, and not yet considered "Production ready". It's getting close, but I wouldn't recommend running it in Production quite yet (as there's still a few known bugs we are working on resolving before the 6.0 final release. Testing the upgrade process is perfectly fine though, and that'd give us great feedback on how it is looking.

If you find any other errors in any of your logs, please pass them along to this list.

Thanks,

Tim


On 7/21/2016 4:30 AM, Sean Carte wrote:
I just remembered. I need to update the query to specify the shard, so I do get stats for previous years. But I just can't start DSpace 6.0rc3 with the shards in place.

Moving the shards out of the solr directory during startup allows me to start, but moving them back in afterwards leaves them inaccessible.

Sean

On 21 July 2016 at 11:24, Sean Carte <[email protected] <mailto:[email protected]>> wrote:

    Thanks for responding, Ivan. Yes, I do run the sharding at the
    start of every year.

    I can't find a way to view usage stats prior to 2016 on my
    original server running 5.5.

    I get results for:

    
/solr/statistics/select?q=type:2+AND+owningColl:4+AND+isBot:false+AND+time:[2016-07-01T00:00:00Z+TO+2016-08-01T00:00:00Z]&indent=on&rows=1

    But not for previous years.

    Maybe sharding wasn't such a good idea after all?

    Sean

    On 21 July 2016 at 10:41, helix84 <[email protected]
    <mailto:[email protected]>> wrote:

        Those cores were created when you chose to shard your
        statistics data [1] and hold your data for that particular
        year. If you delete them, you'll lose the statistics for that
        year. You can try to temporarily move them awat if they seem
        to block you from starting DSpace (DSpace will not attempt to
        write anything to the old shards), just don't forget to try to
        fix the problem later.

        [1]
        
https://wiki.duraspace.org/display/DSDOC5x/SOLR+Statistics+Maintenance#SOLRStatisticsMaintenance-SolrShardingByYear


        Regards,
        ~~helix84

        Compulsory reading: DSpace Mailing List Etiquette
        https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


        On Thu, Jul 21, 2016 at 10:34 AM, Sean Carte
        <[email protected] <mailto:[email protected]>> wrote:

            I've been trying to upgrade from 5.5 to 6.0 and, although
            the maven build completes successfully and the ant update
            is successful, I can't get Tomcat to start. It hangs on
            loading solr cores:

            2016-07-21 09:45:51,690 INFO
            org.dspace.statistics.SolrLoggerServiceImpl @
            solr-statistics.spidersfile:null
            2016-07-21 09:45:51,691 INFO
            org.dspace.statistics.SolrLoggerServiceImpl @
            solr-statistics.server:http://localhost:8080/solr/statistics
            2016-07-21 09:45:51,691 INFO
            org.dspace.statistics.SolrLoggerServiceImpl @
            usage-statistics.dbfile:/dspace/config/GeoLiteCity.dat
            2016-07-21 09:45:51,742 INFO
            org.dspace.statistics.SolrLoggerServiceImpl @ Loading core
            with name: statistics-2013

            If I remove the /dspace/solr/statistics-2013, Tomcat hangs
            loading a different core; if I remove all the
            /dspace/solr/statistics-201? directories Tomcat starts.

            Is it safe to remove those directories; I'm not seeing
            anything obviously wrong in the stats on the upgraded server?

            (Ubuntu 16.04; openjdk 8; Postgres 9.5; Tomcat 8; DSpace
            6.0rc3)

            Sean
-- -- 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]
            <mailto:[email protected]>.
            To post to this group, send email to
            [email protected]
            <mailto:[email protected]>.
            Visit this group at
            https://groups.google.com/group/dspace-tech.
            For more options, visit https://groups.google.com/d/optout.





--



--

--
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] <mailto:[email protected]>. To post to this group, send email to [email protected] <mailto:[email protected]>.
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

--
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.

Reply via email to