[Dspace-tech] Feedback problem
Dear Sir/Madam, I have installed Dspace1.5.1 on Redhat 9. When I tried to use the option Feedback its displaying internal system error. Inspite of giving all the details correctly in Mail settings in dspace.cfg, it's not working. Kindly help me. Thank You in advance. Regards, Geetha -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Feedback problem
Internal system error means, go look in the logs for your servlet container (such as Tomcat) and see what the error is. If the relevant log entries are unclear to you, please post them here. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Balance your desire for bells and whistles with the reality that only a little more than 2 percent of world population has broadband. -- Ledford and Tyler, _Google Analytics 2.0_ pgp5zSrc1pcul.pgp Description: PGP signature -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Feedback problem
Geetha, Take a look at our How to Troubleshoot an Error page. It will help you to look at your log files to tell what the real error is. The internal server error message is just a generic error that says something went wrong, so you'd need to look at the logs to see what the real problem may be. http://wiki.dspace.org/confluence/display/DSPACE/Troubleshoot+an+error Good luck. If you cannot figure it out, send the error message from the logs to this listserv and someone can try to help. - Tim On 5/20/2010 4:06 AM, Geetha Rao wrote: Dear Sir/Madam, I have installed Dspace1.5.1 on Redhat 9. When I tried to use the option Feedback its displaying internal system error. Inspite of giving all the details correctly in Mail settings in dspace.cfg, it's not working. Kindly help me. Thank You in advance. Regards, Geetha -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] LDAP with DSpace
An update on this issue, we had the suggested modification and it resolved
the issue. Users without an email specified in AD can auto login/register.
Anthony Avarca
aava...@anl.gov
630.252.4940
On Fri, May 7, 2010 at 1:09 PM, Avarca, Anthony aava...@anl.gov wrote:
We are seeing a similar problem. Some of our AD accounts do not have an
email specified. We have the appropriate entries in the cfg file. Going to
try the approach suggested:
Change:
if ((ldap.ldapEmail!=null)(!ldap.ldapEmail.equals()))
to
if (ldap.ldapEmail == null) ldap.ldapEmail = ;
if (true)
Anthony Avarca
aava...@anl.gov
630.252.4940
On Mon, Apr 26, 2010 at 7:44 PM, Max McGrath mmcgr...@carthage.eduwrote:
Hi Stuart -
Thanks for clarifying the rebuild and redeploy.
Unfortunately, still no luck.
I think I'll just start working on populating the e-mail field in LDAP.
Thanks for all your help! I really appreciate it!
Max
--
Max McGrath
Asst. Network Admin/Systems Specialist
Carthage College
262-552-5512
mmcgr...@carthage.edu
On Mon, Apr 26, 2010 at 4:02 PM, Stuart Lewis s.le...@auckland.ac.nzwrote:
Hi Max,
After making the change you need to re-build tomcat, and redeploy it. You
can do this by following steps 7, 8, and 9 in the installation guide:
- http://www.dspace.org/1_6_0Documentation/ch03.html#N108B6
But at step 8, as this is not a new installation, you need to run 'ant
update' instead of 'ant fresh_install'.
Thanks,
Stuart Lewis
IT Innovations Analyst and Developer
Te Tumu Herenga The University of Auckland Library
Auckland Mail Centre, Private Bag 92019, Auckland 1142, New Zealand
Ph: +64 (0)9 373 7599 x81928
On 27/04/2010, at 8:57 AM, Max McGrath wrote:
Stuart -
I made the change and then restarted Tomcat and it still is not working
for people that do not have their e-mail address in LDAP.
Should I have done more than just restarting Tomcat?
Thanks for all the help!
--
Max McGrath
Asst. Network Admin/Systems Specialist
Carthage College
262-552-5512
mmcgr...@carthage.edu
On Mon, Apr 26, 2010 at 3:46 PM, Stuart Lewis s.le...@auckland.ac.nz
wrote:
Hi Max,
Yes - that's right.
Change:
if ((ldap.ldapEmail!=null)(!ldap.ldapEmail.equals()))
to
if (ldap.ldapEmail == null) ldap.ldapEmail = ;
if (true)
(I've added an extra line there to hopefully catch another error that
could occur.)
Thanks,
Stuart Lewis
IT Innovations Analyst and Developer
Te Tumu Herenga The University of Auckland Library
Auckland Mail Centre, Private Bag 92019, Auckland 1142, New Zealand
Ph: +64 (0)9 373 7599 x81928
On 27/04/2010, at 4:15 AM, Max McGrath wrote:
Hi Stuart -
Here is the code I am looking at:
if ((ldap.ldapEmail!=null)(!ldap.ldapEmail.equals())) You want me
to change this to if (true) and then leave everything else the same???
{
try
{
eperson =
EPerson.findByEmail(context, ldap.ldapEmail);
if (eperson!=null)
{
log.info
(LogManager.getHeader(context,
type=ldap-login, type=ldap_but_already_email));
context.setIgnoreAuthorization(true);
eperson.setNetid(netid.toLowerCase());
eperson.update();
context.commit();
context.setIgnoreAuthorization(false);
context.setCurrentUser(eperson);
return SUCCESS;
}
else
{
if
(canSelfRegister(context, request, netid))
{
//
TEMPORARILY turn off authorisation
try
{
context.setIgnoreAuthorization(true);
eperson = EPerson.create(context);
if ((ldap.ldapEmail != null) (!ldap.ldapEmail.equals()))
{
eperson.setEmail(ldap.ldapEmail);
}
else
{
eperson.setEmail(netid +
ConfigurationManager.getProperty(ldap.netid_email_domain));
}
if ((ldap.ldapGivenName!=null) (!ldap.ldapGivenName.equals()))
{
eperson.setFirstName(ldap.ldapGivenName);
}
if ((ldap.ldapSurname!=null) (!ldap.ldapSurname.equals()))
{
eperson.setLastName(ldap.ldapSurname);
}
if ((ldap.ldapPhone!=null)(!ldap.ldapPhone.equals()))
{
eperson.setMetadata(phone, ldap.ldapPhone);
}
eperson.setNetid(netid.toLowerCase());
[Dspace-tech] Cocoon Exceptions deleting items in 1.6.0
Hi I've started emailing myself exceptions in the cocoon pipeline and noticed cocoon exceptions when deleting items (see below). Is anyone else seeing this in the cocoon log (there are no signs of any problem from the user interface)? I can't figure this out, so am working round it by commenting out the redirect to /community-list in the doDeleteItem function in administrative.js: /*cocoon.redirectTo(cocoon.request.getContextPath()+/community-list,true); getDSContext().complete(); cocoon.exit();*/ 2010-05-20 14:25:58,530 ERROR cocoon.handled - Could not read resource cocoon://DRI/6/admin/item at map:serialize type=xml - resource://aspects/EPerson/sitemap.xmap:332:31 at map:transform type=Navigation - resource://aspects/EPerson/sitemap.xmap:137:38 at map:generate - resource://aspects/EPerson/sitemap.xmap:126:19 at map:serialize type=xml - resource://aspects/Submission/sitemap.xmap:312:38 at map:transform type=Navigation - resource://aspects/Submission/sitemap.xmap:144:45 at map:generate - resource://aspects/Submission/sitemap.xmap:141:26 at map:serialize type=xml - resource://aspects/Statistics/sitemap.xmap:70:31 at map:generate - resource://aspects/Statistics/sitemap.xmap:33:19 at map:serialize type=xml - resource://aspects/ShareGeoOpen/sitemap.xmap:91:34 at map:generate - resource://aspects/ShareGeoOpen/sitemap.xmap:45:22 at map:serialize type=xml - resource://aspects/EdinaShared/sitemap.xmap:56:34 at map:generate - resource://aspects/EdinaShared/sitemap.xmap:28:22 at map:serialize type=xml - file:///home/grade/dspace/webapps/xmlui/aspects/aspects.xmap:115:34 at map:transform type=PageNotFound - file:///home/grade/dspace/webapps/xmlui/aspects/aspects.xmap:114:43 at map:generate - file:///home/grade/dspace/webapps/xmlui/aspects/aspects.xmap:113:22 at map:serialize type=xhtml - file:///home/grade/dspace/webapps/xmlui/themes/ShareGeoOpen/sitemap.xmap:184:34 at map:transform type=NamespaceFilter - file:///home/grade/dspace/webapps/xmlui/themes/ShareGeoOpen/sitemap.xmap:181:84 at map:transform type=NamespaceFilter - file:///home/grade/dspace/webapps/xmlui/themes/ShareGeoOpen/sitemap.xmap:180:78 at map:transform type=i18n - file:///home/grade/dspace/webapps/xmlui/themes/ShareGeoOpen/sitemap.xmap:174:33 at map:transform - file:///home/grade/dspace/webapps/xmlui/themes/ShareGeoOpen/sitemap.xmap:170:40 at map:transform type=IncludePageMeta - file:///home/grade/dspace/webapps/xmlui/themes/ShareGeoOpen/sitemap.xmap:155:45 at map:generate type=file - file:///home/grade/dspace/webapps/xmlui/themes/ShareGeoOpen/sitemap.xmap:131:55 at map:match - file:///home/grade/dspace/webapps/xmlui/themes/ShareGeoOpen/sitemap.xmap:128:28 at map:mount - file:///home/grade/dspace/webapps/xmlui/themes/themes.xmap:63:45 at map:match type=ThemeMatcher - file:///home/grade/dspace/webapps/xmlui/themes/themes.xmap:62:35 at map:mount - file:///home/grade/dspace/webapps/xmlui/sitemap.xmap:573:94 org.apache.cocoon.ProcessingException: Could not read resource cocoon://DRI/6/admin/item at map:serialize type=xml - resource://aspects/EPerson/sitemap.xmap:332:31 at map:transform type=Navigation - resource://aspects/EPerson/sitemap.xmap:137:38 at map:generate - resource://aspects/EPerson/sitemap.xmap:126:19 at map:serialize type=xml - resource://aspects/Submission/sitemap.xmap:312:38 at map:transform type=Navigation - resource://aspects/Submission/sitemap.xmap:144:45 at map:generate - resource://aspects/Submission/sitemap.xmap:141:26 at map:serialize type=xml - resource://aspects/Statistics/sitemap.xmap:70:31 at map:generate - resource://aspects/Statistics/sitemap.xmap:33:19 at map:serialize type=xml - resource://aspects/ShareGeoOpen/sitemap.xmap:91:34 at map:generate - resource://aspects/ShareGeoOpen/sitemap.xmap:45:22 at map:serialize type=xml - resource://aspects/EdinaShared/sitemap.xmap:56:34 at map:generate - resource://aspects/EdinaShared/sitemap.xmap:28:22 at map:serialize type=xml - file:///home/grade/dspace/webapps/xmlui/aspects/aspects.xmap:115:34 at map:transform type=PageNotFound - file:///home/grade/dspace/webapps/xmlui/aspects/aspects.xmap:114:43 at map:generate - file:///home/grade/dspace/webapps/xmlui/aspects/aspects.xmap:113:22 at map:serialize type=xhtml - file:///home/grade/dspace/webapps/xmlui/themes/ShareGeoOpen/sitemap.xmap:184:34 at map:transform type=NamespaceFilter - file:///home/grade/dspace/webapps/xmlui/themes/ShareGeoOpen/sitemap.xmap:181:84 at map:transform type=NamespaceFilter - file:///home/grade/dspace/webapps/xmlui/themes/ShareGeoOpen/sitemap.xmap:180:78 at map:transform type=i18n - file:///home/grade/dspace/webapps/xmlui/themes/ShareGeoOpen/sitemap.xmap:174:33 at map:transform - file:///home/grade/dspace/webapps/xmlui/themes/ShareGeoOpen/sitemap.xmap:170:40
[Dspace-tech] DuraSpace Launches Sponsorship Program
Dear DSpace Community, Today we have launched a Sponsorship Program to help sustain the DuraSpace organization. We have posted a press release (see a portion below) as well as some informational resources on the duraspace.org website. We have also mailed out 600 sponsorship packets to library directors at institutions around the world. Please encourage your institution's library director and others in your DSpace community network to support our efforts. With the community's help we will continue to enhance our existing technologies, advocate for our user community and innovate with new solutions that ensure the long-term durability of our collective digital heritage. Thank you! Valorie Hollister Director of Community Development, DSpace Project DuraSpace vhollis...@duraspace.org DuraSpace Launches Sponsorship Program Thursday, May 20th, 2010 8:49 am Written by: Carol Minton Morris Ithaca, NY DuraSpace, an independent 501(c)(3) not-for-profit organization, has launched its 2010 Sponsorship Program (http://DuraSpace.org/sponsorship.php) to engage leaders from university and library communities in supporting the organization’s ongoing mission. DuraSpace provides open source software and services to help ensure that current and future generations have access to our collective digital heritage. DuraSpace is the home of the DSpace (http://DSpace.org/) and Fedora (http://Fedora-commons.org/) open source software for digital repositories. Sponsors contribute at three levels of giving (http://DuraSpace.org/sponsorshiplevels.php) as an investment in community-driven approaches to preserving our digital heritage. Providing Leadership and Advocacy DuraSpace (http://DuraSpace.org/) is committed to providing leadership and innovation in the development and deployment of open technologies that promote durable, persistent access to digital data. Collaborators include highly respected academic institutions, government agencies, and scientific and cultural organizations. In addition to its work in open source software and services, DuraSpace advocates for open access to scholarly publications and for interoperability of the supporting technologies. DuraSpace has helped to establish open standards and protocols by working with other open source software projects and working closely with commercial partners on integration strategies. Clifford A. Lynch, Executive Director, Coalition for Networked Information (CNI) offers this rationale for financial support of the DuraSpace organization: “DuraSpace is well positioned to focus resources and talent to accelerate progress in areas critical to the research, education and cultural memory communities.”-- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Email notifications for internal server errors in newer versions
Ever since moving to 1.5 (and subsequently 1.6) I no longer receive emails when dspace throws an internal error. My address is still configured in the dspace.cfg. Did this feature go away or do I need to do something to enable this? -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] More re: Embargo error on Approval
Richard, Thank you very much for this documentation. I've been experimenting
with it today, and I just have few questions.
1.It seems like making the terms field a date type in the
input-forms.xml file would be the safest thing to do, instead of a textarea.
Any thoughts on this?
2. I deposited an item and set the terms field to some value in the
future. I am able to see the item and when I try to access the bitstream, I am
asked to authenticate, is this how it's suppose to work?
3. I tried running
/dspace/bin/dspace embargo-lifter
But it can't seem to find it. I looked around for the file embargo-lifter
but I can't find it. This is the error I get:
[dsp...@pocarisweat bin]$ ./dspace embargo-lifter
Command not found: embargo-lifter
Usage: dspace [command-name] {parameters}
- checker: Run the checksum checker
- checker-emailer: Send emails related to the checksum checker
- cleanup: Remove deleted bitstreams from the assetstore
- community-filiator: Tool to manage community and sub-community relationships
- create-administrator: Create a DSpace administrator account
- dsprop: View a DSpace property from dspace.cfg
- export: Export items or collections
- filter-media: Perform the media filtering to extract full text from
docuemnts and to create thumbnails
- generate-sitemaps: Generate search engine and html sitemaps
- harvest: Manage the OAI-PMH harvesting of external collections
- import: Import items into DSpace
- index: General index command (requires extra paramters)
- index-init: Initialise the search and browse indexes
- index-update: Update the search and browse indexes
- itemcounter: Update the item strength counts in the user interface
- itemupdate: Item update tool for altering metadata and bitstream content in
items
- make-handle-config: Run the handle server simple setup command
- metadata-export: Export metadata for batch editing
- metadata-import: Import metadata after batch editing
- packager: Execute a packager
- registry-loader: Load entries into a registry
- stat-general: Compile the general statistics
- stat-initial: Compile the initial statistics
- stat-monthly: Compile the monthly statistics
- stat-report-general: Create the general statistics report
- stat-report-initial: Create the general statistics report
- stat-report-monthly: Create the monthly statistics report
- stats-log-converter: Convert dspace.log files ready for import into solr
statistics
- stats-log-importer: Import previously converted log files into solr
statistics
- stats-util: Statistics Client for Maintenance of Solr Statistics Indexes
- structure-builder: Build DSpace commnity and collection structure
- test-database: Test the DSpace database connection is OK
- test-email: Test the DSpace email server settings OK
- sub-daily: Send daily subscription notices
- update-handle-prefix: Update handle records and metadata when moving from
one handle to another
From: Richard Rodgers [mailto:rrodg...@mit.edu]
Sent: Thursday, May 06, 2010 5:53 AM
To: Jizba, Richard
Cc: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] More re: Embargo error on Approval
Hi Richard:
Try this document for a fuller explanation. Let me know of any questions not
addressed in it. We will try to include it in the next release.
Thanks,
Richard R
On May 5, 2010, at 6:02 PM, Jizba, Richard wrote:
I finally realized that the Embargo Setter is reading dc.embargo.terms for the
date rather than dc.embargo.liftdate.
I've check our dspace.cfg file and there does not seem to be a mix-up. Nor is
there a mix-up on the submission form.
Perhaps I don't understand what these fields are for? What is dc.embargo.terms
supposed to do?
Richard
_
From: Jizba, Richard
Sent: Wednesday, May 05, 2010 4:05 PM
To:
'dspace-tech@lists.sourceforge.netmailto:'dspace-tech@lists.sourceforge.net'
Subject: Embargo error on Approval
Hello,
We we try to approve an item that has been submitted with an embargo date (in
dc.embargo.liftdate) we receive the following error:
java.lang.NullPointerException
at
org.dspace.embargo.EmbargoManager.getEmbargoDate(EmbargoManager.java:166)
Can anyone suggest how to resolve this?
We are running 1.6.
Richard Jizba
Creighton University
Omaha, NE
ATT1.cATT2.c
--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] More re: Embargo error on Approval
I think that launcher.xml should indicate what to run for embargo-lifter, but
there is no entry for it. Is this a bug in 1.6?
Thanks!
Jose
From: Blanco, Jose [mailto:blan...@umich.edu]
Sent: Thursday, May 20, 2010 3:56 PM
To: Richard Rodgers; Jizba, Richard
Cc: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] More re: Embargo error on Approval
Richard, Thank you very much for this documentation. I've been experimenting
with it today, and I just have few questions.
1.It seems like making the terms field a date type in the
input-forms.xml file would be the safest thing to do, instead of a textarea.
Any thoughts on this?
2. I deposited an item and set the terms field to some value in the
future. I am able to see the item and when I try to access the bitstream, I am
asked to authenticate, is this how it's suppose to work?
3. I tried running
/dspace/bin/dspace embargo-lifter
But it can't seem to find it. I looked around for the file embargo-lifter
but I can't find it. This is the error I get:
[dsp...@pocarisweat bin]$ ./dspace embargo-lifter
Command not found: embargo-lifter
Usage: dspace [command-name] {parameters}
- checker: Run the checksum checker
- checker-emailer: Send emails related to the checksum checker
- cleanup: Remove deleted bitstreams from the assetstore
- community-filiator: Tool to manage community and sub-community relationships
- create-administrator: Create a DSpace administrator account
- dsprop: View a DSpace property from dspace.cfg
- export: Export items or collections
- filter-media: Perform the media filtering to extract full text from
docuemnts and to create thumbnails
- generate-sitemaps: Generate search engine and html sitemaps
- harvest: Manage the OAI-PMH harvesting of external collections
- import: Import items into DSpace
- index: General index command (requires extra paramters)
- index-init: Initialise the search and browse indexes
- index-update: Update the search and browse indexes
- itemcounter: Update the item strength counts in the user interface
- itemupdate: Item update tool for altering metadata and bitstream content in
items
- make-handle-config: Run the handle server simple setup command
- metadata-export: Export metadata for batch editing
- metadata-import: Import metadata after batch editing
- packager: Execute a packager
- registry-loader: Load entries into a registry
- stat-general: Compile the general statistics
- stat-initial: Compile the initial statistics
- stat-monthly: Compile the monthly statistics
- stat-report-general: Create the general statistics report
- stat-report-initial: Create the general statistics report
- stat-report-monthly: Create the monthly statistics report
- stats-log-converter: Convert dspace.log files ready for import into solr
statistics
- stats-log-importer: Import previously converted log files into solr
statistics
- stats-util: Statistics Client for Maintenance of Solr Statistics Indexes
- structure-builder: Build DSpace commnity and collection structure
- test-database: Test the DSpace database connection is OK
- test-email: Test the DSpace email server settings OK
- sub-daily: Send daily subscription notices
- update-handle-prefix: Update handle records and metadata when moving from
one handle to another
From: Richard Rodgers [mailto:rrodg...@mit.edu]
Sent: Thursday, May 06, 2010 5:53 AM
To: Jizba, Richard
Cc: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] More re: Embargo error on Approval
Hi Richard:
Try this document for a fuller explanation. Let me know of any questions not
addressed in it. We will try to include it in the next release.
Thanks,
Richard R
On May 5, 2010, at 6:02 PM, Jizba, Richard wrote:
I finally realized that the Embargo Setter is reading dc.embargo.terms for the
date rather than dc.embargo.liftdate.
I've check our dspace.cfg file and there does not seem to be a mix-up. Nor is
there a mix-up on the submission form.
Perhaps I don't understand what these fields are for? What is dc.embargo.terms
supposed to do?
Richard
_
From: Jizba, Richard
Sent: Wednesday, May 05, 2010 4:05 PM
To:
'dspace-tech@lists.sourceforge.netmailto:'dspace-tech@lists.sourceforge.net'
Subject: Embargo error on Approval
Hello,
We we try to approve an item that has been submitted with an embargo date (in
dc.embargo.liftdate) we receive the following error:
java.lang.NullPointerException
at
org.dspace.embargo.EmbargoManager.getEmbargoDate(EmbargoManager.java:166)
Can anyone suggest how to resolve this?
We are running 1.6.
Richard Jizba
Creighton University
Omaha, NE
ATT1.cATT2.c
--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
[Dspace-tech] Problem with write.lock file in /dspace/search - DSpace 1.5.1
Hello, I updated a Collection description in one of our DSpace instances, a few times this morning. Each time I noticed that it took awhile for the update to complete. I finally looked in the log and saw errors referring to write.lock in /dspace/search. I looked in the /dspace/search directory and was surprised to find a write.lock file in the directory, but I was shocked to see that the search indexes had not been updated since March 29th! Long story short, somehow a failed transaction left a lock file in the search directory on March 29th and then every time after that someone performed a transaction that attempted to update the search indexes, the application waited 30 seconds (explanation later) and then an error occurred. So basically my repository's search indexes have been inaccurate since March 29th. That's easy to fix by running index-update.The problem is that I just sort of found the issue by accident while looking at something else in the dspace.log and was never notified about the errors. I looked at DSIndexer.java and saw that in the documentation at the top of the program it says: It will attempt to attain a lock on the index in the event that an update is requested and will wait a maximum of 30 seconds (a worst case scenario) to attain the lock before giving up and logging the failure to log4j and to the DSpace administrator email account. My question is this: Why wasn't an email sent out when the lock errors occurred? It looks as if the program was successfully writing to the log, but for some reason it didn't send out the emails. Is this an oversight, an issue that's been corrected in a subsequent version, or a problem specific to our installation? I feel like if I had received the email(s) back in March, I could have corrected it then. Below is the error output from the dspace.log. If any has any ideas, please let me know. Thanks! Best regards, Sue 2010-05-20 11:32:36,815 INFO org.dspace.app.webui.servlet.CommunityListServlet @ susan.m.thorn...@nasa.gov:session_id=AB9292929292929292929293939AFAFA:ip_addr=111.222.333.444:view_community_list: 2010-05-20 11:32:41,404 INFO org.dspace.app.webui.servlet.DSpaceServlet @ susan.m.thorn...@nasa.gov:session_id=AB9292929292929292929293939AFAFA:ip_addr=111.222.333.444:view_collection:collection_id=91 2010-05-20 11:32:41,404 INFO org.dspace.browse.BrowseEngine @ susan.m.thorn...@nasa.gov:session_id=AB9292929292929292929293939AFAFA:ip_addr=111.222.333.444:browse_mini: 2010-05-20 11:38:03,321 INFO org.dspace.app.webui.servlet.DSpaceServlet @ susan.m.thorn...@nasa.gov:session_id=AB9292929292929292929293939AFAFA:ip_addr=111.222.333.444:view_community:community_id=34 2010-05-20 11:38:03,325 INFO org.dspace.browse.BrowseEngine @ susan.m.thorn...@nasa.gov:session_id=AB9292929292929292929293939AFAFA:ip_addr=111.222.333.444:browse_mini: 2010-05-20 11:38:03,417 INFO org.dspace.app.webui.servlet.RetrieveServlet @ susan.m.thorn...@nasa.gov:session_id=AB9292929292929292929293939AFAFA:ip_addr=111.222.333.444:view_bitstream:bitstream_id=652731 2010-05-20 11:41:43,673 INFO org.dspace.content.Collection @ susan.m.thorn...@nasa.gov:session_id=AB9292929292929292929293939AFAFA:ip_addr=111.222.333.444:update_collection:collection_id=91 2010-05-20 11:42:13,731 ERROR org.dspace.search.DSIndexer @ Lock obtain timed out: SimpleFSLock@/export/home/dspace/search/write.lock org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: SimpleFSLock@/export/home/dspace/search/write.lock at org.apache.lucene.store.Lock.obtain(Lock.java:85) at org.apache.lucene.index.IndexWriter.init(IndexWriter.java:691) at org.apache.lucene.index.IndexWriter.init(IndexWriter.java:452) at org.dspace.search.DSIndexer.openIndex(DSIndexer.java:805) at org.dspace.search.DSIndexer.writeDocument(DSIndexer.java:877) at org.dspace.search.DSIndexer.buildDocument(DSIndexer.java:943) at org.dspace.search.DSIndexer.indexContent(DSIndexer.java:328) at org.dspace.search.SearchConsumer.end(SearchConsumer.java:207) at org.dspace.event.BasicDispatcher.dispatch(BasicDispatcher.java:171) at org.dspace.core.Context.commit(Context.java:384) at org.dspace.core.Context.complete(Context.java:350) at org.dspace.app.webui.servlet.admin.EditCommunitiesServlet.processConfirmEditCollection(EditCommunitiesServlet.java:693) at org.dspace.app.webui.servlet.admin.EditCommunitiesServlet.doDSPost(EditCommunitiesServlet.java:267) at org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:147) at org.dspace.app.webui.servlet.DSpaceServlet.doPost(DSpaceServlet.java:105) at javax.servlet.http.HttpServlet.service(HttpServlet.java:816) at javax.servlet.http.HttpServlet.service(HttpServlet.java:917) at
Re: [Dspace-tech] Email notifications for internal server errors in newer versions
No, it didn't go away. You should get an email when an internal error occurs. Have you checked your server to make sure your emails are being released? We had a situation recently where that happened. Also, have you checked the dspace.log file(s) for any error messages that may be occurring when your application attempts to send an email out? Sue Sue Walker-Thornton NASA Langley Research Center Integrated Library Systems Developer, Application Database Administrator ConITS Contract ~ NCI Information Systems, Inc. 130 Research Drive Hampton, VA 23666 Office: (757) 224-4074 ~ Mobile: (757) 506-9903 ~ Fax: (757) 224-4001 email: susan.m.thorn...@nasa.govmailto:susan.m.thorn...@nasa.gov From: Damian Marinaccio [mailto:dxm...@rit.edu] Sent: Thursday, May 20, 2010 12:55 PM To: Dspace-Tech Subject: [Dspace-tech] Email notifications for internal server errors in newer versions Ever since moving to 1.5 (and subsequently 1.6) I no longer receive emails when dspace throws an internal error. My address is still configured in the dspace.cfg. Did this feature go away or do I need to do something to enable this? -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] More re: Embargo error on Approval
It's a bug in 1.6.0. Will be fixed in 1.6.1.
Here's the page for the bug in Jira. The bugfix is there.
http://jira.dspace.org/jira/browse/DS-506
--Jason Fowler
From: Blanco, Jose [blan...@umich.edu]
Sent: Thursday, May 20, 2010 4:18 PM
To: Blanco, Jose; Richard Rodgers; Jizba, Richard
Cc: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] More re: Embargo error on Approval
I think that launcher.xml should indicate what to run for embargo-lifter, but
there is no entry for it. Is this a bug in 1.6?
Thanks!
Jose
From: Blanco, Jose [mailto:blan...@umich.edu]
Sent: Thursday, May 20, 2010 3:56 PM
To: Richard Rodgers; Jizba, Richard
Cc: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] More re: Embargo error on Approval
Richard, Thank you very much for this documentation. I’ve been experimenting
with it today, and I just have few questions.
1.It seems like making the terms field a date type in the
input-forms.xml file would be the safest thing to do, instead of a textarea.
Any thoughts on this?
2. I deposited an item and set the terms field to some value in the
future. I am able to see the item and when I try to access the bitstream, I am
asked to authenticate, is this how it’s suppose to work?
3. I tried running
/dspace/bin/dspace embargo-lifter
But it can’t seem to find it. I looked around for the file “embargo-lifter”
but I can’t find it. This is the error I get:
[dsp...@pocarisweat bin]$ ./dspace embargo-lifter
Command not found: embargo-lifter
Usage: dspace [command-name] {parameters}
- checker: Run the checksum checker
- checker-emailer: Send emails related to the checksum checker
- cleanup: Remove deleted bitstreams from the assetstore
- community-filiator: Tool to manage community and sub-community relationships
- create-administrator: Create a DSpace administrator account
- dsprop: View a DSpace property from dspace.cfg
- export: Export items or collections
- filter-media: Perform the media filtering to extract full text from
docuemnts and to create thumbnails
- generate-sitemaps: Generate search engine and html sitemaps
- harvest: Manage the OAI-PMH harvesting of external collections
- import: Import items into DSpace
- index: General index command (requires extra paramters)
- index-init: Initialise the search and browse indexes
- index-update: Update the search and browse indexes
- itemcounter: Update the item strength counts in the user interface
- itemupdate: Item update tool for altering metadata and bitstream content in
items
- make-handle-config: Run the handle server simple setup command
- metadata-export: Export metadata for batch editing
- metadata-import: Import metadata after batch editing
- packager: Execute a packager
- registry-loader: Load entries into a registry
- stat-general: Compile the general statistics
- stat-initial: Compile the initial statistics
- stat-monthly: Compile the monthly statistics
- stat-report-general: Create the general statistics report
- stat-report-initial: Create the general statistics report
- stat-report-monthly: Create the monthly statistics report
- stats-log-converter: Convert dspace.log files ready for import into solr
statistics
- stats-log-importer: Import previously converted log files into solr
statistics
- stats-util: Statistics Client for Maintenance of Solr Statistics Indexes
- structure-builder: Build DSpace commnity and collection structure
- test-database: Test the DSpace database connection is OK
- test-email: Test the DSpace email server settings OK
- sub-daily: Send daily subscription notices
- update-handle-prefix: Update handle records and metadata when moving from
one handle to another
From: Richard Rodgers [mailto:rrodg...@mit.edu]
Sent: Thursday, May 06, 2010 5:53 AM
To: Jizba, Richard
Cc: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] More re: Embargo error on Approval
Hi Richard:
Try this document for a fuller explanation. Let me know of any questions not
addressed in it. We will try to include it in the next release.
Thanks,
Richard R
On May 5, 2010, at 6:02 PM, Jizba, Richard wrote:
I finally realized that the Embargo Setter is reading dc.embargo.terms for the
date rather than dc.embargo.liftdate.
I’ve check our dspace.cfg file and there does not seem to be a mix-up. Nor is
there a mix-up on the submission form.
Perhaps I don’t understand what these fields are for? What is dc.embargo.terms
supposed to do?
Richard
_
From: Jizba, Richard
Sent: Wednesday, May 05, 2010 4:05 PM
To:
'dspace-tech@lists.sourceforge.netmailto:'dspace-tech@lists.sourceforge.net'
Subject: Embargo error on Approval
Hello,
We we try to approve an item that has been submitted with an embargo date (in
dc.embargo.liftdate) we receive the following error:
java.lang.NullPointerException
at
Re: [Dspace-tech] More re: Embargo error on Approval
Hi Jose:
Re #1. Date would be safe, but then you would not be able to enter the
'forever' (open ended) value, which is not a date. I would normally just use
'onebox' (smaller than a text-area).
Re #2. I'm not positive I understand the question, but the embargo does not
hide the metadata or item page - it merely removes 'read' permissions on the
bitstreams.
Re #3. As noted in another email, this is a 1.6 bug. You can get details about
fixing at:
http://jira.dspace.org/jira/browse/DS-506
Thanks,
Richard R
On May 20, 2010, at 3:55 PM, Blanco, Jose wrote:
Richard, Thank you very much for this documentation. I’ve been experimenting
with it today, and I just have few questions.
1.It seems like making the terms field a date type in the
input-forms.xml file would be the safest thing to do, instead of a textarea.
Any thoughts on this?
2. I deposited an item and set the terms field to some value in the
future. I am able to see the item and when I try to access the bitstream, I am
asked to authenticate, is this how it’s suppose to work?
3. I tried running
/dspace/bin/dspace embargo-lifter
But it can’t seem to find it. I looked around for the file “embargo-lifter”
but I can’t find it. This is the error I get:
[dsp...@pocarisweat bin]$ ./dspace embargo-lifter
Command not found: embargo-lifter
Usage: dspace [command-name] {parameters}
- checker: Run the checksum checker
- checker-emailer: Send emails related to the checksum checker
- cleanup: Remove deleted bitstreams from the assetstore
- community-filiator: Tool to manage community and sub-community relationships
- create-administrator: Create a DSpace administrator account
- dsprop: View a DSpace property from dspace.cfg
- export: Export items or collections
- filter-media: Perform the media filtering to extract full text from
docuemnts and to create thumbnails
- generate-sitemaps: Generate search engine and html sitemaps
- harvest: Manage the OAI-PMH harvesting of external collections
- import: Import items into DSpace
- index: General index command (requires extra paramters)
- index-init: Initialise the search and browse indexes
- index-update: Update the search and browse indexes
- itemcounter: Update the item strength counts in the user interface
- itemupdate: Item update tool for altering metadata and bitstream content in
items
- make-handle-config: Run the handle server simple setup command
- metadata-export: Export metadata for batch editing
- metadata-import: Import metadata after batch editing
- packager: Execute a packager
- registry-loader: Load entries into a registry
- stat-general: Compile the general statistics
- stat-initial: Compile the initial statistics
- stat-monthly: Compile the monthly statistics
- stat-report-general: Create the general statistics report
- stat-report-initial: Create the general statistics report
- stat-report-monthly: Create the monthly statistics report
- stats-log-converter: Convert dspace.log files ready for import into solr
statistics
- stats-log-importer: Import previously converted log files into solr
statistics
- stats-util: Statistics Client for Maintenance of Solr Statistics Indexes
- structure-builder: Build DSpace commnity and collection structure
- test-database: Test the DSpace database connection is OK
- test-email: Test the DSpace email server settings OK
- sub-daily: Send daily subscription notices
- update-handle-prefix: Update handle records and metadata when moving from
one handle to another
From: Richard Rodgers [mailto:rrodg...@mit.edu]
Sent: Thursday, May 06, 2010 5:53 AM
To: Jizba, Richard
Cc: dspace-tech@lists.sourceforge.netmailto:dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] More re: Embargo error on Approval
Hi Richard:
Try this document for a fuller explanation. Let me know of any questions not
addressed in it. We will try to include it in the next release.
Thanks,
Richard R
On May 5, 2010, at 6:02 PM, Jizba, Richard wrote:
I finally realized that the Embargo Setter is reading dc.embargo.terms for the
date rather than dc.embargo.liftdate.
I’ve check our dspace.cfg file and there does not seem to be a mix-up. Nor is
there a mix-up on the submission form.
Perhaps I don’t understand what these fields are for? What is dc.embargo.terms
supposed to do?
Richard
_
From: Jizba, Richard
Sent: Wednesday, May 05, 2010 4:05 PM
To:
'dspace-tech@lists.sourceforge.netmailto:'dspace-tech@lists.sourceforge.net'
Subject: Embargo error on Approval
Hello,
We we try to approve an item that has been submitted with an embargo date (in
dc.embargo.liftdate) we receive the following error:
java.lang.NullPointerException
at
org.dspace.embargo.EmbargoManager.getEmbargoDate(EmbargoManager.java:166)
Can anyone suggest how to resolve this?
We are running 1.6.
Richard Jizba
Creighton University
Omaha, NE
ATT1.cATT2.c
