Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
cloudappliance/appliance-troubleshooting [2019_06_04 21:06] – [Log Archive] steven | cloudappliance/appliance-troubleshooting [2019_06_26 23:25] – [Disk Space procedure] steven | ||
---|---|---|---|
Line 2: | Line 2: | ||
Last updated on April 17, 2019. | Last updated on April 17, 2019. | ||
- | This document covers troubleshooting of the Enterprise File Fabric Server. The Server runs as a virtual machine, an instance of the Enterprise File Fabric virtual appliance and may be scaled out horizontally (run as multiple instances). | + | This document covers troubleshooting of the Enterprise File Fabric Server. The Server runs as a virtual machine |
The virtual appliance is a hardened CentOS image with: | The virtual appliance is a hardened CentOS image with: | ||
Line 9: | Line 9: | ||
* Apache Solr search engine | * Apache Solr search engine | ||
- | It is most commonly used this these deployment scenarios | + | The most common |
* 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 | + | * The Apache Solr service |
## Prerequisites | ## Prerequisites | ||
Line 142: | Line 142: | ||
## Disk Space procedure | ## Disk Space procedure | ||
- | You can check the disk space by running the command | + | You can check the disk space by running the command |
- | < | + | |
- | 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 | ||
+ | |||
+ | / | ||
+ | |||
+ | If you have configured | ||
If you ran out of diskspace please see the instruction below: | If you ran out of diskspace please see the instruction below: |