[dspace-tech] Database connection error after change environment variable.

[danielKim]

Hi everyone.

I have changed some environment variable and forget already what I made 
changes.

Can anyone suggest why the error happens? The tomcat starts successfully 
but dspace can't startup.

Thanks for your support!



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

Re: [dspace-tech] Metadata filed doesn't change after modifying local.cfg

[danielKim]

Hello Claudia,
Thanks for your response.
I should try to use another version of DSpace and will post the result here.
(so make sure this version of dspace has issue)

Thanks for your response.
Regards 

2017년 7월 12일 수요일 오후 4시 49분 22초 UTC+8, Claudia Jürgen 님의 말:
>
> Hello Daniel, 
>
> as you mentioned below this seems to be a CRIS issue. 
> I tried it on a vanilla 6.x instance with jspui and it works just fine 
> in all variations (enumeration, each on a seperate line etc.). 
>
> Hope this helps 
>
> Claudia 
>
>
> Am 11.07.2017 um 11:08 schrieb danielKim: 
> > Thanks for reading this question. 
> > Our library repository uses custom metadata filed so I have added 
> following 
> > lines in the local.cfg configuration file. 
> > 
> > webui.itemdisplay.default = dc.title, dc.title.alternative, 
> > dc.contributor.*, \ 
> >  dc.subject(nobreakline), 
> dc.date.issued(date), 
> > dc.publisher, \ 
> >  dc.identifier.citation, 
> > dc.relation.ispartofseries, \ 
> >  dc.description.abstract, dc.description, \ 
> >  dc.identifier.govdoc, 
> dc.identifier.uri(link),\ 
> >  dc.identifier.isbn, dc.identifier.issn, \ 
> >  dc.identifier.ismn, dc.identifier, \ 
> > dc.subject.keywords, dc.rights.uri 
> > 
> > So far I know without this, the default metadata will be displayed in 
> the 
> > web interface. 
> > The problem is 'webui.itemdisplay.default' will only accept one 
> parameter 
> > and ignore parameters after on. 
> > For example, if I change first line of this configuration, 
> > 
> > webui.itemdisplay.default = dc.subject.keywords, dc.title.alternative, 
> > dc.contributor.*, \ 
> > 
> > The web interface will be look like this: 
> > 
> > <
> https://lh3.googleusercontent.com/-F7ZZ-BVt9no/WWSTVaS_Z2I/Gn4/35tq3i29yv8ka80X4D6EMnetPcIa2gY-gCLcBGAs/s1600/shit1.png>
>  
>
> > 
> > 
> > So if I change config like this: 
> > 
> > webui.itemdisplay.default = dc.title, dc.title.alternative, 
> > dc.contributor.*, \ 
> > *..* 
> > *Below are the same as above* 
> > 
> > 
> > web interface will show the title correctly. 
> > 
> > <
> https://lh3.googleusercontent.com/-xcYB10LHDPU/WWSTYNzkZ1I/Gn8/NcbTiIp7ICky7jlRSb4DnFANru_xlsJ_QCLcBGAs/s1600/shit2.png>
>  
>
> > 
> > 
> > So it seems webui.itemdisplay.default accepts only one parameter from 
> the 
> > config file but it should read whole configuration and change metadata 
> > display to users. 
> > 
> > 
> > This is my dspace version information. 
> > 
> > 
> > <
> https://lh3.googleusercontent.com/--t7o7A98W8M/WWSUvndE2cI/GoI/KQo83X3cUEUaL6T7HZsRphpKp79A_UvqgCLcBGAs/s1600/shit3.png>
>  
>
> > 
> > I have another dspace server which is running original 6.0 release. (So 
> > this server is made for using CRIS version of dspace) 
> > 
> > That old server correctly shows all metadata information as we change 
> > related configurations at local.cfg file. 
> > 
> > Do you think this is the bug of CRIS version ? or should I made some 
> > mistake which prevents to dspace can't recognize configurations 
> correctly? 
> > 
> > 
> > Thanks in advance! 
> > 
>
> -- 
> 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...@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. 
>

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

[dspace-tech] Metadata filed doesn't change after modifying local.cfg

[danielKim]

Thanks for reading this question.
Our library repository uses custom metadata filed so I have added following 
lines in the local.cfg configuration file.

webui.itemdisplay.default = dc.title, dc.title.alternative, 
dc.contributor.*, \
dc.subject(nobreakline), dc.date.issued(date), 
dc.publisher, \
dc.identifier.citation, 
dc.relation.ispartofseries, \
dc.description.abstract, dc.description, \
dc.identifier.govdoc, dc.identifier.uri(link),\
dc.identifier.isbn, dc.identifier.issn, \
dc.identifier.ismn, dc.identifier, \
dc.subject.keywords, dc.rights.uri

So far I know without this, the default metadata will be displayed in the 
web interface.
The problem is 'webui.itemdisplay.default' will only accept one parameter 
and ignore parameters after on.
For example, if I change first line of this configuration,

webui.itemdisplay.default = dc.subject.keywords, dc.title.alternative, 
dc.contributor.*, \

The web interface will be look like this:




So if I change config like this:

webui.itemdisplay.default = dc.title, dc.title.alternative, 
dc.contributor.*, \
*..*
*Below are the same as above*


web interface will show the title correctly.




So it seems webui.itemdisplay.default accepts only one parameter from the 
config file but it should read whole configuration and change metadata 
display to users.


This is my dspace version information. 




I have another dspace server which is running original 6.0 release. (So 
this server is made for using CRIS version of dspace)

That old server correctly shows all metadata information as we change 
related configurations at local.cfg file.

Do you think this is the bug of CRIS version ? or should I made some 
mistake which prevents to dspace can't recognize configurations correctly?


Thanks in advance! 

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

Re: [dspace-tech] Failed to execute "dspace database migrated" because of duplicated rows in group2group table.

[danielKim]

Hi!
So your query just remove duplicated rows no matter ID attribute (what I 
was thinking)
The problem was solved. thanks a lot

2017년 7월 6일 목요일 오후 4시 20분 41초 UTC+8, Tom Desair (Atmire) 님의 말:
>
> Hi,
>
> Please try this:
>
>1. Take a backup of your database
>2. Before starting the Flyway migration (bin/dspace database migrate) 
>execute these two SQL statements on your database:
>   - delete from group2group where id in (select id from group2group 
>   g1 where exists (select 1 from group2group g2 where g2.parent_id = 
>   g1.parent_id and g2.child_id = g1.child_id and g2.id < g1.id));
>   - delete from epersongroup2eperson where id in (select id from 
>   epersongroup2eperson g1 where exists (select 1 from 
> epersongroup2eperson g2 
>   where g2.eperson_group_id = g1.eperson_group_id and g2.eperson_id = 
>   g1.eperson_id and g2.id < g1.id));
>   3. Run the Flyway migration and start Tomcat
>
> Best regards,
> Tom
>
>  
> [image: logo] Tom Desair
> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
> Gaston Geenslaan 14, Leuven 3001, Belgium
> www.atmire.com 
> <http://atmire.com/website/?q=services_source=emailfooter_medium=email_campaign=tomdesair>
>
> 2017-07-05 9:56 GMT+02:00 danielKim <hango...@gmail.com >:
>
>> Thanks for watching this question.
>> I am migrating old server which is running dspace 6.0 to new server which 
>> is running CRIS dspace 6.0
>> So far I have done "mvn package" and "ant fresh_install" successfully.
>> After that, I backup database from the old server use pg_dump and restore 
>> it in a new server using psql -f backupfile command.
>>
>> And then, I started the tomcat9 service and it is failed to start service 
>> I guess this is database problem.
>> I stopped tomcat9 service and try to run command "[dspace]/bin/dspace 
>> database info" and I got the following result.
>>
>>
>> ++-+-+-+
>> | Version| Description | 
>> Installed on| State   |
>>
>> ++-+-+-+
>> | 1.1| Initial DSpace 1.1 database schema  | 
>> | > | 1.2| Upgrade to DSpace 1.2 schema| 
>> | > | 1.3| Upgrade to DSpace 1.3 schema| 
>> | > | 1.3.9  | Drop constraint for DSpace 1 4 schema   | 
>> | > | 1.4| Upgrade to DSpace 1.4 schema| 
>> | > | 1.5| Upgrade to DSpace 1.5 schema| 
>> | > | 1.5.9  | Drop constraint for DSpace 1 6 schema   | 
>> | > | 1.6| Initializing from DSpace 1.6 database schema| 
>> 2017-07-05 15:39:55 | Success |
>> | 1.7| Upgrade to DSpace 1.7 schema| 
>> 2017-07-05 15:39:55 | Success |
>> | 1.8| Upgrade to DSpace 1.8 schema| 
>> 2017-07-05 15:39:55 | Success |
>> | 1.8.2.0| DSpaceCRIS-crismodule database schema   | 
>> 2017-07-05 15:39:56 | Success |
>> | 1.8.2.1| DSpaceCRIS-crispubmed database schema   | 
>> 2017-07-05 15:39:58 | Success |
>> | 1.8.2.2| DSpaceCRIS-subscription database schema | 
>> 2017-07-05 15:39:58 | Success |
>> | 3.0| Upgrade to DSpace 3.x schema| 
>> 2017-07-05 15:39:58 | Success |
>> | 3.2.1.0| DSpaceCRIS-Upgrade-crismodule 182 to 321| 
>> 2017-07-05 15:39:58 | Success |
>> | 4.0| Upgrade to DSpace 4.x schema| 
>> 2017-07-05 15:39:58 | Success |
>> | 4.1.0.0| DSpaceCRIS-Upgrade-crismodule 321 to 4  | 
>> 2017-07-05 15:39:59 | Success |
>> | 4.3.0.0| DSpaceCRIS-Upgrade-crismodule 4 to 43   | 
>> 2017-07-05 15:39:59 | Success |
>> | 4.9.2015.10.26 | DS-2818 registry update | 
>> 2017-07-05 15:39:59 | Success |
>> | 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy | 
>> 2017-07-05 15:39:59 | Success |
>> | 5.0.2014.09.25 | DS 1582 Metadata For All Objects drop constraint| 
>> 2017-07-05 15:39:59 | Success |
>> | 

[dspace-tech] Failed to execute "dspace database migrated" because of duplicated rows in group2group table.

[danielKim]

Thanks for watching this question.
I am migrating old server which is running dspace 6.0 to new server which 
is running CRIS dspace 6.0
So far I have done "mvn package" and "ant fresh_install" successfully.
After that, I backup database from the old server use pg_dump and restore 
it in a new server using psql -f backupfile command.

And then, I started the tomcat9 service and it is failed to start service I 
guess this is database problem.
I stopped tomcat9 service and try to run command "[dspace]/bin/dspace 
database info" and I got the following result.

++-+-+-+
| Version| Description | 
Installed on| State   |
++-+-+-+
| 1.1| Initial DSpace 1.1 database schema  |   
  |  ./dspace database migrate
Using DSpace installation in: C:\dspace
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option 
MaxPermSize=2048m; support was removed in 8.0

Database URL: jdbc:postgresql://localhost:5432/dspace
Migrating database to latest version... (Check dspace logs for details)
Migration exception:
java.sql.SQLException: Flyway migration error occurred
at 
org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:669)
at 
org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:577)
at 
org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:224)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at 
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:230)
at 
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:82)
Caused by: org.flywaydb.core.internal.dbsupport.FlywaySqlScriptException:
Migration V6.0_2015.03.07__DS-2701_Hibernate_migration.sql failed
-
SQL State  : 23505
Error Code : 0
Message: ERROR: could not create unique index "group2group_pkey"
  Detail: Key (parent_id, child_id)=(a393424d-eb09-4a5c-bb6d-f226f0a27637, 
70e3dd59-cbc2-4c21-94a6-b11928b2bac7) is duplicated.
Location   : 
org/dspace/storage/rdbms/sqlmigration/postgres/V6.0_2015.03.07__DS-2701_Hibernate_migration.sql
 
(C:\dspace\file:\C:\dspace\lib\dspace-api-CRIS-6.0.0-SNAPSHOT.jar!\org\dspace\storage\rdbms\sqlmigration\postgres\V6.0_2015.03.07__DS-2701_Hibernate_migration.sql)
Line   : 130
Statement  : ALTER TABLE Group2Group add primary key (parent_id,child_id)

at 
org.flywaydb.core.internal.dbsupport.SqlScript.execute(SqlScript.java:117)
at 
org.flywaydb.core.internal.resolver.sql.SqlMigrationExecutor.execute(SqlMigrationExecutor.java:71)
at 
org.flywaydb.core.internal.command.DbMigrate.doMigrate(DbMigrate.java:352)
at 
org.flywaydb.core.internal.command.DbMigrate.access$1100(DbMigrate.java:47)
at 
org.flywaydb.core.internal.command.DbMigrate$4.doInTransaction(DbMigrate.java:308)
at 
org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:72)
at 
org.flywaydb.core.internal.command.DbMigrate.applyMigration(DbMigrate.java:305)
at 
org.flywaydb.core.internal.command.DbMigrate.access$1000(DbMigrate.java:47)
at 
org.flywaydb.core.internal.command.DbMigrate$2.doInTransaction(DbMigrate.java:230)
at 
org.flywaydb.core.internal.command.DbMigrate$2.doInTransaction(DbMigrate.java:173)
at 
org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:72)
at 
org.flywaydb.core.internal.command.DbMigrate.migrate(DbMigrate.java:173)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:959)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:917)
at org.flywaydb.core.Flyway.execute(Flyway.java:1373)
at org.flywaydb.core.Flyway.migrate(Flyway.java:917)
at 
org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:658)
... 8 more
Caused by: org.postgresql.util.PSQLException: ERROR: could not create 
unique index "group2group_pkey"
  Detail: Key (parent_id, child_id)=(a393424d-eb09-4a5c-bb6d-f226f0a27637, 
70e3dd59-cbc2-4c21-94a6-b11928b2bac7) is duplicated.
at 
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2458)
at 
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2158)
at 
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:291)
at 
org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:432)
at 

Re: [dspace-tech] Re: The 6 RC version of DSpace-CRIS is now available

[danielKim]

Thanks! My installation was successfully completed.
Thanks for you assistance and kindness.
Regards
Daniel

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

[dspace-tech] Re: The 6 RC version of DSpace-CRIS is now available

[danielKim]

>
> Dear Bollini,
>

I get an error message when I do "and fresh_install" at database checking 
part.

test_database:
 [java] Failure during kernel init: Infinite loop in property 
interpolation   

   of ${cris.ametrics.elsevier.scopus.enabled}: 
cris.ametrics.elsevier.scopus.enabl 

ed
 [java] java.lang.IllegalStateException: Infinite loop in property 
interpola   

  tion of ${cris.ametrics.elsevier.scopus.enabled}: 
cris.ametrics.elsevier.scopus. 

enabled
 [java] at 
org.apache.commons.lang.text.StrSubstitutor.checkCyclicSubsti   

  
tution(StrSubstitutor.java:701)
 [java] at 
org.apache.commons.lang.text.StrSubstitutor.substitute(StrSub   

  
stitutor.java:645)
 [java] at 
org.apache.commons.lang.text.StrSubstitutor.substitute(StrSub   

  
stitutor.java:656)
 [java] at 
org.apache.commons.lang.text.StrSubstitutor.substitute(StrSub   

  
stitutor.java:563)
 [java] at 
org.apache.commons.lang.text.StrSubstitutor.replace(StrSubsti   

  
tutor.java:305)
 [java] at 
org.apache.commons.configuration.PropertyConverter.interpolat   

  
e(PropertyConverter.java:1040)
 [java] at 
org.apache.commons.configuration.AbstractConfiguration.interp   

  
olate(AbstractConfiguration.java:449)
 [java] at 
org.apache.commons.configuration.AbstractConfiguration.interp   

  
olate(AbstractConfiguration.java:436)
 [java] at 
org.apache.commons.configuration.AbstractConfiguration.getLis   

  
t(AbstractConfiguration.java:1128)
 [java] at 
org.apache.commons.configuration.AbstractConfiguration.getLis   

  
t(AbstractConfiguration.java:1117)
 [java] at 
org.apache.commons.configuration.ConfigurationConverter.getPr   

  
operties(ConfigurationConverter.java:113)
 [java] at 
org.dspace.servicemanager.config.DSpaceConfigurationService.g   

  
etProperties(DSpaceConfigurationService.java:98)
 [java] at 
org.dspace.servicemanager.config.DSpaceConfigurationService.t   

  
oString(DSpaceConfigurationService.java:553)
 [java] at 
org.dspace.servicemanager.config.DSpaceConfigurationService.l   

  
oadInitialConfig(DSpaceConfigurationService.java:506)
 [java] at