On Mon, Feb 08, 2021 at 12:16:10AM -0800, Dayal singh tutorial wrote:
> the Dspace 6 is running good and without any problem. but after  login all 
> user expect admin got internal system error. this email got in admin mail- 
> An internal server error occurred on http://192.168.1.158:8080/jspui:
> 
> Date:       8/2/21 1:37 PM
> Session ID: B7748B699118F9761E5780DA74BE3F22
> User:       Manish Bishnoi ([email protected])
> IP address: 192.168.1.94
> 
> -- URL Was: http://192.168.1.158:8080/jspui/internal-error
> -- Method: GET
> -- Parameters were:
> 
> 
> Exception:
> org.apache.jasper.JasperException: javax.servlet.ServletException: 
> org.dspace.plugin.PluginException: 
> org.dspace.app.webui.components.RecentSubmissionsException: 
> org.dspace.browse.BrowseException: 
> org.dspace.discovery.SearchServiceException: Expected mime type 
> application/octet-stream but got text/html. <!doctype html><html 

"Expected mime type application/octet-stream but got text/html" often
means a problem with DSpace querying Solr.  Follow the chain of
"Caused by" to the bottom and we find an
HttpSolrServer$RemoteSolrException with a number of
org.apache.solr.client.solrj classes in its stack trace, which
confirms my suspicion.

The first thing I would check is whether DSpace's 'solr.server'
configuration is set correctly.  I would give particular attention to
the protocol (http: or https:) since the message complains "request
header is too large".

> lang="en"><head><title>HTTP Status 400 – Bad Request</title><style 
> type="text/css">h1 
> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
>  
> h2 
> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
>  
> h3 
> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
>  
> body 
> {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} b 
> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} 
> p 
> {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}
>  
> a {color:black;} a.name {color:black;} .line 
> {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP
>  
> Status 400 – Bad Request</h1><hr class="line" /><p><b>Type</b> Exception 
> Report</p><p><b>Message</b> Request header is too 
> large</p><p><b>Description</b> The server cannot or will not process the 
> request due to something that is perceived to be a client error (e.g., 
> malformed request syntax, invalid request message framing, or deceptive 
> request 
> routing).</p><p><b>Exception</b></p><pre>java.lang.IllegalArgumentException: 
> Request header is too large
>         
[...]

> Caused by: 
> org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: 
> Expected mime type application/octet-stream but got text/html. <!doctype 
> html><html lang="en"><head><title>HTTP Status 400 – Bad 
> Request</title><style type="text/css">h1 
> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
>  
> h2 
> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
>  
> h3 
> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
>  
> body 
> {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} b 
> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} 
> p 
> {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}
>  
> a {color:black;} a.name {color:black;} .line 
> {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP
>  
> Status 400 – Bad Request</h1><hr class="line" /><p><b>Type</b> Exception 
> Report</p><p><b>Message</b> Request header is too 
> large</p><p><b>Description</b> The server cannot or will not process the 
> request due to something that is perceived to be a client error (e.g., 
> malformed request syntax, invalid request message framing, or deceptive 
> request 
> routing).</p><p><b>Exception</b></p><pre>java.lang.IllegalArgumentException: 
> Request header is too large
>         
> org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:720)
>         
> org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:462)
>         
> org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:684)
>         
> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
>         
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:806)
>         org.apache.tomcat.util.net
> .NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
>         org.apache.tomcat.util.net
> .SocketProcessorBase.run(SocketProcessorBase.java:49)
>         
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>         
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>         
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>         java.lang.Thread.run(Thread.java:748)
> </pre><p><b>Note</b> The full stack trace of the root cause is available in 
> the server logs.</p><hr class="line" /><h3>Apache Tomcat/8.5.39 
> (Ubuntu)</h3></body></html>
>         at 
> org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:512)
>         at 
> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:210)
>         at 
> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:206)
>         at 
> org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:91)
>         at 
> org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:301)
>         at 
> org.dspace.discovery.SolrServiceImpl.search(SolrServiceImpl.java:1610)
>         ... 37 more

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

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/YCFlzaekCPLf/it5%40IUPUI.Edu.

Attachment: signature.asc
Description: PGP signature

Reply via email to