Re: [dspace-tech] "Invalid UUID string" in Solr search core after DSpace 6 upgrade

[Alan Orth]

Dear Mark,

Is there a difference in the automatic re-indexing that is triggered by the
existence of the `dspace/solr/search/conf/reindex.flag` and a manually
triggered `dspace index-discovery -b`? After my database migration was
completed I started Tomcat and then immediately triggered a manual
re-indexing. I lost a few hours investigating the cause of this, only to
stumble on the fact that the "automatic" re-indexing apparently does
something differently—the effects of which are only visible if the
"automatic" re-indexing actually completes without interruption! Very
strange...

Regards,

On Tue, Feb 4, 2020 at 4:37 PM Mark H. Wood  wrote:

> On Tue, Feb 04, 2020 at 12:11:22PM +0200, Alan Orth wrote:
> > I'm testing DSpace version 5.8 to 6.3 upgrade. Immediately after
> performing
> > the database migrations successfully and starting Tomcat I initiated a
> > `dspace index-discovery -b`. I thought something was strange because I
> > didn't see any indexing progress in dspace.log (despite high CPU usage),
> > and then when I browsed the home page I saw many errors such as this in
> > dspace.log:
> >
> > 2020-02-03 10:27:14,485 ERROR org.dspace.browse.ItemCountDAOSolr @
> > caught exception:
> > org.dspace.discovery.SearchServiceException: Invalid UUID string: 1
> > 2020-02-03 13:20:20,475 ERROR
> > org.dspace.app.xmlui.aspect.discovery.AbstractRecentSubmissionTransformer
> > @ Caught SearchServiceException while retrieving recent submission
> > for: home page
> > org.dspace.discovery.SearchServiceException: Invalid UUID string: 111210
> >
> > I checked Solr's search core and saw that the search.resourceid fields
> were
> > indeed integers instead of UUIDs. On a guess I stopped the indexing,
> > deleted the search cores¹, touched an empty file in
> > dspace/solr/search/conf/reindex.flag², and restarted Tomcat. After Tomcat
> > started back up the re-indexing started and correctly indexed
> > search.resourceid as UUIDs.
> >
> > After the initial reindex.flag indexing completes, subsequent manual
> > indexing runs with `dspace index-discovery -b` work correctly. This only
> > seems to happen the first time after upgrade—I tried deleting all search
> > documents and starting a `dspace index-discovery -b` and it behaved
> > correctly.
> >
> > Has anyone seen this? Is it worth filing a bug? Are there perhaps some
> > fixes in the as-of-yet-unreleased 6.4 that would address this?
> >
> > Regards,
> >
> > ¹ curl -s 'http://localhost:8080/solr/search/update?stream.body=
> > *:*=true'
> > ² https://wiki.lyrasis.org/display/DSDOC6x/Upgrading+DSpace
>
> According to https://wiki.lyrasis.org/display/DSDOC6x/Upgrading+DSpace
> the 'search' core should have been reindexed automatically, unless you
> disabled that (as discussed further down that page) and then did not
> follow through with a manual reindex.
>
> You should also be aware of a usage statistics issue which will be
> addressed in 6.4:
>
>
> https://wiki.lyrasis.org/display/DSDOC6x/SOLR+Statistics+Maintenance#SOLRStatisticsMaintenance-UpgradeLegacyDSpaceObjectIdentifiers(pre-6xstatistics)toDSpace6xUUIDIdentifiers
>   https://jira.lyrasis.org/browse/DS-4110
>
> --
> Mark H. Wood
> Lead Technology Analyst
>
> University Library
> Indiana University - Purdue University Indianapolis
> 755 W. Michigan Street
> Indianapolis, IN 46202
> 317-274-0749
> www.ulib.iupui.edu
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/20200204143736.GB14849%40IUPUI.Edu
> .
>


-- 
Alan Orth
alan.o...@gmail.com
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 dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAKKdN4VHr8yep6DyCbzz8-qjLJmS389PHKnRASefTh6eke7cag%40mail.gmail.com.

Re: [dspace-tech] Build failure for installing Mirage 2 in Dspace...Cannot run program "npm"

[Ndong, Maguette]

Hello Yerodin,

Try to install JRuby through rvm (If I remember it’s rvm install jruby)
Be sure that rvm is using ruby as current and default (check with rvm list and 
rvm use default ruby-xx.xx)

And in your “dspace-src/modules/xmlui-mirage2/pom.xml”, add this 
9.2.6.0 under your npm version



Hope it will work for you! 



Cheers,



[/var/folders/75/tk9dnd5n1190v6mj0b5g1bdmgn/T/com.microsoft.Outlook/WebArchiveCopyPasteTempFiles/cidimage005.jpg@01D44A8E.8DDB7BD0]Maguette
 Thioro NDONG
Technical Advisor
Mail: PO Box 15115  |  Dakar Fann
Address: Fann Résidence Rue Saint John Perse x F  |  Dakar Senegal
Tel: +221 33 869 11 51  |  Mobile: +221 77 096 60 54

stay connected: [cid:image007.jpg@01D3533C.94570370] 
@DigitalSQR | 
digitalsquare.org






From:  on behalf of Yerodin P 
Date: Tuesday, February 4, 2020 at 2:54 PM
Cc: "dspace-tech@googlegroups.com" 
Subject: Re: [dspace-tech] Build failure for installing Mirage 2 in 
Dspace...Cannot run program "npm"

Good day all,

Okay,

Can those of you running the Mirage2 responsive theme assist with the answer to 
this question?

In-spite of the following warnings:

1. Bower

$ npm install -g bower
npm WARN deprecated bower@1.8.8: We don't recommend using Bower for new 
projects. Please consider Yarn and Webpack or Parcel.


2. Ruby SASS

$ gem install sass -v 3.3.14
Ruby Sass Has Reached End-of-Life
Ruby Sass should no longer be used, and will no longer be receiving any 
updates. See the Sass blog, and consider switching to the sassc gem

.were those of you running DSpace's Mirage2 theme, able to successfully 
implement the theme in-spite of these warnings?

Yerodin P
DSpace newbie.

On Tue, Feb 4, 2020 at 9:40 AM Yerodin P 
mailto:yerod...@gmail.com>> wrote:
Thank you for the hint Paul,
Forgive me if you get this twice as I did a "reply all" from my Gmail account.
I will try just the 
dspace-tech@googlegroups.com in my next 
post.

Anyway..

Close inspection indicates that your counsel is part of the steps described 
here:
https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-xmlui-mirage2/readme.md#compass
 for loading Mirage2 prerequisites.

I did encounter this suggestion after running the command:
$ curl -o- 
https://raw.githubusercontent.com/creationix/nvm/v0.31.7/install.sh
 | bash

=> Close and reopen your terminal to start using nvm or run the following to 
use it now:
$ export NVM_DIR="/home/yerodinp/.nvm"
$ [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"


Hence, I am interpreting your hint to mean I should look to see if I missed any 
important steps, or didn't read and understand the provided instructions 
properly.

According to the DSpace literature, once Mirage2 prerequisites are successfully 
loaded, the build and implementation of Mirage2 should be easy peasy.

Will report my findings regardless of outcome and post solution if I find out 
what I was doing wrong.

Yerodin P
DSpace newbie.


On Mon, Feb 3, 2020 at 10:58 AM Paul Münch 
mailto:muen...@staff.uni-marburg.de>> wrote:
Hello,

during Node installation there is a hint:

export NVM_DIR="$HOME/.nvm"

[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"


Use this in a script before the maven run. Or add it to your environment in a 
different way.

I hope this helps and kind regards,

Paul Münch
Am 31.01.20 um 21:29 schrieb Yerodin P:

Good Day all,

Before I post for help with my problem, here are the system specifics on which 
I am running DSpace v6.3:

- Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz, 2 cores, 4GB RAM
- Ubuntu Server 18.04.2 LTS
- PostgreSQL v10.10
- OpenSSH_7.6
- Tomcat7 in one instance and Tomcat8 in another.
- javac 1.8.0_242
- openjdk version "1.8.0_242"
OpenJDK Runtime Environment (build 1.8.0_242-8u242-b08-0ubuntu3~18.04-b08)
OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode)

- Apache Maven 3.6.0
Maven home: /usr/share/maven
Java version: 1.8.0_242, vendor: Private Build, runtime: 
/usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-76-generic", arch: "amd64", family: "unix"


- Git version 2.17.1
- $ rvm requirements
Checking requirements for ubuntu.
Requirements installation successful.

- Compass successfully installed
- Ruby-2.6.3 installed.
- 

Re: [dspace-tech] Build failure for installing Mirage 2 in Dspace...Cannot run program "npm"

[Yerodin P]

Good day all,

Okay,

Can those of you running the Mirage2 responsive theme assist with the
answer to this question?

In-spite of the following warnings:

1. Bower

$ npm install -g bower
npm WARN deprecated bower@1.8.8: We don't recommend using Bower for new
projects. Please consider Yarn and Webpack or Parcel.


2. Ruby SASS

$ gem install sass -v 3.3.14
Ruby Sass Has Reached End-of-Life
Ruby Sass should no longer be used, and will no longer be receiving any
updates. See the Sass blog, and consider switching to the sassc gem

.were those of you running DSpace's Mirage2 theme, able to successfully
implement the theme in-spite of these warnings?

Yerodin P
DSpace newbie.

On Tue, Feb 4, 2020 at 9:40 AM Yerodin P  wrote:

> Thank you for the hint Paul,
> Forgive me if you get this twice as I did a "reply all" from my Gmail
> account.
> I will try just the dspace-tech@googlegroups.com in my next post.
>
> Anyway..
>
> Close inspection indicates that your counsel is part of the steps
> described here:
>
> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-xmlui-mirage2/readme.md#compass
>
>  for loading Mirage2 prerequisites.
>
> I did encounter this suggestion after running the command:
> $ curl -o-
> https://raw.githubusercontent.com/creationix/nvm/v0.31.7/install.sh
>  | bash
>
>
> => Close and reopen your terminal to start using nvm or run the following to 
> use it now:
> $ export NVM_DIR="/home/yerodinp/.nvm"
> $ [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
>
>
> Hence, I am interpreting your hint to mean I should look to see if I
> missed any important steps, or didn't read and understand the provided
> instructions properly.
>
> According to the DSpace literature, once Mirage2 prerequisites are
> successfully loaded, the build and implementation of Mirage2 should be easy
> peasy.
>
> Will report my findings regardless of outcome and post solution if I find
> out what I was doing wrong.
>
> Yerodin P
> DSpace newbie.
>
>
> On Mon, Feb 3, 2020 at 10:58 AM Paul Münch 
> wrote:
>
>> Hello,
>>
>> during Node installation there is a hint:
>>
>> export NVM_DIR="$HOME/.nvm"[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"
>>
>>
>> Use this in a script before the maven run. Or add it to your environment
>> in a different way.
>>
>> I hope this helps and kind regards,
>>
>> Paul Münch
>>
>> Am 31.01.20 um 21:29 schrieb Yerodin P:
>>
>>
>> Good Day all,
>>
>> Before I post for help with my problem, here are the system specifics on
>> which I am running DSpace v6.3:
>>
>> - Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz, 2 cores, 4GB RAM
>> - Ubuntu Server 18.04.2 LTS
>> - PostgreSQL v10.10
>> - OpenSSH_7.6
>> - Tomcat7 in one instance and Tomcat8 in another.
>> - javac 1.8.0_242
>> - openjdk version "1.8.0_242"
>> OpenJDK Runtime Environment (build 1.8.0_242-8u242-b08-0ubuntu3~18.04-b08)
>> OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode)
>>
>> - Apache Maven 3.6.0
>> Maven home: /usr/share/maven
>> Java version: 1.8.0_242, vendor: Private Build, runtime:
>> /usr/lib/jvm/java-8-openjdk-amd64/jre
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "linux", version: "4.15.0-76-generic", arch: "amd64", family:
>> "unix"
>>
>>
>> - Git version 2.17.1
>> - $ rvm requirements
>> Checking requirements for ubuntu.
>> Requirements installation successful.
>>
>> - Compass successfully installed
>> - Ruby-2.6.3 installed.
>> - home/useraccount/.nvm/versions/node/v6.5.0/lib
>> ├── bower@1.8.8
>> ├── grunt@1.0.4
>> ├── grunt-cli@1.3.2
>>
>> Please note:
>> The standard Mirage XMLUI theme works fine for me.
>> I have been able as a DSpace Admin, to do such things as batch upload of
>> files and execute search statistics.
>>
>>
>> *MY DSPACE PROBLEM*
>>
>> I was able to successfully:
>>
>> - load the pre-requisites for Mirage2
>> - edit [dspace-source]/dspace/config/xmlui.xconf  to uncomment the
>> regular Mirage theme and add:
>> 
>>
>> - make adjustments to the file
>> [dspace-source]/dspace-6.3-release/dspace/modules/xmlui-mirage2//pom.xml
>> where I changed the version of the dependencies to reflect what was
>> actually loaded.
>>
>> However, when I eventually ran:
>> $ mvn -Dmirage2.on=true -Dmirage2.deps.included=false clean package
>>
>> Even though the directory
>>
>> /build/dspace-6.3-release/dspace/modules/xmlui-mirage2/target/themes/
>>
>> ..does exist, I got the following error message and am temporarily stuck
>> at this part of the Mirage2 installation:
>>
>> [INFO]
>> 
>> [INFO] Reactor Summary for DSpace Parent Project 6.3:
>> [INFO]
>> [INFO] DSpace Parent Project .. SUCCESS [
>> 29.677 s]
>> [INFO] DSpace Addon Modules ... SUCCESS [
>> 0.019 s]
>> [INFO] DSpace Kernel :: Additions and Local Customizations  SUCCESS
>> [01:42 min]
>> [INFO] DSpace XML-UI Mirage2 Theme :: Local Customisations  FAILURE [
>> 49.864 s]
>> [INFO] DSpace XML-UI (Manakin) :: 

Re: [dspace-tech] "Invalid UUID string" in Solr search core after DSpace 6 upgrade

[Mark H. Wood]

On Tue, Feb 04, 2020 at 12:11:22PM +0200, Alan Orth wrote:
> I'm testing DSpace version 5.8 to 6.3 upgrade. Immediately after performing
> the database migrations successfully and starting Tomcat I initiated a
> `dspace index-discovery -b`. I thought something was strange because I
> didn't see any indexing progress in dspace.log (despite high CPU usage),
> and then when I browsed the home page I saw many errors such as this in
> dspace.log:
> 
> 2020-02-03 10:27:14,485 ERROR org.dspace.browse.ItemCountDAOSolr @
> caught exception:
> org.dspace.discovery.SearchServiceException: Invalid UUID string: 1
> 2020-02-03 13:20:20,475 ERROR
> org.dspace.app.xmlui.aspect.discovery.AbstractRecentSubmissionTransformer
> @ Caught SearchServiceException while retrieving recent submission
> for: home page
> org.dspace.discovery.SearchServiceException: Invalid UUID string: 111210
> 
> I checked Solr's search core and saw that the search.resourceid fields were
> indeed integers instead of UUIDs. On a guess I stopped the indexing,
> deleted the search cores¹, touched an empty file in
> dspace/solr/search/conf/reindex.flag², and restarted Tomcat. After Tomcat
> started back up the re-indexing started and correctly indexed
> search.resourceid as UUIDs.
> 
> After the initial reindex.flag indexing completes, subsequent manual
> indexing runs with `dspace index-discovery -b` work correctly. This only
> seems to happen the first time after upgrade—I tried deleting all search
> documents and starting a `dspace index-discovery -b` and it behaved
> correctly.
> 
> Has anyone seen this? Is it worth filing a bug? Are there perhaps some
> fixes in the as-of-yet-unreleased 6.4 that would address this?
> 
> Regards,
> 
> ¹ curl -s 'http://localhost:8080/solr/search/update?stream.body=
> *:*=true'
> ² https://wiki.lyrasis.org/display/DSDOC6x/Upgrading+DSpace

According to https://wiki.lyrasis.org/display/DSDOC6x/Upgrading+DSpace
the 'search' core should have been reindexed automatically, unless you
disabled that (as discussed further down that page) and then did not
follow through with a manual reindex.

You should also be aware of a usage statistics issue which will be
addressed in 6.4:

  
https://wiki.lyrasis.org/display/DSDOC6x/SOLR+Statistics+Maintenance#SOLRStatisticsMaintenance-UpgradeLegacyDSpaceObjectIdentifiers(pre-6xstatistics)toDSpace6xUUIDIdentifiers
  https://jira.lyrasis.org/browse/DS-4110

-- 
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/20200204143736.GB14849%40IUPUI.Edu.


signature.asc
Description: PGP signature

Re: [dspace-tech] Build failure for installing Mirage 2 in Dspace...Cannot run program "npm"

[Yerodin P]

Thank you for the hint Paul,
Forgive me if you get this twice as I did a "reply all" from my Gmail
account.
I will try just the dspace-tech@googlegroups.com in my next post.

Anyway..

Close inspection indicates that your counsel is part of the steps described
here:
https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-xmlui-mirage2/readme.md#compass

 for loading Mirage2 prerequisites.

I did encounter this suggestion after running the command:
$ curl -o-
https://raw.githubusercontent.com/creationix/nvm/v0.31.7/install.sh | bash

=> Close and reopen your terminal to start using nvm or run the
following to use it now:
$ export NVM_DIR="/home/yerodinp/.nvm"
$ [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"


Hence, I am interpreting your hint to mean I should look to see if I missed
any important steps, or didn't read and understand the provided
instructions properly.

According to the DSpace literature, once Mirage2 prerequisites are
successfully loaded, the build and implementation of Mirage2 should be easy
peasy.

Will report my findings regardless of outcome and post solution if I find
out what I was doing wrong.

Yerodin P
DSpace newbie.


On Mon, Feb 3, 2020 at 10:58 AM Paul Münch 
wrote:

> Hello,
>
> during Node installation there is a hint:
>
> export NVM_DIR="$HOME/.nvm"[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"
>
>
> Use this in a script before the maven run. Or add it to your environment
> in a different way.
>
> I hope this helps and kind regards,
>
> Paul Münch
>
> Am 31.01.20 um 21:29 schrieb Yerodin P:
>
>
> Good Day all,
>
> Before I post for help with my problem, here are the system specifics on
> which I am running DSpace v6.3:
>
> - Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz, 2 cores, 4GB RAM
> - Ubuntu Server 18.04.2 LTS
> - PostgreSQL v10.10
> - OpenSSH_7.6
> - Tomcat7 in one instance and Tomcat8 in another.
> - javac 1.8.0_242
> - openjdk version "1.8.0_242"
> OpenJDK Runtime Environment (build 1.8.0_242-8u242-b08-0ubuntu3~18.04-b08)
> OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode)
>
> - Apache Maven 3.6.0
> Maven home: /usr/share/maven
> Java version: 1.8.0_242, vendor: Private Build, runtime:
> /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.15.0-76-generic", arch: "amd64", family:
> "unix"
>
>
> - Git version 2.17.1
> - $ rvm requirements
> Checking requirements for ubuntu.
> Requirements installation successful.
>
> - Compass successfully installed
> - Ruby-2.6.3 installed.
> - home/useraccount/.nvm/versions/node/v6.5.0/lib
> ├── bower@1.8.8
> ├── grunt@1.0.4
> ├── grunt-cli@1.3.2
>
> Please note:
> The standard Mirage XMLUI theme works fine for me.
> I have been able as a DSpace Admin, to do such things as batch upload of
> files and execute search statistics.
>
>
> *MY DSPACE PROBLEM*
>
> I was able to successfully:
>
> - load the pre-requisites for Mirage2
> - edit [dspace-source]/dspace/config/xmlui.xconf  to uncomment the regular
> Mirage theme and add:
> 
>
> - make adjustments to the file
> [dspace-source]/dspace-6.3-release/dspace/modules/xmlui-mirage2//pom.xml
> where I changed the version of the dependencies to reflect what was
> actually loaded.
>
> However, when I eventually ran:
> $ mvn -Dmirage2.on=true -Dmirage2.deps.included=false clean package
>
> Even though the directory
>
> /build/dspace-6.3-release/dspace/modules/xmlui-mirage2/target/themes/
>
> ..does exist, I got the following error message and am temporarily stuck
> at this part of the Mirage2 installation:
>
> [INFO]
> 
> [INFO] Reactor Summary for DSpace Parent Project 6.3:
> [INFO]
> [INFO] DSpace Parent Project .. SUCCESS [
> 29.677 s]
> [INFO] DSpace Addon Modules ... SUCCESS [
> 0.019 s]
> [INFO] DSpace Kernel :: Additions and Local Customizations  SUCCESS [01:42
> min]
> [INFO] DSpace XML-UI Mirage2 Theme :: Local Customisations  FAILURE [
> 49.864 s]
> [INFO] DSpace XML-UI (Manakin) :: Local Customizations  SKIPPED
> [INFO] DSpace JSP-UI :: Local Customizations .. SKIPPED
> [INFO] DSpace RDF :: Local Customizations . SKIPPED
> [INFO] DSpace REST :: Local Customizations  SKIPPED
> [INFO] DSpace SWORD :: Local Customizations ... SKIPPED
> [INFO] DSpace SWORD v2 :: Local Customizations  SKIPPED
> [INFO] DSpace SOLR :: Local Customizations  SKIPPED
> [INFO] DSpace OAI-PMH :: Local Customizations . SKIPPED
> [INFO] DSpace Assembly and Configuration .. SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time:  03:02 min
> [INFO] Finished at: 2020-01-30T16:05:17-04:00
> [INFO]
> 

Re: [dspace-tech] MIGRATING DSPACE DATABASE FROM DSPACE 5.2 ON WINDOWS 7 TO DSPACE 6.3 ON UBUNTU SERVER 18.04

[Claudia Jürgen]

Hello,

take a look at the AIP Backup and Restore
https://wiki.lyrasis.org/display/DSDOC6x/AIP+Backup+and+Restore

Hope this helps

Claudia Jürgen


Am 04.02.2020 um 13:09 schrieb Gerald Okeke:

Greetings,

I seek assistance on how to migrate Dspace and database from Dspace 5.2
installed on WINDOWS 7 computer to fresh installation of Dspace 6.3
installed on Ubuntu Server 18.04. I have tried copying the Assetstore
folder from the windows 7 to the Ubuntu server. But that did not work. I
will appreciate help from anyone. Thank you!!

Best Regards,
Gerald



--
Claudia Juergen
Eldorado

Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund

Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
claudia.juer...@tu-dortmund.de
www.ub.tu-dortmund.de


Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist 
ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese 
E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und 
vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform 
(mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen 
Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is 
solely intended for the recipient. If you are not the intended recipient of 
this e-mail please contact the sender and delete this message. Thank you. 
Without prejudice of e-mail correspondence, our statements are only legally 
binding when they are made in the conventional written form (with personal 
signature) or when such documents are sent by fax.

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/2becbc83-3042-77d6-571d-6d4d21aa274a%40tu-dortmund.de.

[dspace-tech] MIGRATING DSPACE DATABASE FROM DSPACE 5.2 ON WINDOWS 7 TO DSPACE 6.3 ON UBUNTU SERVER 18.04

[Gerald Okeke]

Greetings,

I seek assistance on how to migrate Dspace and database from Dspace 5.2 
installed on WINDOWS 7 computer to fresh installation of Dspace 6.3 
installed on Ubuntu Server 18.04. I have tried copying the Assetstore 
folder from the windows 7 to the Ubuntu server. But that did not work. I 
will appreciate help from anyone. Thank you!!

Best Regards,
Gerald

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/22f6e38e-2b9d-4a5b-9b5b-e9bc8ae005b2%40googlegroups.com.

[dspace-tech] "Invalid UUID string" in Solr search core after DSpace 6 upgrade

[Alan Orth]

Dear list,

I'm testing DSpace version 5.8 to 6.3 upgrade. Immediately after performing
the database migrations successfully and starting Tomcat I initiated a
`dspace index-discovery -b`. I thought something was strange because I
didn't see any indexing progress in dspace.log (despite high CPU usage),
and then when I browsed the home page I saw many errors such as this in
dspace.log:

2020-02-03 10:27:14,485 ERROR org.dspace.browse.ItemCountDAOSolr @
caught exception:
org.dspace.discovery.SearchServiceException: Invalid UUID string: 1
2020-02-03 13:20:20,475 ERROR
org.dspace.app.xmlui.aspect.discovery.AbstractRecentSubmissionTransformer
@ Caught SearchServiceException while retrieving recent submission
for: home page
org.dspace.discovery.SearchServiceException: Invalid UUID string: 111210

I checked Solr's search core and saw that the search.resourceid fields were
indeed integers instead of UUIDs. On a guess I stopped the indexing,
deleted the search cores¹, touched an empty file in
dspace/solr/search/conf/reindex.flag², and restarted Tomcat. After Tomcat
started back up the re-indexing started and correctly indexed
search.resourceid as UUIDs.

After the initial reindex.flag indexing completes, subsequent manual
indexing runs with `dspace index-discovery -b` work correctly. This only
seems to happen the first time after upgrade—I tried deleting all search
documents and starting a `dspace index-discovery -b` and it behaved
correctly.

Has anyone seen this? Is it worth filing a bug? Are there perhaps some
fixes in the as-of-yet-unreleased 6.4 that would address this?

Regards,

¹ curl -s 'http://localhost:8080/solr/search/update?stream.body=
*:*=true'
² https://wiki.lyrasis.org/display/DSDOC6x/Upgrading+DSpace
-- 
Alan Orth
alan.o...@gmail.com
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 dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAKKdN4XRhtBOwsmpf02jxdjV%2Bj8vUEpSvZ9%3Du-737fSgZe0qCA%40mail.gmail.com.