Re: [dspace-tech] Recent-submissions homepage error in DSpace 6.3
gt;>>> at java.lang.reflect.Method.invoke(Method.java:607) >>>> > >>>> > >>>> > I followed the suggestion to run 'bin/database info' but as far as I >>>> can tell the database update checks all come back as Successful. >>>> > >>>> > I'm attaching the stack trace and database info output. >>>> > >>>> > I was curious if there were any other things I might check before >>>> passing this onto our sysadmin for further investigation into what might >>>> cause a missing virtual Site object problem? >>>> > >>>> > Thanks, >>>> > >>>> > Carl >>>> > On Wednesday, February 19, 2020 at 6:50:34 PM UTC-5 >>>> donna@canterbury.ac.nz wrote: >>>> > Hi Tim, >>>> > >>>> > >>>> > >>>> > Thanks very much for pointing us in the right direction. We think >>>> we’ve now resolved the issue by following the instructions for a post you >>>> responded to in 2015. >>>> > >>>> > >>>> > >>>> > The registry update was being ignored, and when I tried to run it >>>> separately, we were getting the error: >>>> > >>>> > >>>> > >>>> > Caused by: java.sql.BatchUpdateException: Batch entry 0 update >>>> public.bitstreamformatregistry set description=NULL, internal='FALSE', >>>> mimetype='application/vnd.openxmlformats-officedocument.wordprocessingml.document', >>>> >>>> short_description=NULL, support_level=-1 where bitstream_format_id=52 was >>>> aborted: ERROR: value too long for type character varying(48) >>>> > >>>> > >>>> > >>>> > Which led me to your 2015 reply to a post about the change of the >>>> bitstreamformatregistry table’s mimetype column switching from 48 to 256 >>>> characters in DSpace 1.5. We’ve been on DSpace since 1.4, so we’ve >>>> obviously been hauling this problem along for a while! >>>> > >>>> > >>>> > >>>> > After altering the column character length on the 5.6 database the >>>> registry update task was initially ignored, but this time when we ran >>>> [dspace]/bin/dspace database migrate ignored, it completed successfully. >>>> We >>>> now have an entry in the site table, and the recent submissions are >>>> working >>>> – yay! >>>> > >>>> > >>>> > >>>> > Hopefully there aren’t any other left-over issues that we haven’t >>>> identified, but as far as we can tell, all is well. J >>>> > >>>> > >>>> > >>>> > Thanks again, >>>> > Donna >>>> > >>>> > >>>> > >>>> > From: Tim Donohue >>>> > Sent: Wednesday, 19 February 2020 9:51 AM >>>> > To: Donna Barber ; DSpace Technical >>>> Support >>>> > Subject: Re: [dspace-tech] Recent-submissions homepage error in >>>> DSpace 6.3 >>>> > >>>> > >>>> > >>>> > Hi Donna, >>>> > >>>> > I'd recommend checking that all the Database migrations ran >>>> successfully when you upgraded to 6.3. That error seems to be returning a >>>> "null" Site object on the homepage. The Site object is a virtual object >>>> that represents your site as a whole...it's created automatically in the >>>> database in a table named "site". This error seems to imply that some >>>> portion of your database migration (which should have created that Site >>>> object) must have failed. >>>> > >>>> > So, I'd recommend looking at your logs more closely during the >>>> upgradealso, you should run "[dspace]/bin/dspace database info" to see >>>> if there are any migrations that your upgrade flagged as IGNORED (if so, >>>> you should run them, by running "./dspace database migrate ignored"). More >>>> info on these new database commands is at: >>>> > >>>> > https://wiki.lyrasis.org/display/DSDOC6x/Database+Utilities >>>> > >>>> > >>>> > >>>> > Overall, it looks to me like y
Re: [dspace-tech] Recent-submissions homepage error in DSpace 6.3
esday, February 19, 2020 at 6:50:34 PM UTC-5 >>> donna@canterbury.ac.nz wrote: >>> > Hi Tim, >>> > >>> > >>> > >>> > Thanks very much for pointing us in the right direction. We think >>> we’ve now resolved the issue by following the instructions for a post you >>> responded to in 2015. >>> > >>> > >>> > >>> > The registry update was being ignored, and when I tried to run it >>> separately, we were getting the error: >>> > >>> > >>> > >>> > Caused by: java.sql.BatchUpdateException: Batch entry 0 update >>> public.bitstreamformatregistry set description=NULL, internal='FALSE', >>> mimetype='application/vnd.openxmlformats-officedocument.wordprocessingml.document', >>> >>> short_description=NULL, support_level=-1 where bitstream_format_id=52 was >>> aborted: ERROR: value too long for type character varying(48) >>> > >>> > >>> > >>> > Which led me to your 2015 reply to a post about the change of the >>> bitstreamformatregistry table’s mimetype column switching from 48 to 256 >>> characters in DSpace 1.5. We’ve been on DSpace since 1.4, so we’ve >>> obviously been hauling this problem along for a while! >>> > >>> > >>> > >>> > After altering the column character length on the 5.6 database the >>> registry update task was initially ignored, but this time when we ran >>> [dspace]/bin/dspace database migrate ignored, it completed successfully. We >>> now have an entry in the site table, and the recent submissions are working >>> – yay! >>> > >>> > >>> > >>> > Hopefully there aren’t any other left-over issues that we haven’t >>> identified, but as far as we can tell, all is well. J >>> > >>> > >>> > >>> > Thanks again, >>> > Donna >>> > >>> > >>> > >>> > From: Tim Donohue >>> > Sent: Wednesday, 19 February 2020 9:51 AM >>> > To: Donna Barber ; DSpace Technical >>> Support >>> > Subject: Re: [dspace-tech] Recent-submissions homepage error in DSpace >>> 6.3 >>> > >>> > >>> > >>> > Hi Donna, >>> > >>> > I'd recommend checking that all the Database migrations ran >>> successfully when you upgraded to 6.3. That error seems to be returning a >>> "null" Site object on the homepage. The Site object is a virtual object >>> that represents your site as a whole...it's created automatically in the >>> database in a table named "site". This error seems to imply that some >>> portion of your database migration (which should have created that Site >>> object) must have failed. >>> > >>> > So, I'd recommend looking at your logs more closely during the >>> upgradealso, you should run "[dspace]/bin/dspace database info" to see >>> if there are any migrations that your upgrade flagged as IGNORED (if so, >>> you should run them, by running "./dspace database migrate ignored"). More >>> info on these new database commands is at: >>> > >>> > https://wiki.lyrasis.org/display/DSDOC6x/Database+Utilities >>> > >>> > >>> > >>> > Overall, it looks to me like your database upgrade didn't succeed. >>> It's hard to say exactly what happened without looking closer at the logs >>> or what the "database info" command returns. If you find an error and are >>> not sure what is happening, feel free to forward it along to this list and >>> hopefully someone here can help! >>> > >>> > >>> > >>> > Tim >>> > >>> > From: dspac...@googlegroups.com on behalf >>> of Donna Barber >>> > Sent: Sunday, February 16, 2020 7:27 PM >>> > To: DSpace Technical Support >>> > Subject: [dspace-tech] Recent-submissions homepage error in DSpace 6.3 >>> > >>> > >>> > >>> > Hi, >>> > >>> > >>> > We’re in the process of moving from 5.6 to 6.3 with everything up and >>> running in our development environment, except we’ve found that we’re now >>> getting an error trying to view the recently added list from
Re: [dspace-tech] Recent-submissions homepage error in DSpace 6.3
document.wordprocessingml.document', >> short_description=NULL, support_level=-1 where bitstream_format_id=52 was >> aborted: ERROR: value too long for type character varying(48) >> > >> > >> > >> > Which led me to your 2015 reply to a post about the change of the >> bitstreamformatregistry table’s mimetype column switching from 48 to 256 >> characters in DSpace 1.5. We’ve been on DSpace since 1.4, so we’ve >> obviously been hauling this problem along for a while! >> > >> > >> > >> > After altering the column character length on the 5.6 database the >> registry update task was initially ignored, but this time when we ran >> [dspace]/bin/dspace database migrate ignored, it completed successfully. We >> now have an entry in the site table, and the recent submissions are working >> – yay! >> > >> > >> > >> > Hopefully there aren’t any other left-over issues that we haven’t >> identified, but as far as we can tell, all is well. J >> > >> > >> > >> > Thanks again, >> > Donna >> > >> > >> > >> > From: Tim Donohue >> > Sent: Wednesday, 19 February 2020 9:51 AM >> > To: Donna Barber ; DSpace Technical >> Support >> > Subject: Re: [dspace-tech] Recent-submissions homepage error in DSpace >> 6.3 >> > >> > >> > >> > Hi Donna, >> > >> > I'd recommend checking that all the Database migrations ran >> successfully when you upgraded to 6.3. That error seems to be returning a >> "null" Site object on the homepage. The Site object is a virtual object >> that represents your site as a whole...it's created automatically in the >> database in a table named "site". This error seems to imply that some >> portion of your database migration (which should have created that Site >> object) must have failed. >> > >> > So, I'd recommend looking at your logs more closely during the >> upgradealso, you should run "[dspace]/bin/dspace database info" to see >> if there are any migrations that your upgrade flagged as IGNORED (if so, >> you should run them, by running "./dspace database migrate ignored"). More >> info on these new database commands is at: >> > >> > https://wiki.lyrasis.org/display/DSDOC6x/Database+Utilities >> > >> > >> > >> > Overall, it looks to me like your database upgrade didn't succeed. It's >> hard to say exactly what happened without looking closer at the logs or >> what the "database info" command returns. If you find an error and are not >> sure what is happening, feel free to forward it along to this list and >> hopefully someone here can help! >> > >> > >> > >> > Tim >> > >> > From: dspac...@googlegroups.com on behalf >> of Donna Barber >> > Sent: Sunday, February 16, 2020 7:27 PM >> > To: DSpace Technical Support >> > Subject: [dspace-tech] Recent-submissions homepage error in DSpace 6.3 >> > >> > >> > >> > Hi, >> > >> > >> > We’re in the process of moving from 5.6 to 6.3 with everything up and >> running in our development environment, except we’ve found that we’re now >> getting an error trying to view the recently added list from the homepage >> (/recent-submissions). However, it still works from the >> community/collection homepages. >> > >> > >> > >> > Does anyone have any idea what could be the cause? We’ve stripped out >> our customisations and switched between Mirage and Mirage2 themes, but it’s >> the same. The stack trace produced when clicking on “view more” is >> attached. >> > >> > >> > >> > Many thanks, >> > >> > >> > Donna Barber >> > >> > eServices Coordinator | Kairuruku Ratonga Tāhiko >> > >> > Library Access and Collections | Rōpū Tautāwhi >> > >> > Phone: +64 3 369 3849 extn 93849 <+64%203-369%203849> | Puaka - James >> Hight Building, Level 5, Rm 519 >> > >> > Learning Resources | University of Canterbury | Te Whare Wānanga o >> Waitaha | Private Bag 4800 | Christchurch 8140 | New Zealand >> > Website: http://www.canterbury.ac.nz/library >> > >> > -- >> > All messages to this mailing list should adhere to the DuraSpace Code >> of Conduct: https://duraspace.org/about/policies/code-of-conduct/ >> > --- >> > You re
Re: [dspace-tech] Recent-submissions homepage error in DSpace 6.3
as initially ignored, but this time when we ran > [dspace]/bin/dspace database migrate ignored, it completed successfully. We > now have an entry in the site table, and the recent submissions are working > – yay! > > > > > > > > Hopefully there aren’t any other left-over issues that we haven’t > identified, but as far as we can tell, all is well. J > > > > > > > > Thanks again, > > Donna > > > > > > > > From: Tim Donohue > > Sent: Wednesday, 19 February 2020 9:51 AM > > To: Donna Barber ; DSpace Technical Support > > > Subject: Re: [dspace-tech] Recent-submissions homepage error in DSpace > 6.3 > > > > > > > > Hi Donna, > > > > I'd recommend checking that all the Database migrations ran successfully > when you upgraded to 6.3. That error seems to be returning a "null" Site > object on the homepage. The Site object is a virtual object that represents > your site as a whole...it's created automatically in the database in a > table named "site". This error seems to imply that some portion of your > database migration (which should have created that Site object) must have > failed. > > > > So, I'd recommend looking at your logs more closely during the > upgradealso, you should run "[dspace]/bin/dspace database info" to see > if there are any migrations that your upgrade flagged as IGNORED (if so, > you should run them, by running "./dspace database migrate ignored"). More > info on these new database commands is at: > > > > https://wiki.lyrasis.org/display/DSDOC6x/Database+Utilities > > > > > > > > Overall, it looks to me like your database upgrade didn't succeed. It's > hard to say exactly what happened without looking closer at the logs or > what the "database info" command returns. If you find an error and are not > sure what is happening, feel free to forward it along to this list and > hopefully someone here can help! > > > > > > > > Tim > > > > From: dspac...@googlegroups.com on behalf > of Donna Barber > > Sent: Sunday, February 16, 2020 7:27 PM > > To: DSpace Technical Support > > Subject: [dspace-tech] Recent-submissions homepage error in DSpace 6.3 > > > > > > > > Hi, > > > > > > We’re in the process of moving from 5.6 to 6.3 with everything up and > running in our development environment, except we’ve found that we’re now > getting an error trying to view the recently added list from the homepage > (/recent-submissions). However, it still works from the > community/collection homepages. > > > > > > > > Does anyone have any idea what could be the cause? We’ve stripped out > our customisations and switched between Mirage and Mirage2 themes, but it’s > the same. The stack trace produced when clicking on “view more” is attached. > > > > > > > > Many thanks, > > > > > > Donna Barber > > > > eServices Coordinator | Kairuruku Ratonga Tāhiko > > > > Library Access and Collections | Rōpū Tautāwhi > > > > Phone: +64 3 369 3849 extn 93849 <+64%203-369%203849> | Puaka - James > Hight Building, Level 5, Rm 519 > > > > Learning Resources | University of Canterbury | Te Whare Wānanga o > Waitaha | Private Bag 4800 | Christchurch 8140 | New Zealand > > Website: http://www.canterbury.ac.nz/library > > > > -- > > 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...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/9f93b399-eeda-4245-99a9-32c64da0ce25%40googlegroups.com > . > > > > > > -- > > 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...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/78d832c5-d3f7-4307-8f59-a5beaa52d60bn%40googlegroups.com > . > > > > -- All messages to this mailing list should adhere to the 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/9e051e4d-8e2b-4dcd-acb5-475d9f128473n%40googlegroups.com.
Re: [dspace-tech] Recent-submissions homepage error in DSpace 6.3
Hi Jose, Thanks, much, for the suggestions. We’ll check those out. Carl > On Dec 7, 2020, at 6:01 PM, Jose Blanco wrote: > > I remember having this issue, and I think it was a migration that had not > run. You can check your database to make sure you have a table named site: > > => \d site > Table "public.site" > Column | Type | Modifiers > +--+--- > uuid | uuid | not null > > Indexes: > "site_pkey" PRIMARY KEY, btree (uuid) > Foreign-key constraints: > "site_uuid_fkey" FOREIGN KEY (uuid) REFERENCES dspaceobject(uuid) > > And also, In the config area take a look at this file: hibernate.cfg.xml > > You should have this in the file: > > > Hope this helps! > -Jose > > On Mon, Dec 7, 2020 at 5:11 PM Carl Jones wrote: > Hi, > > We've upgraded from 1.8 to 6.3 a couple of months ago and are experiencing a > similar error with the 'Recently Added' list when we try to hit the 'View > more' link at the site homepage. Tim Donohue mentioned this could be because > of a missing virtual Site Object that represents our system as a whole. We > get the following Stack Trace (similar to what was reported by Donna Barber > back in February of this year): > > Java stacktrace: java.lang.NullPointerException at > org.dspace.app.xmlui.aspect.discovery.recentSubmissions.RecentSubmissionTransformer.setMainTitle(RecentSubmissionTransformer.java:154) > at > org.dspace.app.xmlui.aspect.discovery.recentSubmissions.RecentSubmissionTransformer.addBody(RecentSubmissionTransformer.java:124) > at > org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:234) > at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source) at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:607) at > org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71) > at com.sun.proxy.$Proxy493.startElement(Unknown Source) at > org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87) > at > org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94) > at > org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:251) > at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source) at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:607) > > > I followed the suggestion to run 'bin/database info' but as far as I can tell > the database update checks all come back as Successful. > > I'm attaching the stack trace and database info output. > > I was curious if there were any other things I might check before passing > this onto our sysadmin for further investigation into what might cause a > missing virtual Site object problem? > > Thanks, > > Carl > On Wednesday, February 19, 2020 at 6:50:34 PM UTC-5 > donna@canterbury.ac.nz wrote: > Hi Tim, > > > > Thanks very much for pointing us in the right direction. We think we’ve now > resolved the issue by following the instructions for a post you responded to > in 2015. > > > > The registry update was being ignored, and when I tried to run it separately, > we were getting the error: > > > > Caused by: java.sql.BatchUpdateException: Batch entry 0 update > public.bitstreamformatregistry set description=NULL, internal='FALSE', > mimetype='application/vnd.openxmlformats-officedocument.wordprocessingml.document', > short_description=NULL, support_level=-1 where bitstream_format_id=52 was > aborted: ERROR: value too long for type character varying(48) > > > > Which led me to your 2015 reply to a post about the change of the > bitstreamformatregistry table’s mimetype column switching from 48 to 256 > characters in DSpace 1.5. We’ve been on DSpace since 1.4, so we’ve obviously > been hauling this problem along for a while! > > > > After altering the column character length on the 5.6 database the registry > update task was initially ignored, but this time when we ran > [dspace]/bin/dspace database migrate ignored, it completed successfully. We > now have an entry in the site table, and the recent submissions are working – > yay! > > > > Hopefully there aren’t any other left-over issues that we haven’t identified, > but as far as we can tell, all is well. J > > > > Thanks again, > Donna > > > > From: Tim Donohue > Sent: Wednesday, 19 February 2020 9:51 AM > T
Re: [dspace-tech] Recent-submissions homepage error in DSpace 6.3
I remember having this issue, and I think it was a migration that had not run. You can check your database to make sure you have a table named site: *=> \d siteTable "public.site" Column | Type | Modifiers +--+--- uuid | uuid | not nullIndexes:"site_pkey" PRIMARY KEY, btree (uuid)Foreign-key constraints:"site_uuid_fkey" FOREIGN KEY (uuid) REFERENCES dspaceobject(uuid)* And also, In the config area take a look at this file: *hibernate.cfg.xml* You should have this in the file: ** Hope this helps! -Jose On Mon, Dec 7, 2020 at 5:11 PM Carl Jones wrote: > Hi, > > We've upgraded from 1.8 to 6.3 a couple of months ago and are experiencing > a similar error with the 'Recently Added' list when we try to hit the 'View > more' link at the site homepage. Tim Donohue mentioned this could be > because of a missing virtual Site Object that represents our system as a > whole. We get the following Stack Trace (similar to what was reported by > Donna Barber back in February of this year): > > Java stacktrace: java.lang.NullPointerException at > org.dspace.app.xmlui.aspect.discovery.recentSubmissions.RecentSubmissionTransformer.setMainTitle(RecentSubmissionTransformer.java:154) > at > org.dspace.app.xmlui.aspect.discovery.recentSubmissions.RecentSubmissionTransformer.addBody(RecentSubmissionTransformer.java:124) > at > org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:234) > at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source) at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:607) at > org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71) > at com.sun.proxy.$Proxy493.startElement(Unknown Source) at > org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87) > at > org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94) > at > org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:251) > at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source) at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:607) > > > I followed the suggestion to run 'bin/database info' but as far as I can > tell the database update checks all come back as Successful. > > I'm attaching the stack trace and database info output. > > I was curious if there were any other things I might check before passing > this onto our sysadmin for further investigation into what might cause a > missing virtual Site object problem? > > Thanks, > > Carl > On Wednesday, February 19, 2020 at 6:50:34 PM UTC-5 > donna@canterbury.ac.nz wrote: > >> Hi Tim, >> >> >> >> Thanks very much for pointing us in the right direction. We think we’ve >> now resolved the issue by following the instructions for a post you >> responded to in 2015. >> >> >> >> The registry update was being ignored, and when I tried to run it >> separately, we were getting the error: >> >> >> >> Caused by: java.sql.BatchUpdateException: Batch entry 0 update >> public.bitstreamformatregistry set description=NULL, internal='FALSE', >> mimetype='application/vnd.openxmlformats-officedocument.wordprocessingml.document', >> short_description=NULL, support_level=-1 where bitstream_format_id=52 was >> aborted: ERROR: value too long for type character varying(48) >> >> >> >> Which led me to your 2015 reply to a post about the change of the >> bitstreamformatregistry table’s mimetype column switching from 48 to 256 >> characters in DSpace 1.5. We’ve been on DSpace since 1.4, so we’ve >> obviously been hauling this problem along for a while! >> >> >> >> After altering the column character length on the 5.6 database the >> registry update task was initially ignored, but this time when we ran >> [dspace]/bin/dspace database migrate ignored, it completed successfully. We >> now have an entry in the site table, and the recent submissions are working >> – yay! >> >> >> >> Hopefully there aren’t any other left-over issues that we haven’t >> identified, but as far as we can tell, all is well. J >> >> >> >> Thanks again, >> Donna >> >> >> >> *From:* Tim Donohue >> *Sent:* Wednesday, 19 February 2020 9:51 AM >> *To:* Donna Barber ; DSpace Technical >> Support >> *Subject:* Re: [dspace-tech] Recent-submissions homepage err
RE: [dspace-tech] Recent-submissions homepage error in DSpace 6.3
Hi Tim, Thanks very much for pointing us in the right direction. We think we’ve now resolved the issue by following the instructions for a post you responded to in 2015. The registry update was being ignored, and when I tried to run it separately, we were getting the error: Caused by: java.sql.BatchUpdateException: Batch entry 0 update public.bitstreamformatregistry set description=NULL, internal='FALSE', mimetype='application/vnd.openxmlformats-officedocument.wordprocessingml.document', short_description=NULL, support_level=-1 where bitstream_format_id=52 was aborted: ERROR: value too long for type character varying(48) Which led me to your 2015 reply to a post about the change of the bitstreamformatregistry table’s mimetype column switching from 48 to 256 characters in DSpace 1.5. We’ve been on DSpace since 1.4, so we’ve obviously been hauling this problem along for a while! After altering the column character length on the 5.6 database the registry update task was initially ignored, but this time when we ran [dspace]/bin/dspace database migrate ignored, it completed successfully. We now have an entry in the site table, and the recent submissions are working – yay! Hopefully there aren’t any other left-over issues that we haven’t identified, but as far as we can tell, all is well. :) Thanks again, Donna From: Tim Donohue Sent: Wednesday, 19 February 2020 9:51 AM To: Donna Barber ; DSpace Technical Support Subject: Re: [dspace-tech] Recent-submissions homepage error in DSpace 6.3 Hi Donna, I'd recommend checking that all the Database migrations ran successfully when you upgraded to 6.3. That error seems to be returning a "null" Site object on the homepage. The Site object is a virtual object that represents your site as a whole...it's created automatically in the database in a table named "site". This error seems to imply that some portion of your database migration (which should have created that Site object) must have failed. So, I'd recommend looking at your logs more closely during the upgradealso, you should run "[dspace]/bin/dspace database info" to see if there are any migrations that your upgrade flagged as IGNORED (if so, you should run them, by running "./dspace database migrate ignored"). More info on these new database commands is at: https://wiki.lyrasis.org/display/DSDOC6x/Database+Utilities Overall, it looks to me like your database upgrade didn't succeed. It's hard to say exactly what happened without looking closer at the logs or what the "database info" command returns. If you find an error and are not sure what is happening, feel free to forward it along to this list and hopefully someone here can help! Tim From: dspace-tech@googlegroups.com<mailto:dspace-tech@googlegroups.com> mailto:dspace-tech@googlegroups.com>> on behalf of Donna Barber mailto:donna.bar...@canterbury.ac.nz>> Sent: Sunday, February 16, 2020 7:27 PM To: DSpace Technical Support mailto:dspace-tech@googlegroups.com>> Subject: [dspace-tech] Recent-submissions homepage error in DSpace 6.3 Hi, We’re in the process of moving from 5.6 to 6.3 with everything up and running in our development environment, except we’ve found that we’re now getting an error trying to view the recently added list from the homepage (/recent-submissions). However, it still works from the community/collection homepages. Does anyone have any idea what could be the cause? We’ve stripped out our customisations and switched between Mirage and Mirage2 themes, but it’s the same. The stack trace produced when clicking on “view more” is attached. Many thanks, Donna Barber eServices Coordinator | Kairuruku Ratonga Tāhiko Library Access and Collections | Rōpū Tautāwhi Phone: +64 3 369 3849 extn 93849 | Puaka - James Hight Building, Level 5, Rm 519 Learning Resources | University of Canterbury | Te Whare Wānanga o Waitaha | Private Bag 4800 | Christchurch 8140 | New Zealand Website: http://www.canterbury.ac.nz/library -- 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<mailto:dspace-tech+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/9f93b399-eeda-4245-99a9-32c64da0ce25%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/9f93b399-eeda-4245-99a9-32c64da0ce25%40googlegroups.com?utm_medium=email_source=footer>. -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ -
Re: [dspace-tech] Recent-submissions homepage error in DSpace 6.3
Hi Donna, I'd recommend checking that all the Database migrations ran successfully when you upgraded to 6.3. That error seems to be returning a "null" Site object on the homepage. The Site object is a virtual object that represents your site as a whole...it's created automatically in the database in a table named "site". This error seems to imply that some portion of your database migration (which should have created that Site object) must have failed. So, I'd recommend looking at your logs more closely during the upgradealso, you should run "[dspace]/bin/dspace database info" to see if there are any migrations that your upgrade flagged as IGNORED (if so, you should run them, by running "./dspace database migrate ignored"). More info on these new database commands is at: https://wiki.lyrasis.org/display/DSDOC6x/Database+Utilities Overall, it looks to me like your database upgrade didn't succeed. It's hard to say exactly what happened without looking closer at the logs or what the "database info" command returns. If you find an error and are not sure what is happening, feel free to forward it along to this list and hopefully someone here can help! Tim From: dspace-tech@googlegroups.com on behalf of Donna Barber Sent: Sunday, February 16, 2020 7:27 PM To: DSpace Technical Support Subject: [dspace-tech] Recent-submissions homepage error in DSpace 6.3 Hi, We’re in the process of moving from 5.6 to 6.3 with everything up and running in our development environment, except we’ve found that we’re now getting an error trying to view the recently added list from the homepage (/recent-submissions). However, it still works from the community/collection homepages. Does anyone have any idea what could be the cause? We’ve stripped out our customisations and switched between Mirage and Mirage2 themes, but it’s the same. The stack trace produced when clicking on “view more” is attached. Many thanks, Donna Barber eServices Coordinator | Kairuruku Ratonga Tāhiko Library Access and Collections | Rōpū Tautāwhi Phone: +64 3 369 3849 extn 93849 | Puaka - James Hight Building, Level 5, Rm 519 Learning Resources | University of Canterbury | Te Whare Wānanga o Waitaha | Private Bag 4800 | Christchurch 8140 | New Zealand Website: http://www.canterbury.ac.nz/library -- 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<mailto:dspace-tech+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/9f93b399-eeda-4245-99a9-32c64da0ce25%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/9f93b399-eeda-4245-99a9-32c64da0ce25%40googlegroups.com?utm_medium=email_source=footer>. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/DM5PR2201MB11485706F6DB21E1798C0D93ED110%40DM5PR2201MB1148.namprd22.prod.outlook.com.
[dspace-tech] Recent-submissions homepage error in DSpace 6.3
Hi, We’re in the process of moving from 5.6 to 6.3 with everything up and running in our development environment, except we’ve found that we’re now getting an error trying to view the recently added list from the homepage (/recent-submissions). However, it still works from the community/collection homepages. Does anyone have any idea what could be the cause? We’ve stripped out our customisations and switched between Mirage and Mirage2 themes, but it’s the same. The stack trace produced when clicking on “view more” is attached. Many thanks, Donna Barber eServices Coordinator | Kairuruku Ratonga Tāhiko Library Access and Collections | Rōpū Tautāwhi Phone: +64 3 369 3849 extn 93849 | Puaka - James Hight Building, Level 5, Rm 519 Learning Resources | University of Canterbury | Te Whare Wānanga o Waitaha | Private Bag 4800 | Christchurch 8140 | New Zealand Website*:* http://www.canterbury.ac.nz/library -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/9f93b399-eeda-4245-99a9-32c64da0ce25%40googlegroups.com. Java stacktrace: java.lang.NullPointerException at org.dspace.app.xmlui.aspect.discovery.recentSubmissions.RecentSubmissionTransformer.setMainTitle(RecentSubmissionTransformer.java:154) at org.dspace.app.xmlui.aspect.discovery.recentSubmissions.RecentSubmissionTransformer.addBody(RecentSubmissionTransformer.java:124) at org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:234) at sun.reflect.GeneratedMethodAccessor145.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71) at com.sun.proxy.$Proxy275.startElement(Unknown Source) at org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87) at org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94) at org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:251) at sun.reflect.GeneratedMethodAccessor145.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71) at com.sun.proxy.$Proxy276.startElement(Unknown Source) at org.apache.cocoon.environment.internal.EnvironmentChanger.startElement(EnvironmentStack.java:140) at org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87) at org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94) at org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:251) at sun.reflect.GeneratedMethodAccessor145.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71) at com.sun.proxy.$Proxy276.startElement(Unknown Source) at org.apache.cocoon.environment.internal.EnvironmentChanger.startElement(EnvironmentStack.java:140) at org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87) at org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94) at org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:251) at sun.reflect.GeneratedMethodAccessor145.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71) at com.sun.proxy.$Proxy276.startElement(Unknown Source) at org.apache.cocoon.environment.internal.EnvironmentChanger.startElement(EnvironmentStack.java:140) at org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87) at org.apache.cocoon.components.sax.AbstractXMLByteStreamInterpreter.parse(AbstractXMLByteStreamInterpreter.java:117) at
