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
Last revisionBoth sides next revision
cloudappliance/appliance-troubleshooting [2020_05_04 16:13] – [Error Log] stevencloudappliance:appliance-troubleshooting [2024_04_03 21:30] – [Process Check] steven
Line 1: Line 1:
 # Appliance Troubleshooting # Appliance Troubleshooting
-Last updated on April 6, 2020. 
  
-This document covers troubleshooting of the Enterprise File Fabric Server. The Server runs as a virtual machine which may be scaled out horizontally (run as multiple instances).+#### Last updated on March 15, 2024 
 + 
 +This document covers troubleshooting of the Nasuni Access Anywhere Server. The Server runs as a virtual machine that may be scaled out horizontally (run as multiple instances).
  
 The virtual appliance is a hardened CentOS image with: The virtual appliance is a hardened CentOS image with:
-   * Enterprise File Fabric Engine components+   * Access Anywhere components
    * MariaDB database server    * MariaDB database server
    * Apache Solr search engine    * Apache Solr search engine
  
 The most common deployment scenarios are: 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 Access Anywhere 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 Access Anywhere 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 Access Anywhere Engine runs on multiple instances behind a load balancer. A high availability database cluster or database-as-as-service is used.
   * The Apache Solr service is optional, but required to support content search. 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
  
-Before you begin troubleshooting and checking the Enterprise File Fabric Server you should have the following information:+Before you begin troubleshooting and checking Access Anywhere Server you should have the following information:
  
    * Server domain name    * Server domain name
Line 26: Line 27:
   * Is ClamAV being used?   * Is ClamAV being used?
   * Passwords:   * Passwords:
-    * smeconfigure password(s)+    * smeconfiguser password(s)
     * root password(s)     * root password(s)
     * database credentials (optional)     * database credentials (optional)
Line 162: Line 163:
     df -kh     df -kh
          
-If a table has run out of memory you will see errors in the SME Error Logs+If a table has run out of memory you will see errors in the NAAError Logs
  
-    /var/www/smestorage/sitelogs/errorlogs.txt+    /var/www/smestorage/sitelogs/logits.txt
  
 If you have configured a notification email, then you will receive notification email with the errors. If you have configured a 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: [[:cloudappliance/determine_layout]]
    
-DB! Table './smestorage/TABLE' is marked as crashed and should be repaired +    DB! Table './smestorage/TABLE' is marked as crashed and should be repaired 
-Symptom - You open the configured SME appliance url in a browser and see an empty page+    Symptom - You open the configured NAA appliance url in a browser and see an empty page
  
 ## Action to Bring up the Appliance ## Action to Bring up the Appliance
Line 177: Line 178:
 ### Increase Disk Size ### Increase Disk Size
  
-To increase the diskspace on SME appliance see the recipe to increase disk space: https://storagemadeeasy.com/wiki/cloudappliance/appladmin+To increase the diskspace on NAA appliance see the recipe to increase disk space: https://storagemadeeasy.com/wiki/cloudappliance/appladmin
  
 ### Repair the Database ### Repair the Database
Line 207: Line 208:
 ### Delete compiled templates ### Delete compiled templates
  
-SME uses compiled templates. If disk space is low the templates can become corrupted. To fix this:+NAAuses compiled templates. If disk space is low the templates can become corrupted. To fix this:
  
 ssh in to appliance as smeconfiguser ssh in to appliance as smeconfiguser
Line 231: Line 232:
  
     find / -xdev -type f -size +10M -exec du -sh {} ';' | sort -rh | head -n50     find / -xdev -type f -size +10M -exec du -sh {} ';' | sort -rh | head -n50
- 
 ## Process Check ## Process Check
  
Line 241: Line 241:
     systemctl status crond     systemctl status crond
     systemctl status mariadb   # if running locally     systemctl status mariadb   # if running locally
-    systemctl status memcached+    docker ps | grep memcached_memcached
  
 ## PHP-FPM Service ## PHP-FPM Service
Line 260: Line 260:
  
     /var/log/php-fpm/error.log     /var/log/php-fpm/error.log
 +
 +### Configuration
 +
 +The configuration file is located here:
 +
 +    /etc/php-fpm.d/www.conf
 +    
 +Please do not change settings without working with support. 
  
 ## Apache HTTP Server (Web Server) ## Apache HTTP Server (Web Server)
Line 308: Line 316:
 This means a record could not be added to memcached and because of that the upload failed. This means a record could not be added to memcached and because of that the upload failed.
  
-To solve this as a root issue the following command:+Another indication of a memcached issue is that you may receive an email notification that a session write failed:
  
-    systemctl restart memcached+{{:appliance:session_not_initialized_email.png?600|}}
  
-After that you can also check the service status:+or see a message in the browser that the storage session could not be initialized:
  
-    systemctl status memcached+{{:appliance:session_not_initialized_browser.png?600|}}
  
-You should see something similar to the below:+and Access Anywhere may not be usable. 
  
-    Active: active (running) since Thu 2016-08-25 13:30:00 BST; 1s ago+To solve any of these memcached issues, as root issue the following command: 
 + 
 +<code> 
 +yum install sme-containers-memcached 
 +cd /var/www/smestorage/containers/memcached 
 +docker-compose restart 
 +</code>
  
 ## Jetty / Apache Solr / PDF Annotation ## Jetty / Apache Solr / PDF Annotation
Line 341: Line 355:
  
 See https://docs.storagemadeeasy.com/cloudappliance/solr for more information. See https://docs.storagemadeeasy.com/cloudappliance/solr for more information.
- 
 ### Logs ### Logs
  
     /home/sme/sme_jetty/logs/solr.log     /home/sme/sme_jetty/logs/solr.log
 +    
 +    /var/solr/logs/solr.log
  
 ### Production ### Production
  
-Note: For production Apache Solr should be running on a separate instance to the Enterprise File Fabric Server (Web Tier). +Note: For production Apache Solr should be running on a separate instance to Access Anywhere Server (Web Tier).
 ### Access Solr Admin GUI Remotely ### Access Solr Admin GUI Remotely
  
-To access the Solr admin from another machine:+SSH can be used to create an HTTP tunnel to access the Solr admin from another machine. For example,
  
-Add this line to /etc/sysconfig/iptables: +   ssh -L 8983:files.example.com:8983 smeconfiguser@files.example.com
- +
-    -A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 7070 -j ACCEPT +
- +
-Restart iptables +
- +
-    systemctl reload iptables +
- +
-Comment out the line in /home/sme/sme_jetty/start.ini: +
- +
-    #jetty.host=127.0.0.1+
  
 From a browser: From a browser:
  
-    http://hostname:7070/  with user solr password drom6etsh9Onk+    http://localhost:8983/solr  
 +     
 +The default username is "solr" with password drom6etsh9Onk.
  
 ## Cloud FTP Service (CloudFTP/CloudFTPS) ## Cloud FTP Service (CloudFTP/CloudFTPS)
  
-By default the File Fabric Cloud FTP service is configured to run an FTP service on port 21 and FTPS (FTP over SSL) service on port 990. See [[cloudappliance/sftpsetup]] for more information. +See [[cloudappliance/cloudftp-configuration]] for more information.
- +
-Check the health of the Cloud FTP service using the service command: +
- +
-    systemctl status cloudftp +
- +
-You should see a few lines of output including one that says, "Active: active (exited)". +
- +
-To start the service: +
- +
-    systemctl start cloudftp +
- +
-To stop the service: +
- +
-    systemctl stop cloudftp+
  
 ### Client Testing ### Client Testing
  
     sftp -v  user@hostname     sftp -v  user@hostname
- 
-### Configuration 
- 
-    /var/www/smestorage/ftpserver/ftpserver.conf 
- 
-### Log 
- 
-    /var/www/smestorage/ftpserver/ftpserver.txt 
- 
-## Cloud SFTP Service 
- 
-The Cloud SFTP service implements the SSH File Transfer Protocol for File Fabric. By default it's available on port 2200. See [[cloudappliance/sftpsetup]] for more information. 
- 
-### Configuration 
- 
-    /var/www/smestorage/ftpserver/sftpserver/sftpserver.conf 
- 
-### Restart 
-     
-To restart the service after a configuration change: 
- 
-    systemctl start cloudftp 
- 
-### Log 
- 
-    /var/www/smestorage/ftpserver/sftpserver/log.txt 
  
 ## Local FTP Service ## Local FTP Service
Line 459: Line 425:
  
 ### Logs ### Logs
 +
 +A log of cron jobs being started can be found at:
  
     /var/log/cron     /var/log/cron
 +
 +A detailed log of the task manager can be found at:
 +
     /var/www/smestorage/cron/log.txt     /var/www/smestorage/cron/log.txt
  
Line 482: Line 453:
 ## CloudDAV ## CloudDAV
  
-CloudDAV is our implementation of WebDAV on top of the File Fabric. It runs as a CGI script from /var/www/smestorage/webdav_html/cgi-bin.+CloudDAV is our implementation of WebDAV on top of Access Anywhere. It runs as a CGI script from /var/www/smestorage/webdav_html/cgi-bin.
  
 ### Log ### Log
Line 494: Line 465:
 ## Cloud S3 ## Cloud S3
  
-Cloud S3 is our implementation of an Amazon S3 compatible API on top of the File Fabric.+Cloud S3 is our implementation of an Amazon S3 compatible API on top of Access Anywhere.
  
 ### Log ### Log
  
-    /var/www/smestorage/ftpserver/sftpserver/log.txt+    /var/www/smestorage/s3_html/cgi-bin/log.txt
  
 ### Configuration ### Configuration
Line 567: Line 538:
     /var/log/maillog     /var/log/maillog
  
-## License (Enterprise File Fabric)+## License (Access Anywhere)
  
 This error on attempted login indicates problems with the license key including not present or expired. This error on attempted login indicates problems with the license key including not present or expired.
Line 598: Line 569:
  
 1) From the shell use the System Package Manager 1) From the shell use the System Package Manager
-   +
    yum info sme-ff-filefabric.x86_64    yum info sme-ff-filefabric.x86_64
  
 2) From the database 2) From the database
  
-   mysql> SELECT * FROM smestorage.se_version;+   SELECT * FROM smestorage.se_version;
  
 3) From the shell as smeconfiguser run the alias: 3) From the shell as smeconfiguser run the alias:
Line 661: Line 632:
 ## Fail2Ban ## Fail2Ban
  
-The SME Appliance ships with a customized version of Fail2Ban (http://www.fail2ban.org/). +The NAA Appliance ships with a customized version of Fail2Ban (http://www.fail2ban.org/). 
  
 Fail2Ban scans logs file for malicious patterns ie. DoS attacks, too many password failures, SSH logins, seeking exploits, trying to scan for download links etc.  Fail2Ban scans logs file for malicious patterns ie. DoS attacks, too many password failures, SSH logins, seeking exploits, trying to scan for download links etc. 
© Copyright 2024 Nasuni.