[community edition] Solr doesn't start after migration from 7.3.0 to 23.4.1

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2025 05:18 AM
Hello,
I have upgraded my communty edition to 23.4.1 on a Linux Devuan server (Debian like). Previously, solr ran fine. Now, search services fail and if I try to do a connction to localhost:8983/solr, I only obtain following error:
HTTP ERROR 500
Problem accessing /solr/. Reason:
Server Error
Caused by:
java.lang.NoClassDefFoundError: Could not initialize class org.alfresco.solr.AlfrescoSolrDataModel
at org.alfresco.solr.security.SecretSharedPropertyCollector.lambda$static$1(SecretSharedPropertyCollector.java:74)
at org.alfresco.solr.security.SecretSharedPropertyCollector.lambda$getProperty$4(SecretSharedPropertyCollector.java:118)
at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
at java.base/java.util.ArrayList$ArrayListSpliterator.tryAdvance(ArrayList.java:1632)
at java.base/java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:127)
Solr seems to be running:
Root rayleigh:[/opt/alfresco/alfresco-search-services/logs] > ps auwx | grep solr
tomcat 19824 15.0 7.5 6803200 1237556 ? Sl 11:14 0:06 java -server -Xms1g -Xmx1g -XX:+UseG1GC -XX:+PerfDisableSharedMem -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=250 -XX:+UseLargePages -XX:+AlwaysPreTouch -XX:+ExplicitGCInvokesConcurrent -Xlog:gc*:file=../../logs/solr_gc.log:time,uptime:filecount=9,filesize=20000 -Dsolr.log.dir=../../logs -Djetty.port=8983 -DSTOP.PORT=7983 -DSTOP.KEY=solrrocks -Duser.timezone=UTC -Djetty.home=/opt/alfresco/alfresco-search-services/solr/server -Dsolr.solr.home=/opt/alfresco/alfresco-search-services/solr/../solrhome -Dsolr.install.dir=/opt/alfresco/alfresco-search-services/solr -Dlog4j.configuration=file:../../logs/log4j.properties -Dsolr.jetty.request.header.size=1000000 -Dsolr.jetty.threads.stop.timeout=300000 -Ddisable.configEdit=true -Xss256k -Dsolr.log.muteconsole -XX:OnOutOfMemoryError=/opt/alfresco/alfresco-search-services/solr/bin/oom_solr.sh 8983 ../../logs -jar start.jar --module=http
root 21023 0.0 0.0 6564 2252 pts/0 S+ 11:15 0:00 grep solr
Root rayleigh:[/opt/alfresco/alfresco-search-services/logs] >
and I have no error in solr log file prior to first access from Alfresco:
2025-02-12 10:14:40.370 INFO (main) [ ] o.e.j.s.Server jetty-9.3.30.v20211001, build timestamp: 2021-10-01T15:51:54Z, git hash: 148ea770504ad315b7936c5737e462879680042b
2025-02-12 10:14:40.789 INFO (main) [ ] o.a.s.s.SolrDispatchFilter ___ _ Welcome to Apache Solr™ version 6.6.5-patched.11 67b7042d8e2134a87c2ef6e663b1fb0cc0c2d454 - pzurek - 2022-11-28 14:45:37
2025-02-12 10:14:40.790 INFO (main) [ ] o.a.s.s.SolrDispatchFilter / __| ___| |_ _ Starting in standalone mode on port 8983
2025-02-12 10:14:40.790 INFO (main) [ ] o.a.s.s.SolrDispatchFilter \__ \/ _ \ | '_| Install dir: /opt/alfresco/alfresco-search-services/solr
2025-02-12 10:14:40.793 INFO (main) [ ] o.a.s.s.SolrDispatchFilter |___/\___/_|_| Start time: 2025-02-12T10:14:40.790654Z
2025-02-12 10:14:41.479 WARN (main) [ ] o.a.s.InterceptorRegistry It was not possible to add the Shared Secret Authentication interceptor. Please make sure to pass the required -Dalfresco.secureComms=secret and -Dalfresco.secureComms.secret=my-secret-value JVM args if trying to use Secret Authentication with Solr.
2025-02-12 10:14:41.583 INFO (main) [ ] o.e.j.s.Server Started @1780ms
I suppose I have done a misconfiguration somewhere, but I'm unable to find where org.alfresco.solr.AlfrescoSolrDataModel is defined.
Help will be welcome,
JB
- Labels:
-
Alfresco Content Services

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2025 09:04 AM
Does your solr.in.cmd file have these params?
set SOLR_ALFRESCO_SECURECOMMS=secret
set SOLR_ALFRESCO_SECURECOMMS_SECRET=yoursecret
In my case if I don`t set up them at Solr side (even though they are defined at alfresco side in alfresco-global.properies) the requests fail with 403 status code. However the exception messages are not the same like yours...
