About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
administration:starting_and_stopping_solr

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
administration:starting_and_stopping_solr [2021/10/19 11:40] – [Linux Method] demiankatzadministration:starting_and_stopping_solr [2023/03/08 18:45] demiankatz
Line 168: Line 168:
 :!: If you need to run VuFind with non-default settings, you may wish to add some lines to export environment variables in this script, or else source a script containing all of your environment settings prior to running "solr.sh". In many newer installations of VuFind, such a script is already set up as /etc/profile.d/vufind.sh. :!: If you need to run VuFind with non-default settings, you may wish to add some lines to export environment variables in this script, or else source a script containing all of your environment settings prior to running "solr.sh". In many newer installations of VuFind, such a script is already set up as /etc/profile.d/vufind.sh.
  
-:!: Newer versions of Solr do not like to be run by the root user; you may need to either add "export SOLR_ADDITIONAL_START_OPTIONS=-force" to your script to force root permissions, or (preferably) set up your script to run Solr as a dedicated user (which can be done by wrapping the solr.sh command with "/bin/su - username -c ..."). +:!: Newer versions of Solr do not like to be run by the root user; you may need to either add "export SOLR_ADDITIONAL_START_OPTIONS=-force" to your script to force root permissions, or (preferably) set up your script to run Solr as a [[administration:security#creating_a_dedicated_solr_user|dedicated user]] (which can be done by wrapping the solr.sh command with "/bin/su - username -c ..."). 
  
 <code> <code>
Line 223: Line 223:
  
 To automate Solr with systemd: To automate Solr with systemd:
-  * create the user "solr", because Solr should not be run under root user.+  * [[administration:security#creating_a_dedicated_solr_user|create the user "solr"]], because Solr should not be run under root user.
   * add permission for the solr directory to this user:    * add permission for the solr directory to this user: 
  
Line 235: Line 235:
 [Unit] [Unit]
 Description=VuFind Starter Description=VuFind Starter
-After=network.target httpd.service mariadb.service+After=network.target
  
 [Service] [Service]
Line 255: Line 255:
 <code> <code>
 [Unit] [Unit]
-After=network.target httpd.service mariadb.service+After=network.target
  
 [Service] [Service]
Line 297: Line 297:
 If you simply stop the Solr server, users attempting to access your VuFind site will encounter error messages.  If you are planning an outage, you can take the site more gracefully offline by adjusting the "available" setting in the "[System]" section of your [[configuration:files:config.ini]] file. If you simply stop the Solr server, users attempting to access your VuFind site will encounter error messages.  If you are planning an outage, you can take the site more gracefully offline by adjusting the "available" setting in the "[System]" section of your [[configuration:files:config.ini]] file.
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
administration/starting_and_stopping_solr.txt · Last modified: 2023/10/24 13:47 by demiankatz