[dspace-tech] Shifting of dspace from one computer to other computer
dear sir, I have fully developed Dspace working on one computer, now i want to move that setup of dspace from one computer to another . My dspace version is 6.2. I have tried to google but couldnt get anything . -- Regards, Vinod Kumar DESIDOC, DRDO Min of Defence Metcalfe House Delhi-110054 011-2390245 -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To 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] Problem indexing OAI
Thanks, Terry: I will look at those changes. However, I was able to get my OAI to work for now. I had a two fold problem. I originally had two “bad” records that were causing the OAI indexing to stop working, but once I had those identified and taken care of, I ran into the hibernate problems, which were actually caused by a separate script that I wrote to eliminate idle Postgres processes. The script was more aggressive than I intended and it was interfering with the DSpace jobs that use Postgres. In any case, I appreciate your advice and your help. George On Wed, Jan 9, 2019 at 3:43 PM Terry Brady wrote: > George, > > I was seeing out of memory errors for the oai import process. If that is > the problem you are encountering, the following PR has resolved the issue > for me. > > https://github.com/DSpace/DSpace/pull/2320 > > Terry > > On Mon, Jan 7, 2019 at 1:03 PM George Kozak wrote: > >> Hi, Mark: >> In the postgres log file, I am seeing "The postmaster has commanded this >> server process to roll back the current transaction and exit, because >> another server process exited abnormally and possibly corrupted shared >> memory." whenever this fails. I am suspecting maybe an out of memory >> condition. >> George Kozak >> Cornell University >> >> On Mon, Jan 7, 2019 at 12:07 PM Mark H. Wood >> wrote: >> >>> I see that this is caused by a connection reset. Is PostgreSQL logging >>> anything interesting around the time that this happens? >>> >>> Remember that the DSpace connection limit should be a bit *lower* than >>> the Pg connection limit, because Pg reserves a few connections for >>> administration. >>> >>> I found >>> https://stackoverflow.com/questions/23951796/hibernate-could-not-extract-resultset-exception >>> which talks about a connection pool which times out connections but is not >>> set to test-on-borrow, so that the client can borrow a closed connection >>> and gets an error. >>> >>> On Friday, January 4, 2019 at 5:06:28 PM UTC-5, George Kozak wrote: Tim: I checked the max connections in postgres and dspace, and there was a discrepancy, but after fixing that, I am still having the same problem. I double checked the hibernate configs, and they are the defaults. So, I have attached the error trace from my oai indexing job. Perhaps, that will reveal something. George Kozak Cornell University On Fri, Jan 4, 2019 at 1:50 PM Tim Donohue wrote: > Hi George, > > That is an odd error. It almost sounds like Hibernate is losing > access to the database (maybe a connection timeout or something?). > > Could you check your logs to see if there's more information around > *when* and *how* this error occurs. You said it's occurring at different > "intervals", but I'm wondering if there's any more information that can be > gathered from the logs (or from the full stacktrace of the error, assuming > one exists). > > For what it's worth, I've not seen this error before. It's hard to > say right now if this is a configuration error or a bug. I think we'd need > more information to narrow things down. It's *possible* there's > something > from your upgrade that resulted in a misconfiguration. You may want to > double check that your Hibernate truly are the defaults, and that your > Database connection settings & pooling info looks good. You also should > double check that PostgreSQL (or Oracle) is configured to allow *at least* > the number of connections that "db.maxconnections" allows -- if you > increased the DSpace setting, it may be expecting more connections than > your database is willing to provide. > > Just a few thoughts there. > > - Tim > > On Fri, Jan 4, 2019 at 12:02 PM George Kozak > wrote: > >> Hi, Terry: >> I am using jdk1.8.0_74 so java 7 is not the problem. We did upgrade >> a few months ago, and ran into trouble immediately with the OAI >> index. Emilio Lorenzo and Adan Roman gave me a patch to >> org.dspace.xoai.app.XOAI.java to print out records being indexed in >> verbose >> mode, and that helped me locate a "bad" record that was causing our OAI >> index to fail. I eliminated that record, and restarted our OAI process, >> and then encountered the >> "org.hibernate.exception.JDBCConnectionException: >> could not extract ResultSet". It doesn't appear to be a specific record >> that is causing this because the crash occurs at different intervals >> during >> the index. >> I never adjusted the hibernate configuration (using defaults). Do >> you think that may be the issue? >> >> George Kozak >> Cornell University >> >> On Thu, Jan 3, 2019 at 4:36 PM Terry Brady < >> terry.br...@georgetown.edu> wrote: >> >>> George, >>> >>> I am not seeing this error. >>> >>> Is there any
Re: [dspace-tech] A way to alter metadata values for display?
Gabe, Please provide a couple additional bits of information. - Which version of DSpace are you using? - Which UI do you use? XMLUI or JSPUI? - If you are running XMLUI, what theme do you use? Terry On Wed, Jan 9, 2019 at 1:38 PM wrote: > Group- > > Is there a straightforward way to hide the actual values contained in a > field, while displaying translated or crosswalked versions of those > values? We'd like to automatically translate two letter language codes > into text: the language field would contain the value 'en' but display the > value 'english'. > > Can anyone suggest a procedure for accomplishing this? > > Thank you in advance for your help! We are just getting started with > DSpace. > > -Gabe > > -- > All messages to this mailing list should adhere to the DuraSpace Code of > Conduct: https://duraspace.org/about/policies/code-of-conduct/ > --- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dspace-tech+unsubscr...@googlegroups.com. > To 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 https://github.com/terrywbrady/info 425-298-5498 (Seattle, WA) -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To 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] A way to alter metadata values for display?
Group- Is there a straightforward way to hide the actual values contained in a field, while displaying translated or crosswalked versions of those values? We'd like to automatically translate two letter language codes into text: the language field would contain the value 'en' but display the value 'english'. Can anyone suggest a procedure for accomplishing this? Thank you in advance for your help! We are just getting started with DSpace. -Gabe -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To 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] Problem indexing OAI
George, I was seeing out of memory errors for the oai import process. If that is the problem you are encountering, the following PR has resolved the issue for me. https://github.com/DSpace/DSpace/pull/2320 Terry On Mon, Jan 7, 2019 at 1:03 PM George Kozak wrote: > Hi, Mark: > In the postgres log file, I am seeing "The postmaster has commanded this > server process to roll back the current transaction and exit, because > another server process exited abnormally and possibly corrupted shared > memory." whenever this fails. I am suspecting maybe an out of memory > condition. > George Kozak > Cornell University > > On Mon, Jan 7, 2019 at 12:07 PM Mark H. Wood wrote: > >> I see that this is caused by a connection reset. Is PostgreSQL logging >> anything interesting around the time that this happens? >> >> Remember that the DSpace connection limit should be a bit *lower* than >> the Pg connection limit, because Pg reserves a few connections for >> administration. >> >> I found >> https://stackoverflow.com/questions/23951796/hibernate-could-not-extract-resultset-exception >> which talks about a connection pool which times out connections but is not >> set to test-on-borrow, so that the client can borrow a closed connection >> and gets an error. >> >> On Friday, January 4, 2019 at 5:06:28 PM UTC-5, George Kozak wrote: >>> >>> Tim: >>> I checked the max connections in postgres and dspace, and there was a >>> discrepancy, but after fixing that, I am still having the same problem. I >>> double checked the hibernate configs, and they are the defaults. So, I >>> have attached the error trace from my oai indexing job. Perhaps, that will >>> reveal something. >>> George Kozak >>> Cornell University >>> >>> On Fri, Jan 4, 2019 at 1:50 PM Tim Donohue >>> wrote: >>> Hi George, That is an odd error. It almost sounds like Hibernate is losing access to the database (maybe a connection timeout or something?). Could you check your logs to see if there's more information around *when* and *how* this error occurs. You said it's occurring at different "intervals", but I'm wondering if there's any more information that can be gathered from the logs (or from the full stacktrace of the error, assuming one exists). For what it's worth, I've not seen this error before. It's hard to say right now if this is a configuration error or a bug. I think we'd need more information to narrow things down. It's *possible* there's something from your upgrade that resulted in a misconfiguration. You may want to double check that your Hibernate truly are the defaults, and that your Database connection settings & pooling info looks good. You also should double check that PostgreSQL (or Oracle) is configured to allow *at least* the number of connections that "db.maxconnections" allows -- if you increased the DSpace setting, it may be expecting more connections than your database is willing to provide. Just a few thoughts there. - Tim On Fri, Jan 4, 2019 at 12:02 PM George Kozak wrote: > Hi, Terry: > I am using jdk1.8.0_74 so java 7 is not the problem. We did upgrade a > few months ago, and ran into trouble immediately with the OAI > index. Emilio Lorenzo and Adan Roman gave me a patch to > org.dspace.xoai.app.XOAI.java to print out records being indexed in > verbose > mode, and that helped me locate a "bad" record that was causing our OAI > index to fail. I eliminated that record, and restarted our OAI process, > and then encountered the "org.hibernate.exception.JDBCConnectionException: > could not extract ResultSet". It doesn't appear to be a specific record > that is causing this because the crash occurs at different intervals > during > the index. > I never adjusted the hibernate configuration (using defaults). Do you > think that may be the issue? > > George Kozak > Cornell University > > On Thu, Jan 3, 2019 at 4:36 PM Terry Brady > wrote: > >> George, >> >> I am not seeing this error. >> >> Is there any chance that you are using an older version of java (such >> as Java 7) when you run the dspace command? >> >> Did you upgrade recently? >> >> On Thu, Jan 3, 2019 at 11:02 AM George Kozak >> wrote: >> >>> Hi, >>> We are using DSpace 6.3 and we are seeing an error when running the >>> dspace oai import -c. The Import fails with >>> "org.hibernate.exception.JDBCConnectionException: could not extract >>> ResultSet". Has anyone else encountered this problem? >>> >>> -- >>> *** >>> George Kozak >>> Digital Library Specialist >>> Cornell University Library - IT >>> 218 Olin Library >>> Cornell University >>> Ithaca, NY 14853 >>> 607-255-8924 >>> g...@cornell.edu
Re: [dspace-tech] replacing an item
Hi Jose, Referring to https://wiki.duraspace.org/display/DSDOC5x/Upgrading+DSpace#UpgradingDSpace-UpgradeSteps (point 11) starting from version 5.x the table "COMMUNITIES2ITEM" is deprecated and can be emptied. Hope this helps Riccardo On Thu, 2018-12-13 at 15:05 -0500, Jose Blanco wrote: > When I try to replace an item using this command: > ./dspace import -r -e 1 -c 123 -s some_dir -m mapfile_test_one > > It wont work because the item is mapped into a community. I kind of > want to remove this mapping using sql, but am unsure. Not really sure > why the item would be in that table. > > org.postgresql.util.PSQLException: ERROR: update or delete on table > "item" violates foreign key constraint "$2" on table > "communities2item" > > Detail: Key (item_id)=(55981) is still referenced from table > "communities2item". > -- -- Riccardo Fazio DSpace and DSpace-CRIS developer 4Science, www.4science.it (an Itway Group Company) office: UP Urban Places - Via Tiburtina, 652, 00159 Roma RM tel: +39 3339341798 -- Questo messaggio e' stato analizzato da Libra ESVA ed e' risultato non infetto. This message was scanned by Libra ESVA and is believed to be clean. -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To 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] OAI sets not showing
Dear Stan, if you look at source of the page that you provided "view-source: http://ec.msvu.ca:8080/oai/request?verb=ListSets; it seems that the data are correctly retrieved but I can see something strange with the first letter of title of the community "10587/1123" maybe you can try to fix/edit it and reindex OAI. Regards Riccardo > Greetings! > > I am running an old DSpace 4.0 and an external organization let me > know that they can't harvest our repository. I looked at DSpace OAI- > PMH Data Provider tabs and all seem to work, with the exception of > "Sets" at http://ec.msvu.ca:8080/oai/request?verb=ListSets . After > reading previous posts on a similar subject, I ran "dspace oai import > -c" and it OAI 2.0 manager imported 1324 items, but the "Sets" tab > still show nothing. What else do I need to do? > > > > > > > -- > All messages to this mailing list should adhere to the DuraSpace Code > of Conduct: https://duraspace.org/about/policies/code-of-conduct/ > --- > You received this message because you are subscribed to the Google > Groups "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, > send an email to dspace-tech+unsubscr...@googlegroups.com. > To 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. > -- -- Riccardo Fazio DSpace and DSpace-CRIS developer 4Science, www.4science.it (an Itway Group Company) office: UP Urban Places - Via Tiburtina, 652, 00159 Roma RM tel: +39 3339341798 -- Questo messaggio e' stato analizzato da Libra ESVA ed e' risultato non infetto. This message was scanned by Libra ESVA and is believed to be clean. -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To 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.
