lt;https://www.plus.ac.at/>
[cid:563df9c7-d690-418f-92bc-9d6c6eb7e77c]
Von: Ehrenleitner Robert Harald
Gesendet: Dienstag, 24. September 2024 15:59
An: users@solr.apache.org
Betreff: AW: Weird error message with solr config
Thank you, this makes some progress.
Now, I
Thank you, this makes some progress.
Now, I receive the 401 error again. The environment variable
SOLR_AUTHENTICATION_OPTS is set, and passing its value additionally doesn't
help either.
Mag.phil. Robert Ehrenleitner, B.Eng.
Webdeveloper
IT-Services
Paris-Lodron-Universität Salzburg
Hel
Maybe that's relevant: I just noticed that on the production system, the search
indices (the cores) were created with version 9.1. It was later upgraded to 9.4
without recreating the search indices. So, I never executed that command which
fails in 9.4 either.
Mag.phil. Robert Ehrenleitner, B.E
Once again, to be sure:
$ searchIndex=mysearchindex
$ bin/solr create -c $searchIndex
WARNING: Using _default configset with data driven schema functionality. NOT
RECOMMENDED for production use.
To turn off: bin/solr config -c mysearchindex -p 8983 -action
set-user-property -property up
Hi,
even with 9.4 I get a strange error:
$ bin/solr config -c mysearchindex -solrUrl http://localhost:8983 -action
set-user-property -property update.autoCreateFields -value false
POSTing request to Config API: http://localhost:8983/mysearchindex/config
{"set-user-property":{"update.autoCreateF
Hi,
thanks for the fast reply. I didn't consider that bin/solr could be a bash
script. I removed (commented out) the offending "if"-block in lines 990-992.
Now, it does not throw this error anymore, but now it claims that I did not
pass authorisation. The enviroment variables for authorisation
