Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 8 Next »

Problem

Some errors are not captured in Totara logs or debugging message. For example authentication errors may occur before Totara is logged into , there may be a file size or processing limit on the web server that has been exceeded. In these cases the Web server logs contain information on the error that has occurred so needs to be viewed to help see what has happened.

Totara supports Apache and Internet Information Server web servers.

Solution

This depends on the web server being used:

Apache Web Server
  1. The name and the location of the log is set by the ErrorLog command and the default apache access log file location:

    • RHEL / Red Hat / CentOS / Fedora Linux Apache access log file location – /var/log/httpd/access_log
    • Debian / Ubuntu Linux Apache access log file location – /var/log/apache2/access.log
    • FreeBSD Apache access log file location – /var/log/httpd-access.log


    The web server user will need to have write access to the error log directory



  2. There may be a graphical application that manages the server.  For example in the Bitnami stack there is Manager app where you select Manage Servers > Open Error log

Internet Information Server
  1. Open the Internet information Services manager application
  2. A list of sites will display in the IIS manager panel - note the site ID of your Totara site
  3. Click on your Totara site and double click the Logging icon
  4. Select Directory and navigate to the folder that ends with site ID of your Totara site. For example, W3SVC2 for site ID 2 

Filter by label

There are no items with the selected labels at this time.

  • No labels