[
https://issues.apache.org/jira/browse/SOLR-16327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17578577#comment-17578577
]
Shawn Heisey edited comment on SOLR-16327 at 8/11/22 5:51 PM:
--------------------------------------------------------------
I copied the whole solrconfig.xml file over to the 8.11.1 install. It still
works as expected in standalone mode.
Here's the solrconfig.xml that results in the permission error on
9.1.0-SNAPSHOT, standalone mode:
{code:xml}
<?xml version="1.0" encoding="UTF-8" ?>
<config>
<luceneMatchVersion>LATEST</luceneMatchVersion>
<updateHandler class="solr.DirectUpdateHandler2">
<updateLog>
<int name="numVersionBuckets">65536</int>
</updateLog>
<autoCommit>
<maxTime>60000</maxTime>
<openSearcher>true</openSearcher>
</autoCommit>
<autoSoftCommit>
<maxTime>-1</maxTime>
</autoSoftCommit>
</updateHandler>
<indexConfig>
<ramBufferSizeMB>128</ramBufferSizeMB>
</indexConfig>
<updateRequestProcessorChain name="default" default="true">
<processor class="solr.TrimFieldUpdateProcessorFactory"/>
<processor class="solr.LogUpdateProcessorFactory"/>
<processor class="solr.DistributedUpdateProcessorFactory"/>
<processor class="solr.RunUpdateProcessorFactory"/>
</updateRequestProcessorChain>
<query>
<filterCache size="128"
initialSize="64"
autowarmCount="32"/>
<queryResultCache size="512"
initialSize="512"
autowarmCount="64"/>
<documentCache
size="512"
initialSize="512"
autowarmCount="0"/>
<enableLazyFieldLoading>true</enableLazyFieldLoading>
<queryResultWindowSize>200</queryResultWindowSize>
<queryResultMaxDocsCached>2000</queryResultMaxDocsCached>
<useColdSearcher>false</useColdSearcher>
</query>
<requestDispatcher>
<httpCaching never304="true" />
</requestDispatcher>
<requestHandler name="/select" class="solr.SearchHandler">
<lst name="defaults">
<!--
<str name="defType">edismax</str>
<str name="qf">body to subject cc from</str>
-->
<str name="echoParams">all</str>
<int name="rows">10</int>
</lst>
</requestHandler>
<requestHandler name="/admin/ping" class="solr.PingRequestHandler">
<!-- relative paths are resolved against the data dir -->
<str name="healthcheckFile">server-enabled.txt</str>
<lst name="invariants">
<str name="qt">/select</str><!-- handler to delegate to -->
<!--
<str name="defType">edismax</str>
<str name="qf">body to subject cc from</str>
-->
<str name="q">mail</str>
<str name="rows">1</str>
</lst>
</requestHandler>
<queryResponseWriter name="xml"
default="true"
class="solr.XMLResponseWriter" />
</config>
{code}
bq. I know I am a broken record, but we should just always use cloud mode
It will take me a little bit of time to convert my install to cloud mode. I do
not often deal with it. Can you tell me what the changes are to
/etc/default/solr.in.sh to start and use an embedded zk? I know what to do for
an external zk, but not for the embedded one.
was (Author: elyograg):
I copied the whole solrconfig.xml file over to the 8.11.1 install. It still
works as expected in standalone mode.
Here's the solrconfig.xml that results in the permission error on
9.1.0-SNAPSHOT, standalone mode:
{code:xml}
<?xml version="1.0" encoding="UTF-8" ?>
<config>
<luceneMatchVersion>LATEST</luceneMatchVersion>
<updateHandler class="solr.DirectUpdateHandler2">
<updateLog>
<int name="numVersionBuckets">65536</int>
</updateLog>
<autoCommit>
<maxTime>60000</maxTime>
<openSearcher>true</openSearcher>
</autoCommit>
<autoSoftCommit>
<maxTime>-1</maxTime>
</autoSoftCommit>
</updateHandler>
<indexConfig>
<ramBufferSizeMB>128</ramBufferSizeMB>
</indexConfig>
<updateRequestProcessorChain name="default" default="true">
<processor class="solr.TrimFieldUpdateProcessorFactory"/>
<processor class="solr.LogUpdateProcessorFactory"/>
<processor class="solr.DistributedUpdateProcessorFactory"/>
<processor class="solr.RunUpdateProcessorFactory"/>
</updateRequestProcessorChain>
<query>
<filterCache size="128"
initialSize="64"
autowarmCount="32"/>
<queryResultCache size="512"
initialSize="512"
autowarmCount="64"/>
<documentCache
size="512"
initialSize="512"
autowarmCount="0"/>
<enableLazyFieldLoading>true</enableLazyFieldLoading>
<queryResultWindowSize>200</queryResultWindowSize>
<queryResultMaxDocsCached>2000</queryResultMaxDocsCached>
<useColdSearcher>false</useColdSearcher>
</query>
<requestDispatcher>
<httpCaching never304="true" />
</requestDispatcher>
<requestHandler name="/select" class="solr.SearchHandler">
<lst name="defaults">
<!--
<str name="defType">edismax</str>
<str name="qf">body to subject cc from</str>
-->
<str name="echoParams">all</str>
<int name="rows">10</int>
</lst>
</requestHandler>
<requestHandler name="/admin/ping" class="solr.PingRequestHandler">
<!-- relative paths are resolved against the data dir -->
<str name="healthcheckFile">server-enabled.txt</str>
<lst name="invariants">
<str name="qt">/select</str><!-- handler to delegate to -->
<!--
<str name="defType">edismax</str>
<str name="qf">body to subject cc from</str>
-->
<str name="q">mail</str>
<str name="rows">1</str>
</lst>
</requestHandler>
<queryResponseWriter name="xml"
default="true"
class="solr.XMLResponseWriter" />
</config>
{code}
bq. I know I am a broken record, but we should just always use cloud mode
It will take me a little bit of time to convert my install to cloud mode. I do
not often deal with it. Can you tell me what the changes are to
/etc/default/solr.in.sh to start and use an embedded zk? I know what to do for
an external zk, but not for the embedded one.
> Admin UI reports permission error if the request it made results in ANY
> exception
> ---------------------------------------------------------------------------------
>
> Key: SOLR-16327
> URL: https://issues.apache.org/jira/browse/SOLR-16327
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Admin UI
> Affects Versions: main (10.0)
> Reporter: Shawn Heisey
> Priority: Minor
> Attachments: image-2022-08-06-15-36-24-158.png, screenshot-1.png,
> solr9_ping_exception.txt
>
>
> A lot of the pages in the UI report permission errors even when the actual
> problem is some other exception. For this screenshot, I clicked first on the
> Overview, and then on Ping ... there was a misconfig in the ping handler
> where it was not declaring a default field, so the query generated an
> exception which is attached to the issue. I did not have a security.json
> file.
> !image-2022-08-06-15-36-24-158.png|width=389,height=182!
> I also saw this on other things besides Ping when I was clicking around the
> admin UI during a solr service restart. The version info showing where the
> git repo was when I compiled from branch_9x:
> 9.1.0-SNAPSHOT f1510b1f54ea9225df654e3aad0ca7da856c1f72 [snapshot build,
> details omitted]
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
