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_05_06 22:49] – [Configuration] steven | cloudappliance/appliance-troubleshooting [2019_09_04 18:19] – solr instructions didn't show in fixed width - hard to read 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 101: | Line 101: | ||
/ | / | ||
+ | |||
+ | ### Log Rotation | ||
+ | |||
+ | A log rotation script runs under cron. | ||
+ | |||
+ | / | ||
+ | |||
+ | The configuration file is at: | ||
+ | |||
+ | / | ||
## Ports In Use | ## Ports In Use | ||
Line 132: | 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 a table has run out of memory | ||
+ | |||
+ | / | ||
- | If you have configured notification email, then you will receive notification email with the errors.) | + | 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: | ||
Line 323: | Line 338: | ||
To access the Solr admin from another machine: | To access the Solr admin from another machine: | ||
- | 1. Add this line to / | + | Add this line to / |
-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 / | + | Comment out the line in / |
# | # | ||
- | 4. From a browser: | + | From a browser: |
http:// | http:// |