You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you run a new backup (look at the crontab and copy the backup command, run it as deploy user) and then consult /tmp/solr_backup.log you will see request ids and can use those to check the status of the backup like so:
{
"responseHeader":{
"status":0,
"QTime":4},
"success":{
"lib-solr-staging1.princeton.edu:8983_solr":{
"responseHeader":{
"status":0,
"QTime":0}}},
"geniza-2025011614562084550127003914":{
"responseHeader":{
"status":0,
"QTime":0},
"STATUS":"failed",
"msg":"Failed to backup core=geniza_shard1_replica_n1 because org.apache.solr.common.SolrException: Path /mnt/solr_backup/solr9/staging/20250116/geniza-20250116.bk/geniza must be relative to SOLR_HOME, SOLR_DATA_HOME coreRootDirectory. Set system property 'solr.allowPaths' to add other allowed paths."},
"failure":{
"lib-solr-staging1.princeton.edu:8983_solr":{
"responseHeader":{
"status":0,
"QTime":0},
"STATUS":"failed",
"msg":"Failed to backup core=geniza_shard1_replica_n1 because org.apache.solr.common.SolrException: Path /mnt/solr_backup/solr9/staging/20250116/geniza-20250116.bk/geniza must be relative to SOLR_HOME, SOLR_DATA_HOME coreRootDirectory. Set system property 'solr.allowPaths' to add other allowed paths."}},
"Operation backup caused exception:":"java.nio.file.NoSuchFileException:java.nio.file.NoSuchFileException: /mnt/solr_backup/solr9/staging/20250116/geniza-20250116.bk/geniza/zk_backup_0",
"exception":{
"msg":"/mnt/solr_backup/solr9/staging/20250116/geniza-20250116.bk/geniza/zk_backup_0",
"rspCode":-1},
"status":{
"state":"failed",
"msg":"found [geniza-202501161456] in failed tasks"}}
It seems like there's something we could do in solr9 playbook to make this work.
If you run a new backup (look at the crontab and copy the backup command, run it as deploy user) and then consult
/tmp/solr_backup.log
you will see request ids and can use those to check the status of the backup like so:curl "http://localhost:8983/solr/admin/collections?action=REQUESTSTATUS&requestid=geniza-202501161456"
Currently we get the following status:
It seems like there's something we could do in solr9 playbook to make this work.
See more at https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html
Expected behavior
A clear and concise description of what you expected to happen.
Actual behavior
Include screenshots, or links and browser version if relevant.
Error messages
Include any error messages from STDOUT, STDERR, log files, etc., that you did not include under 'Actual behavior' above.
Steps to replicate
How would someone else make this error happen?
Impact of this bug
E.g. "I can't work until this is fixed" or "I have a workaround".
Relevant links and code snippets, if applicable
Implementation notes, if any
The text was updated successfully, but these errors were encountered: