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
cloudappliance/appliance-troubleshooting [2019_06_26 23:20] stevencloudappliance/appliance-troubleshooting [2019_09_04 18:19] – solr instructions didn't show in fixed width - hard to read steven
Line 9: Line 9:
    * Apache Solr search engine    * Apache Solr search engine
  
-It is most commonly used this these deployment scenarios+The most common deployment scenarios are:
   * Single server with database - with the File Fabric Engine and database server on a single instance   * Single server with database - with the File Fabric Engine and database server on a single instance
   * Single server separate database - The File Fabric Engine runs on one instance. The database runs separately either as an additional instance or through a database-as-as-service.   * Single server separate database - The File Fabric Engine runs on one instance. The database runs separately either as an additional instance or through a database-as-as-service.
   * High availability - The File Fabric Engine runs on multiple instances behind a load balancer. A high availability database cluster or database-as-as-service is used.   * High availability - The File Fabric Engine runs on multiple instances behind a load balancer. A high availability database cluster or database-as-as-service is used.
-  * The Apache Solr application is required when content search is required. It should run on  a separate machine instance.+  * The Apache Solr service is optional, but required to support content search. It should run on a separate machine instance.
  
 ## Prerequisites ## Prerequisites
Line 142: Line 142:
 ## Disk Space procedure  ## Disk Space procedure 
  
-You can check the disk space by running the command <code>df -kh</code>, you will see the following error for any mysql table in the SME Error Logs  +You can check the disk space by running the command
-    <code>/var/www/smestorage/sitelogs/errorlogs.txt</code>.+
  
-If you have configured notification email, then you will receive notification email with the errors.)+    df -kh 
 +     
 +If a table has run out of memory you will see errors in the SME Error Logs 
 + 
 +    /var/www/smestorage/sitelogs/errorlogs.txt 
 + 
 +If you have configured notification email, then you will receive notification email with the errors.
  
 If you ran out of diskspace please see the instruction below: If you ran out of diskspace please see the instruction below:
Line 333: Line 338:
 To access the Solr admin from another machine: To access the Solr admin from another machine:
  
-1. Add this line to /etc/sysconfig/iptables:+Add this line to /etc/sysconfig/iptables:
  
     -A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 7070 -j ACCEPT     -A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 7070 -j ACCEPT
  
-2. Restart iptables+Restart iptables
  
     systemctl reload iptables     systemctl reload iptables
  
-3. Comment out the line in /home/sme/sme_jetty/start.ini:+Comment out the line in /home/sme/sme_jetty/start.ini:
  
     #jetty.host=127.0.0.1     #jetty.host=127.0.0.1
  
-4. From a browser:+From a browser:
  
     http://hostname:7070/  with user solr password drom6etsh9Onk     http://hostname:7070/  with user solr password drom6etsh9Onk