This page describes features that allows you to keep track of the resources being used by EASA Server together with any diagnostic messages from the EASA Server.
You can see how EASA is running on the EASA Server by selecting Diagnostics under the System menu while in Administrator mode. On the Diagnostics page, you can access five other pages:
Each of these pages will be described in more detail in the following sections.
On the Summary page, the computer resources being used by EASA are shown below the System Information heading. By default, the following values will be displayed under System Information:
Additional system resource values can be configured to be displayed under System Information by making use of Performance Logs defined in the Computer Management tool available in Windows. See Adding a System Resource Monitor Value for details.
The next section on the Summary page having the Throughput heading displays the following throughput values accumulated since EASA Server software was last started:
On the Server Output page, the diagnostics messages that are output from EASA on the EASA Server are shown in the box below the Server Output heading. This server output is made up of a variety of messages about such things as:
Many of the messages are time and date stamped to help track down when and why problems may have occurred on your EASA system. There are several actions available to you under the ‘Actions’ dropdown beneath the log window:
Tip: The messages shown on the Diagnostics page under the Server Output heading are stored in a text file called
server.txt in the
<SERVERDATA>/admin/logs folder. Older archived log files are also stored here with date stamps added to the file names.
Output from the HTML Server is also available from this page, and can be accessed via the radio buttons above the log window. This corresponds to the information from
On the Logging page, you have the ability to set the level or quantity of logging performed by EASA, which is stored in the server.txt file and displayed on the Server Output page described in the previous section. There are two different types of diagnostic messages that can be controlled on the Logging page, Queue messages and Web Page request messages. To change the logging level, just perform the following two steps:
This table lists all the system commands currently being run by EASA. These typically are associated with submitted EASAP processes being run either locally on the EASA Server acting as a compute server or via rsh commands to a remote compute server.
By pressing the Free Resources button, you initiate a request for the EASA Server to free up any computer memory that it no longer needs to be using. The information on the Free Resources page shows memory usage information before and after the memory free up process.
Under Thread Details you can see Current number of threads, Peak number of threads, Total started threads, Deadlocked Threads and Monitor-Deadlocked Threads. Many threads make up EASA. Their roles and how they work are not in the scope of this document and therefore they are for advanced users only. The Log Stacktraces button is used for printing all data related to threads into the server log (found under System → Diagnostics → Server Output → EASA Server).
Under All Threads, you can see a list of the current threads and their respective status.
Note: During normal operation, memory is also freed up by EASA automatically from time to time.
In addition to the default system resource values displayed on the Summary page under the Diagnostics selection, it is possible for you to monitor more system resource values by making use of Performance Logs defined in the Computer Management tool available in Windows.
Note: The procedures and functionality described in this section will not apply to EASA Servers running under Linux.
To add a new System Resource Monitor Value for display on the Summary page under the Diagnostics selection, you need to complete two separate procedures:
<SERVERDATA*>/admin/configwithin the EASA installation.
To create the new Counter Log in Windows XP, please follow the instructions given below:
Counter Log functionality in Windows 7 differs to Windows XP in that they are organized into Data Sets. However, we can still achieve the desired results with a few configuration options. To create the new Counter Log in Windows 7, please follow the instructions given below:
C:\perflogs, for simplicity). In order to keep a consistent file name for EASA to locate, we need to clear the Subdirectory name format field and unselect the Prefix subdirectory with computer name option. This will ensure that the log file is always in the same place – the root folder.
Now that the new counter log file has been initiated, you can proceed to adding an entry for the new monitor in the
System.properties file located under
<SERVERDATA>/admin/config in your EASA installation. To add the entry and complete the addition of the new System Resource Monitor Value, please follow the instructions given below:
System.propertiesfile in a text editor such as Notepad or Wordpad.
<text> is unique identifier such as a number,
<location_of_log_file> is the full path to the log file including the file name,
<column_number> is the number corresponding to the column containing the monitor value data in the log file, and
<title_shown_on_summary_page> is the text shown on the Summary page under the System Information heading.
easa.server.systemmonitor1=C\:/PerfLogs/cpu.csv,2,% CPU Time
System.propertiesfile and exit the text editor.