This section will show you how to access some of the basic error reporting functions for Drupal, Fedora, Apache, Tomcat, and Microservices. For specific troubleshooting on the installation process, check out Troubleshooting Installation.
Most components in the Islandora stack have their own log. This document will describe each of those logs: where they can be found; how to configure them; and what information they contain. Logs typically have "levels" which are used to determine what kinds and how much information should be placed in them. A general rule of thumb is that a log will support the following levels in order of the most information to the least:
...
Drupal core/modules often display Drupal, PHP, and SQL error messages to the end user in the browser as they happen. Often these messages will refer to a problem/action that occurred during the previous request. Most likely if you encounter a problem at this level, someone else has as well; its best to search google for relevant information. The issues are colour coded by seriousness, (red = error, yellow = warning, green = status/info).
Drupal also logs information to what it calls the 'watchdog'. The watchdog is essentially a database table, within the Drupal database. It contains messages generated by Drupal core/module code. You can view the 'watchdog' by visiting "http://yoursite/admin/reports/dblog" or by logging into your site, clicking the 'Reports' link in the admin bar (or navigating to http://URL.of.your.site/admin) and clicking 'Recent log entries' under 'Reports'. Errors are categorized by "type" which usually indicates which module generated the message.
You will see a list of recent log entries from various sources. Not all entries are errors - error messages will be marked with a red 'X'.
Clicking on a message description will give you a detailed summary of the error. You can use this information to troubleshoot a problem yourself, or to provide more detail to a technical support contact.
Check the watchdog frequently even when the site is working correctly. Many non-fatal issues will be logged to the watchdog. Be proactive! Check the watchdog when:
...
You will then be prompted for your password.
Navigate to your Fedora logs directory; for example:
...
From here you can type 'ls' to view a list of files in the directory.
You can view a log file in various ways; for example:
...