Thanks, Tim. It looks like the problem is just me though.

Looks like I can't just copy shards to another machine with a different IP
address and expect them to work.

(I did another copy of the production to a test environment, and everything
works in the test environment prior to upgrading apart from accessing the
solr shards.)

Sean

On 21 July 2016 at 16:23, Tim Donohue <[email protected]> wrote:

> Thanks Sean,
>
> Unfortunately, I'm still not seeing any ERRORs listed in those logs.  Are
> there any other log files that have been written to recently in your
> [dspace]/log/ directory (or in your Tomcat logs folder) that could provide
> clues?
> I'm still not sure what could be causing this and it seems odd to me that
> no errors are being reported anywhere.  I'm assuming the test upgrade
> process went smoothly, and no errors were reported (especially in the
> DSpace logs) when you ran your test upgrade?
>
> If there's anyone else listening in on this conversation with your own
> Solr Statistics "shards" handy, it would be worth finding someone else to
> try and test this upgrade in a similar scenario.
>
> As for the list of known 6.0 issues, we are maintaining a list of "Must
> have" fixes in 6.0 in our weekly developer meeting notes/agenda. Many
> tickets are in progress, some just need documentation, and a few are still
> outstanding issues needing resolution or re-testing.  Here's that list from
> this week's meeting:
>
> https://wiki.duraspace.org/display/DSPACE/DevMtg+2016-07-20
>
> - Tim
>
>
> On 7/21/2016 9:13 AM, Sean Carte wrote:
>
>
>
> On 21 July 2016 at 15:55, Tim Donohue <[email protected]> wrote:
>
>> 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.
>>
>  root@dspace:~# tail -f /dspace/log/dspace.log.2016-07-21
> 2016-07-21 16:09:42,845 INFO  org.hibernate.tool.hbm2ddl.TableMetadata @
> HHH000261: Table found: public.webapp
> 2016-07-21 16:09:42,846 INFO  org.hibernate.tool.hbm2ddl.TableMetadata @
> HHH000037: Columns: [webapp_id, appname, started, url, isui]
> 2016-07-21 16:09:42,853 INFO  org.hibernate.tool.hbm2ddl.TableMetadata @
> HHH000261: Table found: public.workflowitem
> 2016-07-21 16:09:42,853 INFO  org.hibernate.tool.hbm2ddl.TableMetadata @
> HHH000037: Columns: [collection_id, owner, workflow_id, published_before,
> item_id, multiple_titles, multiple_files, state, embargoduration]
> 2016-07-21 16:09:42,861 INFO  org.hibernate.tool.hbm2ddl.TableMetadata @
> HHH000261: Table found: public.workspaceitem
> 2016-07-21 16:09:42,862 INFO  org.hibernate.tool.hbm2ddl.TableMetadata @
> HHH000037: Columns: [collection_id, stage_reached, page_reached,
> published_before, item_id, multiple_titles, multiple_files,
> embargoduration, workspace_item_id]
> 2016-07-21 16:09:45,106 INFO  org.dspace.statistics.SolrLoggerServiceImpl
> @ solr-statistics.spidersfile:null
> 2016-07-21 16:09:45,107 INFO  org.dspace.statistics.SolrLoggerServiceImpl
> @ solr-statistics.server:http://localhost:8080/solr/statistics
> 2016-07-21 16:09:45,107 INFO  org.dspace.statistics.SolrLoggerServiceImpl
> @ usage-statistics.dbfile:/dspace/config/GeoLiteCity.dat
> 2016-07-21 16:09:45,163 INFO  org.dspace.statistics.SolrLoggerServiceImpl
> @ Loading core with name: statistics-2013
>
> dspace@dspace:/dspace/solr$ tail -f /dspace/log/solr.log
> [nothing written to solr.log]
>
> I've attached catalina.out.
>
> 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.
>>
> I'm only testing. Is there a list of known bugs I should look at first?
>
>> If you find any other errors in any of your logs, please pass them along
>> to this list.
>>
> I'll do so.
>
> Sean
>
>
> --
> 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