solr-jetty does not work - multiple issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lucene-solr (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After installing solr-jetty and solr-common (3.6.2+dfsg-1) on Ubuntu 18.04.4 LTS, jetty starts and reports a banner page at http://
(I'm guessing based on the config that this is the path - the documentation explains *nothing*).
Although a directories /var/log/solr and /var/log/jetty9 are created, there is nothing in them.
systemd is capturing some information that suggests something is going wrong at startup:
? jetty9.service - Jetty 9 Web Application Server
Loaded: loaded (/lib/systemd/
Active: active (running) since Mon 2020-03-30 22:27:39 BST; 13min ago
Docs: https:/
Main PID: 1206 (java)
Tasks: 27 (limit: 2318)
CGroup: /system.
+-1206 /usr/bin/java -Djetty.
Mar 30 22:27:41 dev-a02-si-solr.bip jetty9[1206]: at org.eclipse.
Mar 30 22:27:41 dev-a02-si-solr.bip jetty9[1206]: at sun.reflect.
Mar 30 22:27:41 dev-a02-si-solr.bip jetty9[1206]: at sun.reflect.
Mar 30 22:27:41 dev-a02-si-solr.bip jetty9[1206]: at sun.reflect.
Mar 30 22:27:41 dev-a02-si-solr.bip jetty9[1206]: at java.lang.
Mar 30 22:27:41 dev-a02-si-solr.bip jetty9[1206]: at org.eclipse.
Mar 30 22:27:41 dev-a02-si-solr.bip jetty9[1206]: at org.eclipse.
Mar 30 22:27:41 dev-a02-si-solr.bip jetty9[1206]: at org.eclipse.
Mar 30 22:27:41 dev-a02-si-solr.bip jetty9[1206]: 2020-03-30 22:27:41.
Mar 30 22:27:41 dev-a02-si-solr.bip jetty9[1206]: 2020-03-30 22:27:41.
There are no setup instructions in /usr/share/
i.e. issues are:
1) it doesn't appear to work
2) documentation is incomplete
3) default configuration is not writing any log files
After trying solr-tomcat in place of solr-jetty, I get some more meaningful errors suggesting that the system won't start due to the lack of any base dataset. Navigating to the solr web page returns a stack trace suggesting:
If you want solr to continue after configuration errors, change: <abortOnConfigu rationError> false</ abortOnConfigur ationError> in solr.xml
However this tag is not currently present in solr.xml, and adding it / retarting the service had no impact on the behaviour.