Hello!
I am using DSpace 8 and working fine till yesterday I upgrade the Debian 12. after upgrading when i try to submit new item to the repository as administer I getting the below error
" You don't have permission to make a new submission." and also getting an "Error fetching search results" at the administer workflow page.
Kindly help!
Many thanks
--
All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/56b8ee91-b66a-45d6-b830-2f2ae1eef4den%40googlegroups.com.
In our case, when a popup message appeared on the upper right side announcing that we did not have permission to add an item, it was an error in SOLR.
It may be that it has not been indexed or that there has been an error in the indexing.
First we check the permissions on the directory:
/var/solr/data/... (they should be solr:solr).
And also in /dspace/log/ (must be dspace:dspace)
If in SOLR there are files .../index/write.lock we delete them and restart the service:
[dspace] /opt/solr/bin/solr restart.
Now we reindex again:
[dspace] nohup /dspace/bin/dspace index-discovery -b
With nohup we make sure that, even if the communication is interrupted, the process continues running. It will create a file “nohup.out” with the process log. This way we will see if the indexing has errors.
If everything went well, we will be able to add items.
Thanks for the reply. All the permissions are the same as you mentioned. I haven't found a file named 'write.lock' anywhere and I also reindexed, but nothing changed
We encountered the same error messages. In our case, the problem was with the item-submission.xml file. Our test instance had 6 collections configured, but the production instance only had 3. However, the item-submission.xml file on both instances still referenced all 6 collections.
After removing the 3 unused collection references from the file on production, everything worked correctly.
Here’s an example of one configuration entry: