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:automation

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:automation [2015/12/14 19:09] – ↷ Page moved from automation to administration:automation demiankatzadministration:automation [2018/12/19 17:19] demiankatz
Line 40: Line 40:
 === Why restart VuFind? === === Why restart VuFind? ===
  
-The main reason to regularly restart the VuFind is to ensure system stability.  Due to the way Java garbage collection works, Solr can eventually run out of memory and stop responding; periodic restarts are an easy way to avoid this problem.  If you want to automatically detect garbage collection problems in a more sophisticated way, you can try this solution suggested by Erik Mitchell: +The main reason to regularly restart the VuFind is to ensure system stability.  Due to the way Java garbage collection works, Solr can eventually run out of memory and stop responding; periodic restarts are an easy way to avoid this problem.  It is also a good idea to investigate [[administration:performance#java_tuning|Java tuning]] to address the root cause -- but even with a well-tuned systemoccasional restarts (such as, on weekly basis) can help ensure long-term stability.
- +
-1.  Modify the JAVA_OPTIONS to include Garbage Collector logging (Xloggc) +
- +
-<code> +
-JAVA_OPTIONS="-server -Xms1024m -Xmx3800m -XX:+UseParallelGC -XX:NewRatio=5 -Xloggc:/var/log/vufindr/gc.log" +
-</code> +
- +
-2.  Create and cron a script that searches this log for the word Full.  If it finds itthe GC has failed and it is only matter of time before vufind bonks. +
- +
-<code> +
-if [[ $(grep -c 'Full' /var/log/vufind/gc.log) != 0 ]];then  +
-exec /usr/local/vufind/vufind_cron.sh restart >> /home/vufind/cron.log +
-fi  +
-</code> +
- +
-(File paths may need to be adjusted to match your own system). +
 ==== Using mysqldump ==== ==== Using mysqldump ====
  
Line 351: Line 334:
   * As with the previous script, you need to have SSH keys set up so that SFTP can transfer files automatically.   * As with the previous script, you need to have SSH keys set up so that SFTP can transfer files automatically.
   * You'll need to customize some variables to match your local setup.   * You'll need to customize some variables to match your local setup.
-  * When using VuFind 1.x, be sure you run this script a significant amount of time AFTER the update script listed above.  In 1.x, both the update's suppressed cleanup and this script will optimize your Solr index.  You don't want to have two optimize actions going on at the same time! If you are using VuFind 2.x, the delete script does not automatically optimize your index, giving you more control over the timing. 
  
 <code bash> <code bash>
administration/automation.txt · Last modified: 2023/03/06 20:48 by demiankatz