[simplistics-gord]

1 year, 8 months ago in reply to: Unable to create new core WPSolr 22.3, Solr 9.0 #30720

I’ve resolved permission issues and no longer get the warning of not being able to write to the configset dir, but still have the Solr error Exception in reloading spell check index for spellchecker: suggest when creating the index, which triggers the request to fail and the configuration to not save to the site DB

[simplistics-gord]

1 year, 8 months ago in reply to: Unable to create new core WPSolr 22.3, Solr 9.0 #30674

After extracting the WPSolr-generated configset files to /var/solr9/data/configsets/indexname, loading the Core Admin page of the Solr Admin panel shows the following error:
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: Could not load configuration from directory /var/solr9/data/configsets/indexname

Attemping to then create the core from the interface, using default values except for instanceDir:configsets/indexname as suggested, another error is thrown:
org.apache.solr.common.SolrException: Error CREATEing SolrCore ‘indexname’: Couldn’t persist core properties to /var/solr9/data/configsets/indexname/core.properties

[simplistics-gord]

1 year, 8 months ago in reply to: Unable to create new core WPSolr 22.3, Solr 9.0 #30670

I don’t have alot of Solr experience and don’t know how to do that, but if I create and extract the configset files as in WPSolr instructions, then attempt to create the core through the Solr Admin interface with the following args, I get an error:
Name: new_index_name
InstanceDir: new_index_name
DataDir: data
Config: solrconfig.xml
Schema: schema.xml

The error is :
Can’t find resource ‘solrconfig.xml’ in classpath or ‘/var/solr9/data/new_index_name’
^^ As mentioned before, my server is running 2 different versions of Solr on different ports, so /var/solr is 8.x and /var/solr9 is 9.x.

[simplistics-gord]

1 year, 8 months ago in reply to: Unable to create new core WPSolr 22.3, Solr 9.0 #30668

Just the same issues I flagged in my original post. It looks as though perhaps it can’t write to the config directory, which is is later causing the spellchecker tst.dat file to not be created, and ultimately the error is thrown when trying to read that file during spell check index reload?

[simplistics-gord]

1 year, 8 months ago in reply to: Unable to create new core WPSolr 22.3, Solr 9.0 #30666

Yes I have added custom debug logging at ajax_solr_services.php:275. The error message is a nondescript “Solr HTTP error: HTTP request failed” even though the request was accepted by the server and the core was created. The error code is 0.

[simplistics-gord]

1 year, 8 months ago in reply to: Unable to create new core WPSolr 22.3, Solr 9.0 #30663

I don’t think that this is the issue. I just found this in the WPSolr-generated solrconfig.xml that it attempts to load lib files from both contrib (8.x) and modules (9.0) dirs, so that warning is unlikely related to the error.

[simplistics-gord]

1 year, 8 months ago in reply to: Unable to create new core WPSolr 22.3, Solr 9.0 #30662

I just downloaded copies of 8.11 and 9.0 to compare and 9.0 actually doesn’t ship with contrib/extraction/lib. Looks like the analogous files are in modules/extraction/lib. Presumably this is triggered to load from within Solr and this is more likely an issue with the Solr 9.0 server than a plugin integration issue?

[simplistics-gord]

1 year, 8 months ago in reply to: Unable to create new core WPSolr 22.3, Solr 9.0 #30660

Is there any sort of error logging that can be enabled within the plugin? When attempting to save the configuration, the site throws a nondescript ‘HTTP Request Failed’ error, which doesn’t help in finding/resolving the issue.

[simplistics-gord]

1 year, 8 months ago in reply to: Unable to create new core WPSolr 22.3, Solr 9.0 #30655

Yes.

1. The first time generates the configset and provides instructions for downloading and installing, and tells you to re-save the configuration to create the core/save to the site DB as normal.
2. The second time creates the core but displays a generic HTTP error issue in the interface (Apache Solr logs include the error in original post)
3. Any additional attempts fail because the core is already created