AdminCenter12.1

Page tree

Page Description

Use the Error Log page as a diagnostic tool to monitor the event Error Log.

Note

In order to view the Database tab, the INI file must be configured so that ErrorLog is added to the DB_FEATURE_SET ACO for an additional database. This allows for the ability to record Error Log messages in the database. Error Log messages can be recorded in the database, in addition to recording them in a file. Error Log messages cannot be recorded in the primary system database; they can only be stored in an additional system database. If the INI file is configured to support the recording Error Log messages in an additional database, a new System Defaults page option for Error Log messages becomes available. The Error Log Type drop-down list is available on the Miscellaneous Settings tab on the System Defaults page.

  • File Tab: Use the File tab to view the original contents of the Error Log.
  • Database Tab: Use the Database tab to view the Error Log records using a datatable. Note that if the INI file is not configured to support the Error Log feature in an additional database, the Database tab will not appear on the Error Log page.

Accessing this Page

  • Select the Administration menu button, select the Monitor button, and then select the Error Log submenu link. You must have the necessary security permissions to access the Administration menu button. When you select the Administration menu button, the system opens the main Administration menu, which contains administrative menu buttons, including the Monitor menu. To return to the main menu for the system, select the Tasks menu button.

File Tab

Viewing File Actions

  1. Select the Server drop-down list to select a server to view log detail.
  2. Select an option from the File drop-down list. This list displays all of the files that the system has created to record errors. The most recent file ends in zero, and the system increases the numbers of the remaining files when it adds a new file. For example, when the system adds a new file, the file that ended in zero changes to one, and the number for all other files increases by one.
  3. Select Files to open the Error Log Directory pop-up that displays a directory listing for the system and Tomcat logs. Select the blue link(s) to download the system and/or Tomcat log files.
  4. Increase the number in the Buffer Size field to view a larger portion of the selected file, or decrease the number to view a smaller portion of the selected file. The system displays the full File Size of the file above the contents field. This allows you to know whether you are viewing the complete file or only a portion of the file.
  5. Select Download after selecting a file from the File drop-down to download the file. Selecting this button triggers a download prompt for the Error Log file that is currently selected.
  6. Select Refresh to view the error log details in the Log Detail section of the page.
    • The system displays the file starting from the bottom, which contains the most recent errors.
    • If you increase the buffer size to view more of the log, it will take longer to display the contents of the file.
  7. The system will display an error message instead of the log file contents under the following conditions:
    • The log file feature is not enabled in the Startup File page. If this is the case, contact a System Administrator to initialize this feature.
    • The path to the location of the error logs defined in the Startup File is incorrect or does not exist. If this is the case, contact System Administrator to enter or correct the path to the log file location in the Startup File page.

Database Tab

Viewing Database Actions

  1. Enter text in to the Server field to filter by the server where the error occurred.
  2. Enter text in to the Exception Type field to filter on the type of exception that occurred.
  3. Select the Only show errors with no exception checkbox to have the filter ignore the Exception Type field and only show the errors with no exception.
  4. Select the Do not show CSRF attack errors checkbox to have the filter ignore the “potential cross-site request forgery (CSRF) attack thwarted” errors. They won't display in the log when the checkbox is selected. This error may appear when an alternate database is used. Navigate to AdminCenter > System Setup > System Defaults > Miscellaneous Settings tab and set the Error Log Type setting to File and Database to see this option.
  5. Enter text in to the Message Content field to filter on the body text of the error message.
  6. Enter a date and time in the format MM/DD/YYYY HH:MM AM/PM in the Start and End fields, or select a date from the calendar view by selecting the calendar icon located next to the fields. Select Now to enter the current date and time. Select Clear to clear the date and time fields. The date/time filters items on the time when the error occurred.
  7. The Database table displays the Triggered By, Server, Event Date/Time, Exception Type, and Message columns.
    • Triggered By: Displays either the name of the user or the host, or the System, Patient, or Orchard Superuser, depending on who or what triggered the error.
    • Server: Displays the name of the server where the error was triggered.
    • Event Date/Time: Displays the date and time that the error occurred. This is the default sorted column. The column will now sort the entries to be newest first.
    • Exception Type: Displays the exception that triggered the error, or None if the error was not triggered by an exception.
    • Message: Displays the full text of the message as it would appear in the Error Log file. Startup error messages are never recorded in the database.