dspace 6.3 problem loading items on mirage 2 theme
242 views
Skip to first unread message
Massimiliano CILURZO
Jul 26, 2019, 9:45:34 AM7/26/19
to DSpace Technical Support
Dear All,
We have a Dspace 6.3 server. We hava upgraded the system from 5.6.
We are using mirage 2 as theme.
Now we have a problem when we try to load items only on some collection.
Especially collections with large pdf (100 MB or more) and a lot of image (400 or more).
The system give us this error:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
It seems as the system goes in time out.
Do you have some suggestions?
We have modified our dspace.cfg putting
xmlui.theme.mirage.item-list.emphasis = file
webui.browse.thumbnail.show = false
webui.preview.enabled = false
xmlui.community-list.render.full = false
Thanks
Best regards
Massimiliano
Mark H. Wood
Jul 26, 2019, 10:20:18 AM7/26/19
to DSpace Technical Support
On Fri, Jul 26, 2019 at 06:45:34AM -0700, Massimiliano CILURZO wrote:
> Internal Server Error
>
> The server encountered an internal error or misconfiguration and was unable
> to complete your request.
>
> Please contact the server administrator at root@localhost to inform them of
> the time this error occurred, and the actions you performed just before
> this error.
>
> More information about this error may be available in the server error log.
If you see this message, and you *are* the server administrator, then
> Internal Server Error
>
> The server encountered an internal error or misconfiguration and was unable
> to complete your request.
>
> Please contact the server administrator at root@localhost to inform them of
> the time this error occurred, and the actions you performed just before
> this error.
>
> More information about this error may be available in the server error log.
the first thing to do (as hinted in the last line) is to inspect the
logs around the time of the error. If the cause of the problem is not
clear from the logs, please post the relevant portions here. It is
better to provide too much context, than too little.
--
Mark H. Wood
Lead Technology Analyst
University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu
Massimiliano CILURZO
Jul 29, 2019, 3:31:54 AM7/29/19
to DSpace Technical Support
Dear Mark,
I have seen all the logs but the cause of the problem is not
clear.
clear.
The system now give this error:
Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
This is the cocoon.log
2019-07-29 09:09:41,843 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/9/handle/10556/2949?pipelinehash=4400125204872469117_T-Navigation-2179865478699912566_T-ItemViewer-983520235286152229
2019-07-29 09:09:43,523 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache HIT for PK_G-aspect-cocoon://DRI/8/handle/10556/2949?pipelinehash=-4626015561481666846_T-Navigation-5728138339744327642
2019-07-29 09:09:43,525 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache HIT for PK_G-aspect-cocoon://DRI/7/handle/10556/2949?pipelinehash=4118340052035854956_T-Navigation-5728138339744327642
2019-07-29 09:09:43,525 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/6/handle/10556/2949_T-SystemwideAlerts-1_T-Navigation--5367372201529954577
2019-07-29 09:09:43,525 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/5/handle/10556/2949_T-Navigation--5255526706584267476
2019-07-29 09:09:43,525 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/4/handle/10556/2949
2019-07-29 09:09:43,525 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/3/handle/10556/2949
2019-07-29 09:09:43,525 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/2/handle/10556/2949
2019-07-29 09:09:43,525 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/1/handle/10556/2949
2019-07-29 09:09:43,528 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-file-cocoon://DRI/handle/10556/2949_T-xslt-file:///usr/local/src/apache-tomcat-9.0.20/webapps/xmlui/themes/Mirage2/xsl/preprocess.xsl_T-IncludePageMeta--2183294294163301955_T-xslt-file:///usr/local/src/apache-tomcat-9.0.20/webapps/xmlui/themes/Mirage2/xsl/theme.xsl_T-i18n-context://i18n/?it___T-strip-namespaces-1_S-html-no-doctype-;encoding=UTF-8;indent=yes
2019-07-29 09:09:43,714 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache HIT for PK_R-ThemeResourceReader-file:///usr/local/src/apache-tomcat-9.0.20/webapps/xmlui/themes/Mirage2/scripts-dist.xml
2019-07-29 09:09:43,716 WARN cocoon.access - org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe
2019-07-29 09:09:43,716 INFO cocoon.access - 'handle/10556/2949' Processed by Apache Cocoon in 2.7382834 minutes.
2019-07-29 09:09:45,528 INFO cocoon.access - 'bitstream/handle/10556/1015/tesi A. Marandino.pdf' Processed by Apache Cocoon in 239 milliseconds.
2019-07-29 09:09:54,217 INFO org.apache.cocoon.components.treeprocessor.sitemap.RedirectToURINode - Redirecting to '/bitstream/handle/10556/1014/abstract in italiano e inglese D. Marra.pdf?sequence=2' at <map:redirect-to> - file:///usr/local/src/apache-tomcat-9.0.20/webapps/xmlui/sitemap.xmap:369:137
2019-07-29 09:09:54,218 INFO org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor$TreeProcessorRedirector - Redirecting to '/bitstream/handle/10556/1014/abstract in italiano e inglese D. Marra.pdf?sequence=2'
2019-07-29 09:09:54,218 INFO cocoon.access - 'bitstream/10556/1014/2/abstract in italiano e inglese D. Marra.pdf' Processed by Apache Cocoon in 1 milliseconds.
2019-07-29 09:10:16,829 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache HIT for PK_G-file-file:///usr/local/src/apache-tomcat-9.0.20/webapps/xmlui/aspects/protodocument.xml
2019-07-29 09:10:16,830 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache MISS for PK_G-aspect-cocoon://DRI/9/handle/10556/974?pipelinehash=4400125204872469117_T-Navigation--3826449426891179088_T-ItemViewer-4920697739924254990
2019-07-29 09:10:16,979 INFO org.apache.cocoon.caching.impl.CacheImpl - Caching new response for PK_G-aspect-cocoon://DRI/8/handle/10556/974?pipelinehash=726219467082772024_T-Navigation--7644061660383790846
2019-07-29 09:10:16,980 INFO org.apache.cocoon.caching.impl.CacheImpl - Caching new response for PK_G-aspect-cocoon://DRI/7/handle/10556/974?pipelinehash=-7886039018503951890_T-Navigation--7644061660383790846
2019-07-29 09:10:16,988 INFO cocoon.access - 'handle/10556/974' Processed by Apache Cocoon in 187 milliseconds.
2019-07-29 09:10:38,391 INFO org.apache.cocoon.caching.impl.CacheImpl - Cache HIT for PK_R-ThemeResourceReader-file:///usr/local/src/apache-tomcat-9.0.20/webapps/xmlui/themes/Mirage2/scripts-dist.xml
2019-07-29 09:10:38,394 WARN cocoon.access - org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe
2019-07-29 09:10:38,394 INFO cocoon.access - 'handle/10556/2949' Processed by Apache Cocoon in 2.8829834 minutes.
This the dspace.log
2019-07-29 09:27:50,178 INFO org.dspace.statistics.SolrLoggerServiceImpl @ Failed DNS Lookup for IP:172.16.7.4
2019-07-29 09:27:50,178 ERROR org.dspace.statistics.SolrLoggerServiceImpl @ Unable to get location of request: The address 172.16.7.4 is not in the database.
This error happen only on the xmlui (mirage2 theme) if i try to see the same item on the jspui there is no problem.
Do you have some suggestions?
Thanks
Best regards
Massimiliano
Massimiliano CILURZO
Sep 4, 2019, 1:38:29 PM9/4/19
to DSpace Technical Support
Someone have some suggestion for this problem?
We had deleted some collection and rebuilt it.
But some collections are too large and appears as inaccessible with xmlui mirage2.
With Jspui there are no problem.
Thanks
Best regards
Massimiliano
Tim Donohue
Sep 4, 2019, 4:06:48 PM9/4/19
to Massimiliano CILURZO, DSpace Technical Support
Hello Massimiliano,
If the site is crashing on large collections, it's most likely some form of "out of memory error" being thrown by Tomcat (you'd want to check the Tomcat logs, as this level of error may not appear in the DSpace logs). My best guess is you might want to consider giving your site more memory, see https://wiki.duraspace.org/display/DSDOC6x/Performance+Tuning+DSpace
If the site is crashing on large collections, it's most likely some form of "out of memory error" being thrown by Tomcat (you'd want to check the Tomcat logs, as this level of error may not appear in the DSpace logs). My best guess is you might want to consider giving your site more memory, see https://wiki.duraspace.org/display/DSDOC6x/Performance+Tuning+DSpace
That said, this is only a guess, as you didn't provide any information about how much memory you are currently allocating to Tomcat. Additionally, as Mark noted, you should look closely at your log files. Both of the messages you sent to this list are being
reported by *Tomcat* (not DSpace). When Tomcat crashes like this, you will almost always see errors reported in the Tomcat logs which provide better clues around what the problem may be.
Tim
From: dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf of Massimiliano CILURZO <mcil...@unisa.it>
Sent: Wednesday, September 4, 2019 12:38 PM
To: DSpace Technical Support <dspac...@googlegroups.com>
Subject: [dspace-tech] Re: dspace 6.3 problem loading items on mirage 2 theme
Sent: Wednesday, September 4, 2019 12:38 PM
To: DSpace Technical Support <dspac...@googlegroups.com>
Subject: [dspace-tech] Re: dspace 6.3 problem loading items on mirage 2 theme
--
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/56c90acf-79c3-4bf1-aaf9-55d7ae95e461%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/56c90acf-79c3-4bf1-aaf9-55d7ae95e461%40googlegroups.com.
Massimiliano CILURZO
Sep 10, 2019, 7:39:35 AM9/10/19
to DSpace Technical Support
Dear Tim,
Which logs in particular I have to watch?
The problem happen only for mirage 2, in jspui we haven't this problem.
For the memory we have 10 GB of RAM on that machine.
It seems very strange this error because for dspace 5.6 we hadn't this problem.
If we use the original mirage 2 of dspace 6.3 we have this problem with some collection. if we put the mirage2 theme used on dspace 5.6 we have even some community that goes in error.
Thanks
Best regards
Massimiliano
To unsubscribe from this group and stop receiving emails from it, send an email to dspac...@googlegroups.com.
Tim Donohue
Sep 16, 2019, 4:31:24 PM9/16/19
to Massimiliano CILURZO, DSpace Technical Support
Hello Massimiliano,
As noted previously, you should look at the Tomcat Logs whenever the errors displayed are coming from Tomcat (and not DSpace). It's still possible that DSpace is causing the error, but Tomcat's logs will contain the detailed error message (as it is where the failure occurred).
As noted previously, you should look at the Tomcat Logs whenever the errors displayed are coming from Tomcat (and not DSpace). It's still possible that DSpace is causing the error, but Tomcat's logs will contain the detailed error message (as it is where the failure occurred).
Depending on your operating system, the Tomcat logs may be under "/var/log/tomcat" or "/var/lib/tomcat/logs" or simply in a "logs" folder wherever you have installed Tomcat.
Tim
From: dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf of Massimiliano CILURZO <mcil...@unisa.it>
Sent: Tuesday, September 10, 2019 6:39 AM
Subject: Re: [dspace-tech] Re: dspace 6.3 problem loading items on mirage 2 theme
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/668a60e1-792a-4c76-8b71-68289c0c5443%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/668a60e1-792a-4c76-8b71-68289c0c5443%40googlegroups.com.
Massimiliano CILURZO
Sep 17, 2019, 4:01:06 AM9/17/19
to DSpace Technical Support
Dear Tim,
I have seen that in the log directory of tomcat the only file that is modified is localhost_access_log
66.249.64.8 - - [17/Sep/2019:09:51:44 +0200] "GET /xmlui/themes/Mirage2/vendor/BookReader/BookReaderJSSimple.js HTTP/1.1" 404 16300
66.249.64.8 - - [17/Sep/2019:09:51:45 +0200] "GET /xmlui/themes/Mirage2/vendor/BookReader/jquery.ui.ipad.js HTTP/1.1" 404 16288
66.249.64.10 - - [17/Sep/2019:09:51:46 +0200] "GET /xmlui/themes/Mirage2/vendor/BookReader/dragscrollable.js HTTP/1.1" 404 16288
66.249.64.10 - - [17/Sep/2019:09:51:47 +0200] "GET /xmlui/themes/Mirage2/vendor/BookReader/jquery-ui-1.8.5.custom.min.js HTTP/1.1" 404 16244
66.249.64.10 - - [17/Sep/2019:09:51:48 +0200] "GET /xmlui/themes/Mirage2/vendor/BookReader/BookReader.js HTTP/1.1" 404 16196
66.249.64.10 - - [17/Sep/2019:09:51:49 +0200] "GET /xmlui/themes/Mirage2/vendor/BookReader/jquery-ui-1.8.5.custom.min.js HTTP/1.1" 404 16244
127.0.0.1 - - [17/Sep/2019:09:52:11 +0200] "POST /solr/statistics/update?wt=javabin&version=2 HTTP/1.1" 200 40
127.0.0.1 - - [17/Sep/2019:09:52:13 +0200] "POST /solr/search/select HTTP/1.1" 200 449
Th cocoon.log is this
2019-09-17 09:47:33,209 WARN cocoon.access - org.apache.catalina.connector.ClientAbortException: java.io.IOException: Pipe interrotta
2019-09-17 09:47:33,209 INFO cocoon.access - 'handle/10556/2949' Processed by Apache Cocoon in 2.0272 minutes.
As if the system goes in timeout the answer is "Service Unavailable" The server is temporaly unable to service your request due to maintance downtime or capacity problems. Please try again later.
I have followed even this https://github.com/DSpace/DSpace/pull/2130 but nothing change.
And if I put log4j.proprieties in "DEBUG" I have this error:
unknown protocol resource.
Thanks
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/668a60e1-792a-4c76-8b71-68289c0c5443%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages