[dspace-tech] Re: the dspce is not running

[Ahmed Maher]

i have the same problem 

and the log files are empty 


On Friday, November 18, 2016 at 3:44:08 PM UTC+2, Null Null wrote:
>
> hi.
> I did the installation. I did not get any errors. The anchors are not 
> working now. 
>
> error
>
> FAIL - Application at context path /jspui could not be started
>
>  
> 
>
> FAIL - Application at context path /xmlui could not be started
>
>

-- 
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] Default Group for new user

[Terry Brady]

Have you reviewed the options in
https://wiki.duraspace.org/display/DSDOC6x/Authentication+Plugins

Depending on your authentication method, there may be an option to assist
you.

On Mon, Nov 21, 2016 at 11:27 AM, Donald Bynum  wrote:

> I am running DSpace 5.5 with XMLUI and Mirage.  Is there a way to specify
> a non-anonymous group for a new user?  I'd like all new users to go into a
> group which has READ access (i.e. able to view and download content).  The
> ultimate goal is to only allow view and download to logged in users, but I
> don't want to have to perform a "manual" admin task for each new user,
> rather have them default to a group which has READ access to the repository.
>
> Regards,
>
> Don.
>
> --
> 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.
>



-- 
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
http://georgetown-university-libraries.github.io/

425-298-5498 (Seattle, WA)

-- 
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: vagrant-dspace install issues - librarian-puppet?

[Hardy Pottinger]

Hi, Darryn, can you give us more to go on?

--Hardy

On Nov 21, 2016 2:11 PM, "Darryn Brooking" 
wrote:

> Any thoughts on why librarian-puppet is failing? places to find more error
> messages?
>
> On Tue, Nov 22, 2016 at 5:02 AM, Hardy Pottinger <
> hardy.pottin...@gmail.com> wrote:
>
>> Done: https://github.com/DSpace/vagrant-dspace/blob/master/
>> README.md#requirements
>>
>> On Mon, Nov 21, 2016 at 9:26 AM, Tim Donohue 
>> wrote:
>>
>>> Yes, glad to hear the solution was found.  It *sounds* like this may be
>>> directly related to the fact that vagrant-dspace is now using Ubuntu
>>> 16.04LTS, which uses OpenSSH 7.0. For those who haven't yet discovered,
>>> OpenSSH 7 *disallows* DSA keys by default:
>>> http://viryagroup.com/what-we-do/our-blog-posts/hosting-and-
>>> linux-server-managment-blog/ssh-keys-failing-in-ubuntu-16-04
>>> -xenial-with-permission-denied-publickey
>>>
>>> So, if others are hitting this issue, you should make sure you are using
>>> an *RSA* SSH Key
>>>
>>> BTW, Hardy or Andrea, could you post an updated note to the
>>> vagrant-dspace setup/installation instructions about this?  It sounds like
>>> it may be something worth noting in the README at
>>> https://github.com/DSpace/vagrant-dspace
>>>
>>> - Tim
>>>
>>>
>>> On 11/20/2016 5:02 PM, Andrea Schweer wrote:
>>>
 Hi Hardy, all,

 On 11/19/2016 06:49 AM, Hardy Pottinger wrote:

> OK, here's a shot in the dark, and it will require you taking a leap
> back as it were, if in addition to destroying your vagrant environment you
> also delete the box image Vagrant has cached away for you:
>
> in your Vagrant-DSpace folder, run:
>
> vagrant box remove box-cutter/ubuntu1604
> vagrant destroy -f
>

 Same behaviour as before :( Vagrant 1.8.5, vagrant-vbguest installed,
 running on Ubuntu 16.04 with ssh agent that has a key in it that lets it
 pull from DSpace/DSpace via git.

 When I vagrant ssh to the box, I see the ssh key (via ssh-add -L).

 ssh -T -oStrictHostKeyChecking=no g...@github.com
 still gets
 Permission denied (publickey).

 Same command on the host gets
 Hi [username]! You've successfully authenticated, but GitHub does not
 provide shell access.

 Aha -- I may have solved the mystery? My key is an old one (dsa). On
 the host, my ssh config has
 Host github.com
 PubkeyAcceptedKeyTypes +ssh-dss

 When I add that on the vagrant box, I get the successful auth message
 just like on the host.

 So, I then generated an rsa key and added that to my github profile +
 the ssh agent on the host. This does indeed get me past the ssh problem,
 and through to a successful vagrant up - yay! I guess the alternative to
 generating a new key would be to make sure the ssh config option ends up on
 the vagrant box.

 [I still need to work out how to build the 5.x branch but I'm guessing
 the problems I ran into there are from the build.properties -> local.cfg
 change.]

 cheers,
 Andrea


>>> --
>>> Tim Donohue
>>> Technical Lead for DSpace & DSpaceDirect
>>> DuraSpace.org | DSpace.org | DSpaceDirect.org
>>>
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "DSpace Technical Support" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/dspace-tech/rv9GNuoGsvo/unsubscribe.
>> To unsubscribe from this group and all its topics, 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.
>>
>
> --
> 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.
>

-- 
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: vagrant-dspace install issues - librarian-puppet?

[Darryn Brooking]

Any thoughts on why librarian-puppet is failing? places to find more error
messages?

On Tue, Nov 22, 2016 at 5:02 AM, Hardy Pottinger 
wrote:

> Done: https://github.com/DSpace/vagrant-dspace/blob/
> master/README.md#requirements
>
> On Mon, Nov 21, 2016 at 9:26 AM, Tim Donohue 
> wrote:
>
>> Yes, glad to hear the solution was found.  It *sounds* like this may be
>> directly related to the fact that vagrant-dspace is now using Ubuntu
>> 16.04LTS, which uses OpenSSH 7.0. For those who haven't yet discovered,
>> OpenSSH 7 *disallows* DSA keys by default: http://viryagroup.com/what-we-
>> do/our-blog-posts/hosting-and-linux-server-managment-blog/ss
>> h-keys-failing-in-ubuntu-16-04-xenial-with-permission-denied-publickey
>>
>> So, if others are hitting this issue, you should make sure you are using
>> an *RSA* SSH Key
>>
>> BTW, Hardy or Andrea, could you post an updated note to the
>> vagrant-dspace setup/installation instructions about this?  It sounds like
>> it may be something worth noting in the README at
>> https://github.com/DSpace/vagrant-dspace
>>
>> - Tim
>>
>>
>> On 11/20/2016 5:02 PM, Andrea Schweer wrote:
>>
>>> Hi Hardy, all,
>>>
>>> On 11/19/2016 06:49 AM, Hardy Pottinger wrote:
>>>
 OK, here's a shot in the dark, and it will require you taking a leap
 back as it were, if in addition to destroying your vagrant environment you
 also delete the box image Vagrant has cached away for you:

 in your Vagrant-DSpace folder, run:

 vagrant box remove box-cutter/ubuntu1604
 vagrant destroy -f

>>>
>>> Same behaviour as before :( Vagrant 1.8.5, vagrant-vbguest installed,
>>> running on Ubuntu 16.04 with ssh agent that has a key in it that lets it
>>> pull from DSpace/DSpace via git.
>>>
>>> When I vagrant ssh to the box, I see the ssh key (via ssh-add -L).
>>>
>>> ssh -T -oStrictHostKeyChecking=no g...@github.com
>>> still gets
>>> Permission denied (publickey).
>>>
>>> Same command on the host gets
>>> Hi [username]! You've successfully authenticated, but GitHub does not
>>> provide shell access.
>>>
>>> Aha -- I may have solved the mystery? My key is an old one (dsa). On the
>>> host, my ssh config has
>>> Host github.com
>>> PubkeyAcceptedKeyTypes +ssh-dss
>>>
>>> When I add that on the vagrant box, I get the successful auth message
>>> just like on the host.
>>>
>>> So, I then generated an rsa key and added that to my github profile +
>>> the ssh agent on the host. This does indeed get me past the ssh problem,
>>> and through to a successful vagrant up - yay! I guess the alternative to
>>> generating a new key would be to make sure the ssh config option ends up on
>>> the vagrant box.
>>>
>>> [I still need to work out how to build the 5.x branch but I'm guessing
>>> the problems I ran into there are from the build.properties -> local.cfg
>>> change.]
>>>
>>> cheers,
>>> Andrea
>>>
>>>
>> --
>> Tim Donohue
>> Technical Lead for DSpace & DSpaceDirect
>> DuraSpace.org | DSpace.org | DSpaceDirect.org
>>
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "DSpace Technical Support" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/dspace-tech/rv9GNuoGsvo/unsubscribe.
> To unsubscribe from this group and all its topics, 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.
>

-- 
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] Default Group for new user

[Donald Bynum]

I am running DSpace 5.5 with XMLUI and Mirage.  Is there a way to specify a 
non-anonymous group for a new user?  I'd like all new users to go into a 
group which has READ access (i.e. able to view and download content).  The 
ultimate goal is to only allow view and download to logged in users, but I 
don't want to have to perform a "manual" admin task for each new user, 
rather have them default to a group which has READ access to the repository.

Regards,

Don.

-- 
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: vagrant-dspace install issues - librarian-puppet?

[Hardy Pottinger]

Done:
https://github.com/DSpace/vagrant-dspace/blob/master/README.md#requirements

On Mon, Nov 21, 2016 at 9:26 AM, Tim Donohue  wrote:

> Yes, glad to hear the solution was found.  It *sounds* like this may be
> directly related to the fact that vagrant-dspace is now using Ubuntu
> 16.04LTS, which uses OpenSSH 7.0. For those who haven't yet discovered,
> OpenSSH 7 *disallows* DSA keys by default: http://viryagroup.com/what-we-
> do/our-blog-posts/hosting-and-linux-server-managment-blog/ss
> h-keys-failing-in-ubuntu-16-04-xenial-with-permission-denied-publickey
>
> So, if others are hitting this issue, you should make sure you are using
> an *RSA* SSH Key
>
> BTW, Hardy or Andrea, could you post an updated note to the vagrant-dspace
> setup/installation instructions about this?  It sounds like it may be
> something worth noting in the README at https://github.com/DSpace/vagr
> ant-dspace
>
> - Tim
>
>
> On 11/20/2016 5:02 PM, Andrea Schweer wrote:
>
>> Hi Hardy, all,
>>
>> On 11/19/2016 06:49 AM, Hardy Pottinger wrote:
>>
>>> OK, here's a shot in the dark, and it will require you taking a leap
>>> back as it were, if in addition to destroying your vagrant environment you
>>> also delete the box image Vagrant has cached away for you:
>>>
>>> in your Vagrant-DSpace folder, run:
>>>
>>> vagrant box remove box-cutter/ubuntu1604
>>> vagrant destroy -f
>>>
>>
>> Same behaviour as before :( Vagrant 1.8.5, vagrant-vbguest installed,
>> running on Ubuntu 16.04 with ssh agent that has a key in it that lets it
>> pull from DSpace/DSpace via git.
>>
>> When I vagrant ssh to the box, I see the ssh key (via ssh-add -L).
>>
>> ssh -T -oStrictHostKeyChecking=no g...@github.com
>> still gets
>> Permission denied (publickey).
>>
>> Same command on the host gets
>> Hi [username]! You've successfully authenticated, but GitHub does not
>> provide shell access.
>>
>> Aha -- I may have solved the mystery? My key is an old one (dsa). On the
>> host, my ssh config has
>> Host github.com
>> PubkeyAcceptedKeyTypes +ssh-dss
>>
>> When I add that on the vagrant box, I get the successful auth message
>> just like on the host.
>>
>> So, I then generated an rsa key and added that to my github profile + the
>> ssh agent on the host. This does indeed get me past the ssh problem, and
>> through to a successful vagrant up - yay! I guess the alternative to
>> generating a new key would be to make sure the ssh config option ends up on
>> the vagrant box.
>>
>> [I still need to work out how to build the 5.x branch but I'm guessing
>> the problems I ran into there are from the build.properties -> local.cfg
>> change.]
>>
>> cheers,
>> Andrea
>>
>>
> --
> 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.

Re: [dspace-tech] Re: vagrant-dspace install issues - librarian-puppet?

[Tim Donohue]

Yes, glad to hear the solution was found.  It *sounds* like this may be 
directly related to the fact that vagrant-dspace is now using Ubuntu 
16.04LTS, which uses OpenSSH 7.0. For those who haven't yet discovered, 
OpenSSH 7 *disallows* DSA keys by default: 
http://viryagroup.com/what-we-do/our-blog-posts/hosting-and-linux-server-managment-blog/ssh-keys-failing-in-ubuntu-16-04-xenial-with-permission-denied-publickey


So, if others are hitting this issue, you should make sure you are using 
an *RSA* SSH Key


BTW, Hardy or Andrea, could you post an updated note to the 
vagrant-dspace setup/installation instructions about this?  It sounds 
like it may be something worth noting in the README at 
https://github.com/DSpace/vagrant-dspace


- Tim

On 11/20/2016 5:02 PM, Andrea Schweer wrote:

Hi Hardy, all,

On 11/19/2016 06:49 AM, Hardy Pottinger wrote:
OK, here's a shot in the dark, and it will require you taking a leap 
back as it were, if in addition to destroying your vagrant 
environment you also delete the box image Vagrant has cached away for 
you:


in your Vagrant-DSpace folder, run:

vagrant box remove box-cutter/ubuntu1604
vagrant destroy -f


Same behaviour as before :( Vagrant 1.8.5, vagrant-vbguest installed, 
running on Ubuntu 16.04 with ssh agent that has a key in it that lets 
it pull from DSpace/DSpace via git.


When I vagrant ssh to the box, I see the ssh key (via ssh-add -L).

ssh -T -oStrictHostKeyChecking=no g...@github.com
still gets
Permission denied (publickey).

Same command on the host gets
Hi [username]! You've successfully authenticated, but GitHub does not 
provide shell access.


Aha -- I may have solved the mystery? My key is an old one (dsa). On 
the host, my ssh config has

Host github.com
PubkeyAcceptedKeyTypes +ssh-dss

When I add that on the vagrant box, I get the successful auth message 
just like on the host.


So, I then generated an rsa key and added that to my github profile + 
the ssh agent on the host. This does indeed get me past the ssh 
problem, and through to a successful vagrant up - yay! I guess the 
alternative to generating a new key would be to make sure the ssh 
config option ends up on the vagrant box.


[I still need to work out how to build the 5.x branch but I'm guessing 
the problems I ran into there are from the build.properties -> 
local.cfg change.]


cheers,
Andrea



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

Re: [dspace-tech] DSPACE-CRIS error load publications

[Pascarelli Luigi Andrea]

I checked your web application and I think that you have many problems not only 
this!

I see that you are testing the DSpace CRIS version 5.5.0 please download the 
last stable version 5.6.1 from https://github.com/4Science/DSpace.git 
(https://github.com/4Science/DSpace/releases/tag/dspace-cris-5.6.1)

In any case the error is related to this piece of code 
https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace-api/src/main/java/org/dspace/content/Community.java#L343

Check your database maybe you fell into an installation issue.

Please open a database console and run this query:

select * from metadataschemaregistry where short_id = 'dc';

and this query:

select * from metadatafieldregistry where metadata_schema_id = 1 and element = 
'title' and qualifier is null;

Let me know.

Best,

Luigi Andrea

Il 21/11/2016 13:09, Vitor Rodrigues ha scritto:
Hello,

I got this error when i tried load the publications


2016-11-21 09:34:28,125 WARN  org.dspace.app.webui.servlet.InternalErrorServlet 
@ :session_id=7AC3DE4A841863ADB075FC76FC3B85BA:internal_error:-- URL Was: 
http://200.145.5.2/simple-search?query==publications
-- Method: GET
-- Parameters were:
-- query: ""
-- location: "publications"

java.lang.NullPointerException
at org.dspace.content.Community.findAllTop(Community.java:343)
at 
org.dspace.app.webui.discovery.DiscoverySearchRequestProcessor.doSimpleSearch(DiscoverySearchRequestProcessor.java:258)
at 
org.dspace.app.webui.servlet.SimpleSearchServlet.doDSGet(SimpleSearchServlet.java:63)
at 
org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:119)
at 
org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.dspace.app.webui.cris.filter.ExploreLocationFilter.doFilter(ExploreLocationFilter.java:88)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:221)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:956)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:436)
at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:190)
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
at 
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
2016-11-21 09:50:38,972 INFO  org.dspace.browse.BrowseEngine @ 
anonymous:session_id=30DDC7A7C7BE1EE762D0071E2232C74F:ip_addr=130.211.177.74:browse_mini:
2016-11-21 09:50:38,986 INFO  org.dspace.app.webui.discovery.DiscoverUtility @ 
facets for scope, null: 1

--
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] dspace6 xmlui Error - 404

[Ahmed Maher]

Hi All,
i installed Dspace-6 on debian-8 jessi 
and xmlui didn't start or deployed , only /solr deployed sucessfully 
i using openjdk1.8 , tomcat8 , postgresql 9.4 

all installation steps successfully completed 
when browse to /xmlui  said 404 error 
the tomcat error file didn't contains error messages 

thanks

-- 
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] batch metadata import with ORCID

[Stefanie Behnke]

 

Dear all,

 

I am using Dspace 5.5 with XMLUI mirage theme.

 

I want to use the batch metadata import as described in:

https://wiki.duraspace.org/display/DSDOC5x/ORCID+Integration#ORCIDIntegration-EditingexistingitemsusingBatchCSVEditing

 

When I use

ORCID:dc.contributor.author

 

In the column, I always get the error: 

 

java.lang.NullPointerException

at 
org.dspace.app.bulkedit.MetadataImport.compare(MetadataImport.java:49

5)

at 
org.dspace.app.bulkedit.MetadataImport.runImport(MetadataImport.java:

169)

at 
org.dspace.app.bulkedit.MetadataImport.main(MetadataImport.java:1341)

 

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.

java:62)

at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces

sorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at 
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.j

ava:226)

at 
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:78)

There were no changes detected

 



When I use ORCID.dc.contributor.author instead of 
ORCID:dc.contributor.author

The lookup works, but the metadata field cannot be added:

 

Changes for item: 14770 (10.2312/2630804)

+ Add(ORCID.dc.contributor[]): Behnke, Stefanie

 

1 item(s) will be changed

 

Do you want to make these changes? [y/n] y

java.sql.SQLException: Invalid metadata field: [ORCID.dc.contributor]

at 
org.dspace.content.DSpaceObject.updateMetadata(DSpaceObject.java:122)

 

at org.dspace.content.Item.update(Item.java:1100)

at 
org.dspace.app.bulkedit.MetadataImport.compare(MetadataImport.java:62

0)

at 
org.dspace.app.bulkedit.MetadataImport.runImport(MetadataImport.java:

169)

at 
org.dspace.app.bulkedit.MetadataImport.main(MetadataImport.java:1396)

 

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.

java:62)

at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces

sorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at 
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.j

ava:226)

at 
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:78)



 

How can I manage the correct editing? What has to be in the column headline?

 

Thanks in advance

Stefanie

-- 
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-CRIS error load publications

[Vitor Rodrigues]

Hello,

I got this error when i tried load the publications

2016-11-21 09:34:28,125 WARN  org.dspace.app.webui.servlet.InternalErrorServlet 
@ :session_id=7AC3DE4A841863ADB075FC76FC3B85BA:internal_error:-- URL Was: 
http://200.145.5.2/simple-search?query==publications
-- Method: GET
-- Parameters were:
-- query: ""
-- location: "publications"

java.lang.NullPointerException
at org.dspace.content.Community.findAllTop(Community.java:343)
at 
org.dspace.app.webui.discovery.DiscoverySearchRequestProcessor.doSimpleSearch(DiscoverySearchRequestProcessor.java:258)
at 
org.dspace.app.webui.servlet.SimpleSearchServlet.doDSGet(SimpleSearchServlet.java:63)
at 
org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:119)
at 
org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.dspace.app.webui.cris.filter.ExploreLocationFilter.doFilter(ExploreLocationFilter.java:88)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:221)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:956)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:436)
at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:190)
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
at 
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
2016-11-21 09:50:38,972 INFO  org.dspace.browse.BrowseEngine @ 
anonymous:session_id=30DDC7A7C7BE1EE762D0071E2232C74F:ip_addr=130.211.177.74:browse_mini:
2016-11-21 09:50:38,986 INFO  org.dspace.app.webui.discovery.DiscoverUtility @ 
facets for scope, null: 1

-- 
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: DOI

[Massimiliano CILURZO]

 Dear All,

I noticed that if I run 
  /dspace/bin/dspace doi-organiser -l
There are no DOIs queued for reservation.

There are no DOIs queued for registration.

DOIs queued for update: 
doi:10.14273/unisa-679 (belongs to item with handle 105xxx/x)
doi:10.14273/unisa-680 (belongs to item with handle 1055xx6/2xxx)
doi:10.14273/unisa-682 (belongs to item with handle 1055xx6/xxx)

There are no DOIs queued for deletion.

I can see som new item but when I run
 /dspace/bin/dspace doi-organiser -u
The system tell me
Email alert is sent.
It wasn't possible to update this identifier: doi:10.14zzz/unixx-679
Email alert is sent.
It wasn't possible to update this identifier: doi:10.14/unixx-680
Email alert is sent.
It wasn't possible to update this identifier: doi:10.12zzz/unixx-682
 ERROR org.dspace.identifier.doi.DOIOrganiser @ It wasn't possible to 
update this identifier:  doi:10.14zz/uni-682 Exceptions code:  CODE_NOT_SET
org.dspace.identifier.doi.DOIIdentifierException: DSO with type ITEM and id 
2485 already has DOI . Won't reserve DOI doi:10.1xxxun-682 for it.
at 
org.dspace.identifier.doi.DataCiteConnector.reserveDOI(DataCiteConnector.java:529)
at 
org.dspace.identifier.doi.DataCiteConnector.updateMetadata(DataCiteConnector.java:681)
at 
org.dspace.identifier.DOIIdentifierProvider.updateMetadataOnline(DOIIdentifierProvider.java:413)
at 
org.dspace.identifier.doi.DOIOrganiser.update(DOIOrganiser.java:669)
at 
org.dspace.identifier.doi.DOIOrganiser.runCLI(DOIOrganiser.java:265)
at org.dspace.identifier.doi.DOIOrganiser.main(DOIOrganiser.java:82)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:226)
at 
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:78) 

> It wasn't possible to update this identifier
>

Thanks
Best regards
Massimiliano 

-- 
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] DOI

[Massimiliano CILURZO]

Dear all,
I have DSPACE 5.3 and we have configured the  DOI DataCite Plugin.
Till some month ago every worked fine.
But now it seems that we haven't the doi anymore.
We have configured dspace.cfg, DIM2DataCite.xsl and identifier-service.xml:
identifier-service.xml configuration:


http://www.springframework.org/schema/beans;
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
   xsi:schemaLocation="http://www.springframework.org/schema/beans
  
 http://www.springframework.org/schema/beans/spring-beans-2.5.xsd;>




   

  























In the source page of a new item we haven't 
http://dx.doi.org/10.1xzxxx scheme="
DCTERMS.URI" /> anymore as you see

 
 
 
 
 
 
http://hdl.handle.net/10556/1738; scheme
="DCTERMS.URI" /> 
http://dx.doi.org/10.1xzxxx scheme="
DCTERMS.URI" />
Could you help us.
Thanks
Best regards
Massimiliano

-- 
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 generating a lot of DNS queries

[Mesut Güngör]

When i run tcpdump on the DSPACE server it is generating alot of DNS 
queries. Is it normal ? Sometimes it increases to 10 queries per second.  
What causes this ? any statistics module or anything else ? side note : 
when i shutdown tomcat on the server dns queries stops.

tcpdump -vvv   -n dst host 8.8.8.8

tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 
bytes
12:50:54.963062 IP (tos 0x0, ttl 64, id 36065, offset 0, flags [DF], proto 
UDP (17), length 72)
193.140.248.74.29530 > 8.8.8.8.domain: [bad udp cksum 1012!] 50042+ 
PTR? 114.66.249.66.in-addr.arpa. (44)
12:50:55.403481 IP (tos 0x0, ttl 64, id 36505, offset 0, flags [DF], proto 
UDP (17), length 72)
193.140.248.74.57157 > 8.8.8.8.domain: [bad udp cksum 4018!] 20831+ 
PTR? 114.66.249.66.in-addr.arpa. (44)
12:50:55.507179 IP (tos 0x0, ttl 64, id 36609, offset 0, flags [DF], proto 
UDP (17), length 72)
193.140.248.74.28586 > 8.8.8.8.domain: [bad udp cksum 65c0!] 6357+ PTR? 
114.66.249.66.in-addr.arpa. (44)
12:50:56.043793 IP (tos 0x0, ttl 64, id 37146, offset 0, flags [DF], proto 
UDP (17), length 72)
193.140.248.74.63576 > 8.8.8.8.domain: [bad udp cksum d302!] 19897+ 
PTR? 114.66.249.66.in-addr.arpa. (44)
12:50:56.126384 IP (tos 0x0, ttl 64, id 37228, offset 0, flags [DF], proto 
UDP (17), length 69)
193.140.248.74.46604 > 8.8.8.8.domain: [bad udp cksum 3a9d!] 59462+ 
PTR? 16.9.88.77.in-addr.arpa. (41)
12:50:56.554399 IP (tos 0x0, ttl 64, id 37656, offset 0, flags [DF], proto 
UDP (17), length 72)
193.140.248.74.57978 > 8.8.8.8.domain: [bad udp cksum a7de!] 34754+ 
PTR? 114.66.249.66.in-addr.arpa. (44)
12:50:56.681578 IP (tos 0x0, ttl 64, id 37783, offset 0, flags [DF], proto 
UDP (17), length 72)
193.140.248.74.5296 > 8.8.8.8.domain: [bad udp cksum 29a2!] 37385+ PTR? 
116.66.249.66.in-addr.arpa. (44)
12:50:56.974473 IP (tos 0x0, ttl 64, id 38076, offset 0, flags [DF], proto 
UDP (17), length 72)
193.140.248.74.25179 > 8.8.8.8.domain: [bad udp cksum 1186!] 24694+ 
PTR? 116.66.249.66.in-addr.arpa. (44)
12:50:57.295146 IP (tos 0x0, ttl 64, id 38397, offset 0, flags [DF], proto 
UDP (17), length 72)
193.140.248.74.4938 > 8.8.8.8.domain: [bad udp cksum 4505!] 12122+ PTR? 
120.66.249.66.in-addr.arpa. (44)
12:50:57.622233 IP (tos 0x0, ttl 64, id 38724, offset 0, flags [DF], proto 
UDP (17), length 72)
193.140.248.74.11070 > 8.8.8.8.domain: [bad udp cksum ac81!] 39930+ 
PTR? 114.66.249.66.in-addr.arpa. (44)
12:50:57.855780 IP (tos 0x0, ttl 64, id 38958, offset 0, flags [DF], proto 
UDP (17), length 72)
193.140.248.74.4648 > 8.8.8.8.domain: [bad udp cksum 9755!] 57637+ PTR? 
114.66.249.66.in-addr.arpa. (44)

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