On 5/24/22 06:17, Deeksha Shrivastava wrote:
Solr set up was done long time back. Currently Solr is deployed on our QA and
PROD servers, and our website's search functionality is working fine as of now.
The Solr version installed is 7.2.1, previously java/jre was not installed but
we did the installation of JRE 8 on the server.
As per our understanding, no major changes were made in the script included
with Solr. We are attaching solr.in.cmd file for your reference.
Attaching the solr.in.cmd and solr.log file.
Please do let us know if we can provide any other configuration file for
further reference.\
The attachment you sent hit my scanner and got quarantined because it
included an executable file -- solr.in.cmd. It appears that the message
never made it to the mailing list at all, likely because the zipfile
includes a banned type of file. I released the message from quarantine
on my server so I could read it. Attachments sent to the mailing list
almost never work -- I only got it because you sent the message directly
to me as well as the list.
It appears that you really do actually have the string "etc." configured
on the GC_TUNE variable in solr.in.cmd. That's not going to work, and
probably would cause Solr to not start, because the Java commandline
would be invalid. The variable is commented in the file you sent.
The log file contains two error messages that appear to be the same.
You tried indexing a document that was incompatible with your schema.
This is the relevant part of the error message: "multiple values
encountered for non multiValued field type_t_zh". If you are going to
index multiple values in a field, the field MUST be multiValued, or Solr
will throw that error.
Thanks,
Shawn
