[dspace-tech] Re: Εrror Related to SHERPA beans initialization

[Pantelis Karamolegkos]

Hi Mark, thanks for pointing to me the -Dlocal-config option!

That saved the day!

Yes it turns out you CAN relocate local.cfg, we just did.

The whole issue started from our CI tool that deleted previous files when 
performing a git pull (even untracked ones, such as local.cfg so we had to 
figure a way to use a remote file)

Regards,

P.K.

On Wednesday, October 26, 2016 at 4:19:54 PM UTC+3, Pantelis Karamolegkos 
wrote:
>
> When performing an ant update after an mvn clean install, the following 
> error appears during execution of the test_database target
>
> [java] Caused by: org.springframework.beans.factory.BeanCreationException: 
> Error creating bean with name 
> 'org.dspace.app.sherpa.submit.SHERPASubmitConfigurationService' defined in 
> URL 
> [jar:file:/home/gitlab-runner/builds/a8dc15bb/0/photodentro/ebooks-v2/dspace/target/dspace-installer/lib/dspace-api-6.0-rc5-SNAPSHOT.jar!/spring/spring-dspace-addon-sherpa-configuration-services.xml]:
>  
> Cannot create inner bean 
> 'org.dspace.app.sherpa.submit.MetadataValueISSNExtractor#3c69362a' of type 
> [org.dspace.app.sherpa.submit.MetadataValueISSNExtractor] while setting 
> bean property 'issnItemExtractors' with key [0]; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating 
> bean with name 
> 'org.dspace.app.sherpa.submit.MetadataValueISSNExtractor#3c69362a': 
> Injection of autowired dependencies failed; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Could not autowire 
> field: public org.dspace.content.service.ItemService 
> org.dspace.app.sherpa.submit.MetadataValueISSNExtractor.itemService; nested 
> exception is 
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No 
> qualifying bean of type [org.dspace.content.service.ItemService] found for 
> dependency: expected at least 1 bean which qualifies as autowire candidate 
> for this dependency. Dependency annotations: 
> {@org.springframework.beans.factory.annotation.Autowired(required=true)}
>
>
> Any suggestions what might be causing this?
>
> Thanks,
>
> P.K.
>

-- 
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: Εrror Related to SHERPA beans initialization

[Pantelis Karamolegkos]

By trial and error I found out that the error was gone when running the ant 
command with a local cgf file.

I was previously running the ant update command with a remote dir cfg file, 
i.e.

ant -Dconfig=/anotherdir/config/local.cfg

why is that?

do I have to specify this in the mvn commands also?

Thanks,

P.K.

why is that?

On Wednesday, October 26, 2016 at 4:19:54 PM UTC+3, Pantelis Karamolegkos 
wrote:
>
> When performing an ant update after an mvn clean install, the following 
> error appears during execution of the test_database target
>
> [java] Caused by: org.springframework.beans.factory.BeanCreationException: 
> Error creating bean with name 
> 'org.dspace.app.sherpa.submit.SHERPASubmitConfigurationService' defined in 
> URL 
> [jar:file:/home/gitlab-runner/builds/a8dc15bb/0/photodentro/ebooks-v2/dspace/target/dspace-installer/lib/dspace-api-6.0-rc5-SNAPSHOT.jar!/spring/spring-dspace-addon-sherpa-configuration-services.xml]:
>  
> Cannot create inner bean 
> 'org.dspace.app.sherpa.submit.MetadataValueISSNExtractor#3c69362a' of type 
> [org.dspace.app.sherpa.submit.MetadataValueISSNExtractor] while setting 
> bean property 'issnItemExtractors' with key [0]; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating 
> bean with name 
> 'org.dspace.app.sherpa.submit.MetadataValueISSNExtractor#3c69362a': 
> Injection of autowired dependencies failed; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Could not autowire 
> field: public org.dspace.content.service.ItemService 
> org.dspace.app.sherpa.submit.MetadataValueISSNExtractor.itemService; nested 
> exception is 
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No 
> qualifying bean of type [org.dspace.content.service.ItemService] found for 
> dependency: expected at least 1 bean which qualifies as autowire candidate 
> for this dependency. Dependency annotations: 
> {@org.springframework.beans.factory.annotation.Autowired(required=true)}
>
>
> Any suggestions what might be causing this?
>
> Thanks,
>
> P.K.
>

-- 
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: Εrror Related to SHERPA beans initialization

[Pantelis Karamolegkos]

The same error seems to prevent a proper tomcat8 restart.

On Wednesday, October 26, 2016 at 4:19:54 PM UTC+3, Pantelis Karamolegkos 
wrote:
>
> When performing an ant update after an mvn clean install, the following 
> error appears during execution of the test_database target
>
> [java] Caused by: org.springframework.beans.factory.BeanCreationException: 
> Error creating bean with name 
> 'org.dspace.app.sherpa.submit.SHERPASubmitConfigurationService' defined in 
> URL 
> [jar:file:/home/gitlab-runner/builds/a8dc15bb/0/photodentro/ebooks-v2/dspace/target/dspace-installer/lib/dspace-api-6.0-rc5-SNAPSHOT.jar!/spring/spring-dspace-addon-sherpa-configuration-services.xml]:
>  
> Cannot create inner bean 
> 'org.dspace.app.sherpa.submit.MetadataValueISSNExtractor#3c69362a' of type 
> [org.dspace.app.sherpa.submit.MetadataValueISSNExtractor] while setting 
> bean property 'issnItemExtractors' with key [0]; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating 
> bean with name 
> 'org.dspace.app.sherpa.submit.MetadataValueISSNExtractor#3c69362a': 
> Injection of autowired dependencies failed; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Could not autowire 
> field: public org.dspace.content.service.ItemService 
> org.dspace.app.sherpa.submit.MetadataValueISSNExtractor.itemService; nested 
> exception is 
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No 
> qualifying bean of type [org.dspace.content.service.ItemService] found for 
> dependency: expected at least 1 bean which qualifies as autowire candidate 
> for this dependency. Dependency annotations: 
> {@org.springframework.beans.factory.annotation.Autowired(required=true)}
>
>
> Any suggestions what might be causing this?
>
> Thanks,
>
> P.K.
>

-- 
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] Εrror Related to SHERPA beans initialization

[Pantelis Karamolegkos]

When performing an ant update after an mvn clean install, the following 
error appears during execution of the test_database target

[java] Caused by: org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 
'org.dspace.app.sherpa.submit.SHERPASubmitConfigurationService' defined in 
URL 
[jar:file:/home/gitlab-runner/builds/a8dc15bb/0/photodentro/ebooks-v2/dspace/target/dspace-installer/lib/dspace-api-6.0-rc5-SNAPSHOT.jar!/spring/spring-dspace-addon-sherpa-configuration-services.xml]:
 
Cannot create inner bean 
'org.dspace.app.sherpa.submit.MetadataValueISSNExtractor#3c69362a' of type 
[org.dspace.app.sherpa.submit.MetadataValueISSNExtractor] while setting 
bean property 'issnItemExtractors' with key [0]; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating 
bean with name 
'org.dspace.app.sherpa.submit.MetadataValueISSNExtractor#3c69362a': 
Injection of autowired dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Could not autowire 
field: public org.dspace.content.service.ItemService 
org.dspace.app.sherpa.submit.MetadataValueISSNExtractor.itemService; nested 
exception is 
org.springframework.beans.factory.NoSuchBeanDefinitionException: No 
qualifying bean of type [org.dspace.content.service.ItemService] found for 
dependency: expected at least 1 bean which qualifies as autowire candidate 
for this dependency. Dependency annotations: 
{@org.springframework.beans.factory.annotation.Autowired(required=true)}


Any suggestions what might be causing this?

Thanks,

P.K.

-- 
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: Additional Metadata Schema in DSpace

[Pantelis Karamolegkos]

Thanks Claudia.
In any case we are not considering about removing any of the existing 
schemas, just adding a (couple of) new one(s).

Best,

Pantelis

On Wednesday, October 19, 2016 at 3:23:10 PM UTC+3, Pantelis Karamolegkos 
wrote:
>
> In order to declare and use a new metadata schema, what is the recommended 
> way of going about it?
> Should we directly add entries to the database or update / add xml files 
> under the dspace/config/registries folder?
>
> For example, in order to add say the LOM schema, should we add a 
> lom-types.xml file with the LOM application profile we intend to use?
> (as its already done for dc and dcterm schemas with dublin-core-types.xml 
> and dcterms-types.xml respectively?)
>

-- 
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: DB Migration when adding new metadata field

[Pantelis Karamolegkos]

If a previously added field needs to be removed, what is the recommended 
way to remove it from the database?
(I assume either way it has to be removed from input-forms.xml)

On Friday, July 8, 2016 at 5:07:17 PM UTC+3, Pantelis Karamolegkos wrote:
>
> When adding a new metadata field through the respective admin form (in an 
> existing schema. e.g. dc), do we also have to manually add the respective 
> flyway migration script under org.dspace.storage.sqlmigration. ?
> Otherwise how will the new field be added to the database of someone who 
> checks out our code from the branch we are working on?
>

-- 
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: DB Migration when adding new metadata field

[Pantelis Karamolegkos]

<https://lh3.googleusercontent.com/-0A8hT-AF-6I/V3_NEAjXqRI/AUQ/oJzxN1DXLH8KW5XDEF-rAjeQe7d9I1jJgCLcB/s1600/newfield.jpg>
Ηi Claudia,

so, if I undestand correctly, adding a new metadata field to an existing 
schema (say dc for example) is a 3 step process?

1. Addition of the field in the following admin form

<https://lh3.googleusercontent.com/-0A8hT-AF-6I/V3_NEAjXqRI/AUQ/oJzxN1DXLH8KW5XDEF-rAjeQe7d9I1jJgCLcB/s1600/newfield.jpg>

2. Addition in the input-forms.xml

3. Addition in the registries, i.e. in our case dublin-core-types.xml?

Is that correct?

(In my case I carried out the first 2 steps, and the field was indeed 
added...I just wanted to know how the db migration will take place so 
someone who checks out my code has the new field in his db instance)

Thanks,

P.K.

On Friday, July 8, 2016 at 5:07:17 PM UTC+3, Pantelis Karamolegkos wrote:
>
> When adding a new metadata field through the respective admin form (in an 
> existing schema. e.g. dc), do we also have to manually add the respective 
> flyway migration script under org.dspace.storage.sqlmigration. ?
> Otherwise how will the new field be added to the database of someone who 
> checks out our code from the branch we are working on?
>

-- 
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] DB Migration when adding new metadata field

[Pantelis Karamolegkos]

When adding a new metadata field through the respective admin form (in an 
existing schema. e.g. dc), do we also have to manually add the respective 
flyway migration script under org.dspace.storage.sqlmigration. ?
Otherwise how will the new field be added to the database of someone who 
checks out our code from the branch we are working on?

-- 
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] Re: Recommended Testing Strategy

[Pantelis Karamolegkos]

Hi Tim, many thanks for your very comprehensive reply.

I am assuming that changing directory to [dspace-src]/dspace within the 
second command, before running mvn package is to ensure that the build 
process for the overlay modules (where customization / extensions are 
supposed to take place) work? (this should be the process you call quick 
build If I understand correctly)

P.K.

P.S: Is there somewhere a brief explanation (or tutorial) about what the so 
called 'assembly' process (which I assume has its own maven profile) is?

On Thursday, June 30, 2016 at 8:18:12 PM UTC+3, Tim Donohue wrote:
>
> Hi P.K.
>
> Those two Travis CI steps are doing two different things (based on the 
> flags passed to those Maven commands). The comments in the .travis.yml are 
> meant to describe the two commands:
>
> https://github.com/DSpace/DSpace/blob/master/.travis.yml 
> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2FDSpace%2FDSpace%2Fblob%2Fmaster%2F.travis.yml=D=1=AFQjCNHpmSuuhygbsANn3QwlXh94AbeqHA>
>
> 1) The first command (mvn clean install) is the ONLY one that runs Unit 
> Tests & Integration Tests. It's role is to run all the tests for all API 
> classes, and install the resulting JARs in the .m2 (Maven cache) on the 
> Travis CI server. This command runs from the [src] directory, and 
> builds/tests *all* core modules.
>
> 2) The second command (mvn package) takes those installed JARs, and then 
> runs a test build of Mirage 2 (for XMLUI) and other modules *from* the 
> [src]/dspace/ directory (ensuring the "quick build" works).
> So, the first command is the one that is often more likely to fail, as it 
> is where we run our tests.  But, the second command is there to also ensure 
> the quick build and Mirage 2 build process is still working properly.
>
> The reason we split these up is that Travis CI has very strict policies on 
> memory usage for free accounts (we have a free acct).  They could be run as 
> a single step. But, in the past, doing so often caused us to hit the Travis 
> CI memory usage limit (at which point Travis *kills* your tests, and they 
> all result in failures).  Splitting them up helps us remain under that 
> limit.
>
> - Tim
>
> On 6/30/2016 5:49 AM, Pantelis Karamolegkos wrote:
>
> In the .travis.yml file, why is a  
>
> mvn clean install (line 42 of the latest commit on master)
>
> followed by an 
>
> mvn package (line 47)
>
> given that the mvn install will ALSO package the project(s)?
>
> (i.e. install seems to be a superset of package in maven terms)
>
> On Monday, June 6, 2016 at 6:56:35 PM UTC+3, Pantelis Karamolegkos wrote: 
>>
>> Assuming someone wants to fork and proceed with heavy DSpace 
>> customization, what is the recommended testing strategy?
>> i.e. which of the tests should be kept in a CI environment like travis? 
>> (apart from our own custom tests we may set up)
>> (note: 99% of the customization will most likely take place on jspui)
>> Is there any documentation on dspace's (Unit/Integration) tests?
>>
>> Thx,
>>
>> P.K.
>>
> -- 
> 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
>
>

-- 
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] Spring error (related to database) [current master branch]

[Pantelis Karamolegkos]

After successful build, when changing directory to 
[dspace-src]/dspace/target/dspace-installer and executing ant 
test_database, I get the following error which I am unable to understand.

https://gist.github.com/anonymous/3e5b5a52b32ea1698dc6d39015a93294

Any suggestions?

Many thanks,

P.K.

-- 
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: Recommended Testing Strategy

[Pantelis Karamolegkos]

In the .travis.yml file, why is a 

mvn clean install (line 42 of the latest commit on master)

followed by an 

mvn package (line 47)

given that the mvn install will ALSO package the project(s)?

(i.e. install seems to be a superset of package in maven terms)

On Monday, June 6, 2016 at 6:56:35 PM UTC+3, Pantelis Karamolegkos wrote:
>
> Assuming someone wants to fork and proceed with heavy DSpace 
> customization, what is the recommended testing strategy?
> i.e. which of the tests should be kept in a CI environment like travis? 
> (apart from our own custom tests we may set up)
> (note: 99% of the customization will most likely take place on jspui)
> Is there any documentation on dspace's (Unit/Integration) tests?
>
> Thx,
>
> P.K.
>

-- 
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: Error when uploading file during item submission

[Pantelis Karamolegkos]

Perhaps it's a coincidence but the problem was solved (uploads now work) 
after making the following change to the postgresql driver dependency in 
root pom


org.postgresql
postgresql
9.4.1208.jre7



(i.e. now using the latest version)


On Tuesday, June 14, 2016 at 2:51:23 PM UTC+3, Pantelis Karamolegkos wrote:
>
> When trying to upload a file (i.e. in the 'Upload' step) I get the 
> following error:
>
> https://gist.github.com/pkaramol/ba72dc37541114b31d13397057153498
>
> any suggestions?
>

-- 
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: Error when uploading file during item submission

[Pantelis Karamolegkos]

I forgot to mention that I am using the latest build as it comes out of the 
master branch.
(working on Ubuntu 14.04 with Tomcat 8.0.23 and Postgresql 9.5)

On Tuesday, June 14, 2016 at 2:51:23 PM UTC+3, Pantelis Karamolegkos wrote:
>
> When trying to upload a file (i.e. in the 'Upload' step) I get the 
> following error:
>
> https://gist.github.com/pkaramol/ba72dc37541114b31d13397057153498
>
> any suggestions?
>

-- 
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] Error when uploading file during item submission

[Pantelis Karamolegkos]

When trying to upload a file (i.e. in the 'Upload' step) I get the 
following error:

https://gist.github.com/pkaramol/ba72dc37541114b31d13397057153498

any suggestions?

-- 
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] Recommended Testing Strategy

[Pantelis Karamolegkos]

Assuming someone wants to fork and proceed with heavy DSpace customization, 
what is the recommended testing strategy?
i.e. which of the tests should be kept in a CI environment like travis? 
(apart from our own custom tests we may set up)
(note: 99% of the customization will most likely take place on jspui)
Is there any documentation on dspace's (Unit/Integration) tests?

Thx,

P.K.

-- 
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] Are DSpace Rebuild instructions valid for versions > 3

[Pantelis Karamolegkos]

Came across this link: 
https://wiki.duraspace.org/display/DSDOC3x/Rebuild+DSpace
There seem to be specific instructions for versions =< 3.
What is the case for versions 4, 5 and 6?
Does the above link (for v3) apply to them as well?

-- 
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] Exceptions when creating a top-level community (dspace built from master branch)

[Pantelis Karamolegkos]

DSpace6 based on checkout from the master branch, on Ubuntu 16.04, using 
Tomcat8 and Java8.

On a fresh install, after creating admin account, the following exception 
appears on the dspace.log when hitting the 'Upload a logo ' button while 
trying to add a 'top level community)


Admin Home Page --> Browse / Communities & Collections --> Create Top-Level 
Community --> Upload

2016-05-25 16:18:31,876 WARN  org.dspace.app.util.Util @ Unable to 
recoginze UUID from String "null". Will return null.
java.lang.IllegalArgumentException: Invalid UUID string: null
at java.util.UUID.fromString(UUID.java:194)
at org.dspace.app.util.Util.getUUIDParameter(Util.java:262)
at 
org.dspace.app.webui.servlet.admin.EditCommunitiesServlet.doDSPost(EditCommunitiesServlet.java:156)


(here is the entire stack trace )

The upload logo page comes up however and after selecting a file and 
clicking 'Upload', the following exception comes up:

2016-05-25 16:27:12,063 ERROR org.dspace.storage.bitstore.DSBitStoreService 
@ put(16994001143855103125446320897951791631, inputstream)
java.io.IOException: No such file or directory
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(File.java:1012)
at 
org.dspace.storage.bitstore.DSBitStoreService.put(DSBitStoreService.java:125)
at 
org.dspace.storage.bitstore.BitstreamStorageServiceImpl.store(BitstreamStorageServiceImpl.java:107)
at 
org.dspace.content.BitstreamServiceImpl.create(BitstreamServiceImpl.java:101)
at 
org.dspace.content.CommunityServiceImpl.setLogo(CommunityServiceImpl.java:220)
at 
org.dspace.app.webui.servlet.admin.EditCommunitiesServlet.processUploadLogo(EditCommunitiesServlet.java:966)


(full stack trace )


-- 
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: Solr url access returning 403 error

[Pantelis Karamolegkos]

*Resolved*

Given the fact that the the following config parames were passed in 
local.cfg

dspace.baseUrl = http://my.pc.ip.add:8080

solr.server = http://my.pc.ip.add:8080/solr

where my.pc.ip.add are of course digits corresponding to my workstation's 
(static) IP addr, I had to also allow it explicitly in the value of the 
allow parameter of the Valve element which now looks sth like this

 

On Tuesday, May 24, 2016 at 6:01:29 PM UTC+3, Pantelis Karamolegkos wrote:
>
> I just installed dspace from the master branch source.
> I am however getting an "Internal System Error" on the landing page (as 
> you can see in the attached image)
>
> dspace log indicates a solr issue: http://pastebin.com/CP93Mwj0
>
> tl;dr: solr is not accessible via http (returning 403). Here is my 
> server.xml extract regarding dspace sonfiguration:
>
>   docBase="/home/pkaramol/Workspace/dspace/dspace-installation/webapps/jspui" 
> reloadable="true" />
>  docBase="/home/pkaramol/Workspace/dspace/dspace-installation/webapps/solr" 
> reloadable="true">
>  className="org.apache.catalina.valves.RemoteAddrValve" 
> allow="127\.0\.0\.1|123\.123\.123\.123|111\.222\.233\.d+"/>
>  value="false" override="false" />
> 
>
>
> Any suggestions would be appreciated, thx.
>
> Pantelis
>
>

-- 
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: No parameter substitution in ant when creating log.dir - DSpace 6 RC1

[Pantelis Karamolegkos]

Although the problem was manually corrected after creating the log dir and 
setting the respective value in log4j.properties, I am still getting the 
following error related to solr logs:

log4j:ERROR setFile(null,true) call failed.

*java.io.FileNotFoundException: /log/solr.log (No such file or directory)*
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(FileOutputStream.java:270)
at java.io.FileOutputStream.(FileOutputStream.java:213)
at java.io.FileOutputStream.(FileOutputStream.java:133)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
at 
org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:223)
at 
org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
at 
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172)
at 
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104)
at 
org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842)
at 
org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)
at 
org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:648)
at 
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:514)
at 
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580)
at 
org.apache.log4j.PropertyConfigurator.configure(PropertyConfigurator.java:415)
at 
org.dspace.solr.filters.ConfigureLog4jListener.contextInitialized(ConfigureLog4jListener.java:79)
at 
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4812)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5255)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
at 
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
at 
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
log4j:ERROR Either File or DatePattern options are not set for appender 
[file].

It seems that a relevant substitution needs to be made to configure solr 
logs (?)

Any idea where the solr logs location is set? Can't seem to find it.

Thx,

Pantelis

On Sunday, May 22, 2016 at 6:53:59 PM UTC+3, Pantelis Karamolegkos wrote:
>
> After running fresh_install, a file literally named ${log.dir} is created 
> in dspace_installer folder.
> It seems no parameter substitution takes place when running the ant target.
> Where are the folder names taken from, i.e. ${upload.temp.dir}, 
> ${report.dir} etc and why the log dir is not substituted while the others 
> are?
>

-- 
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: DSpace 6 RC1 - migrate_database ant target fails

[Pantelis Karamolegkos]

Resolved it was an issue of failed installation of pgcrypto.

On Sunday, May 22, 2016 at 6:59:05 PM UTC+3, Pantelis Karamolegkos wrote:
>
> The above target fails with the following output:
>
>  [java] 2016-05-22 18:56:33,108 INFO 
>  org.dspace.services.caching.CachingServiceImpl @ destroy()
>  [java] 2016-05-22 18:56:33,109 INFO 
>  org.springframework.cache.ehcache.EhCacheManagerFactoryBean @ Shutting 
> down EhCache CacheManager
>  [java] 2016-05-22 18:56:33,109 INFO 
>  org.dspace.services.sessions.SessionRequestServiceImpl @ shutdown
>  [java] 2016-05-22 18:56:33,109 WARN 
>  org.dspace.services.sessions.SessionRequestServiceImpl @ Request 
> interceptor 
> (org.dspace.services.events.SystemEventService$EventRequestInterceptor@7d35e191)
>  
> failed to execute on end (request-387-1463932592942): null
>  [java] 2016-05-22 18:56:33,113 INFO 
>  org.dspace.servicemanager.spring.SpringServiceManager @ Spring Service 
> Manager Shutdown...
>  [java] 2016-05-22 18:56:33,113 INFO 
>  org.dspace.servicemanager.DSpaceServiceManager @ Shutdown DSpace core 
> service manager
>  [java] 2016-05-22 18:56:33,113 INFO 
>  org.dspace.servicemanager.DSpaceKernelImpl @ DSpace kernel shutdown 
> completed and unregistered MBean: 
> org.dspace:name=2a65a6db-e965-4813-9766-fce8b7cb4f05,type=DSpaceKernel
>
> BUILD FAILED
> /home/pkaramol/Workspace/dspace_dir/dspace-6.0-rc1-src-release/dspace/target/dspace-installer/build.xml:799:
>  
> Java returned: 1
>
> Working on Ubuntu 16.04, with Postgres 9.5 and Java 1.8.0_91
>
>

-- 
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: No parameter substitution in ant when creating log.dir - DSpace 6 RC1

[Pantelis Karamolegkos]

Still it seems it is unable to grasp the value of log.dir parameter and 
substitute in log4j.properties.
My way around this was to hardcode the value of log.dir in log4j.properties 
in which I now have an entry like:

log.dir=/home/pkaramol/Workspace/dspace6/dspace-6.0-rc1-install-dir/log

And I also had to manually create the log dir in the above path and also 
grant rwx permissions to tomcat8 user (via setfacl)

On Sunday, May 22, 2016 at 6:53:59 PM UTC+3, Pantelis Karamolegkos wrote:
>
> After running fresh_install, a file literally named ${log.dir} is created 
> in dspace_installer folder.
> It seems no parameter substitution takes place when running the ant target.
> Where are the folder names taken from, i.e. ${upload.temp.dir}, 
> ${report.dir} etc and why the log dir is not substituted while the others 
> are?
>

-- 
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: No parameter substitution in ant when creating log.dir - DSpace 6 RC1

[Pantelis Karamolegkos]

On Sunday, May 22, 2016 at 6:53:59 PM UTC+3, Pantelis Karamolegkos wrote:
>
> After running fresh_install, a *folder* literally named ${log.dir} is 
> created in dspace_installer folder.
> It seems no parameter substitution takes place when running the ant target.
> Where are the folder names taken from, i.e. ${upload.temp.dir}, 
> ${report.dir} etc and why the log dir is not substituted while the others 
> are?
>

-- 
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] DSpace 6 RC1 - migrate_database ant target fails

[Pantelis Karamolegkos]

The above target fails with the following output:

 [java] 2016-05-22 18:56:33,108 INFO 
 org.dspace.services.caching.CachingServiceImpl @ destroy()
 [java] 2016-05-22 18:56:33,109 INFO 
 org.springframework.cache.ehcache.EhCacheManagerFactoryBean @ Shutting 
down EhCache CacheManager
 [java] 2016-05-22 18:56:33,109 INFO 
 org.dspace.services.sessions.SessionRequestServiceImpl @ shutdown
 [java] 2016-05-22 18:56:33,109 WARN 
 org.dspace.services.sessions.SessionRequestServiceImpl @ Request 
interceptor 
(org.dspace.services.events.SystemEventService$EventRequestInterceptor@7d35e191)
 
failed to execute on end (request-387-1463932592942): null
 [java] 2016-05-22 18:56:33,113 INFO 
 org.dspace.servicemanager.spring.SpringServiceManager @ Spring Service 
Manager Shutdown...
 [java] 2016-05-22 18:56:33,113 INFO 
 org.dspace.servicemanager.DSpaceServiceManager @ Shutdown DSpace core 
service manager
 [java] 2016-05-22 18:56:33,113 INFO 
 org.dspace.servicemanager.DSpaceKernelImpl @ DSpace kernel shutdown 
completed and unregistered MBean: 
org.dspace:name=2a65a6db-e965-4813-9766-fce8b7cb4f05,type=DSpaceKernel

BUILD FAILED
/home/pkaramol/Workspace/dspace_dir/dspace-6.0-rc1-src-release/dspace/target/dspace-installer/build.xml:799:
 
Java returned: 1

Working on Ubuntu 16.04, with Postgres 9.5 and Java 1.8.0_91

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