Hi, if you are still hitting this issue, it seems to be a Solr question more than a DSpace one. Here's a guide though from ServerFault on how to possibly solve it in Solr: https://serverfault.com/questions/1023093/it-should-be-set-to-65000-to-avoid-operational-disruption
Tim On Tuesday, November 5, 2024 at 6:26:02 AM UTC-6 [email protected] wrote: > Dear Sir, > > Recently i encounter the error as i was trying to upgrade the Dspace from > 6 to 7. During the migration process everything went fine until i give the > *solr > *restart command. please anyone in this forum could enlighten me to sort > out the below error. > > > > > > > > > > > > *root@mseclibrary-V520-15IKL:/home/mseclibrary# su dspace$ > /opt/solr/bin/solr start*** [WARN] *** Your open file limit is currently > 1024.It should be set to 65000 to avoid operational disruption.If you no > longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false in > yourprofile or solr.in.sh <http://solr.in.sh>*** [WARN] *** Your Max > Processes Limit is currently 31093.It should be set to 65000 to avoid > operational disruption.If you no longer wish to see this warning, set > SOLR_ULIMIT_CHECKS to false in yourprofile or solr.in.sh > <http://solr.in.sh>ERROR: Logs directory /opt/solr/server/logs could not be > created. Exiting* > > Thank you > > Dr.Sureshkumar C. > -- 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 Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/dspace-community/7ca5800a-2391-47d3-b389-dec88819c4e0n%40googlegroups.com.
