8.4.1 Details of how to collecting data
The following shows how to collect data when a problem occurs.
- Organization of this subsection
(1) Collecting data for troubleshooting in Windows
(a) Execute the data collection tool
JP1/AJS3 for Cloud Service Applications provides the data collection tool (jajs_log.bat).
Use this tool if you have not changed the output destinations of log files and other data from the defaults, or if you do not need to collect data other than the data collected by default.
The following shows examples of executing the data collection tool:
C:\Program Files\Hitachi\JP1AJS3CSA\tools\jajs_log.bat
By default, the results of executing the data collection tool are output under %TEMP%\jp1ajs2\backlog. Back up these folders.
When you use the data collection tools in a cluster system, you can collect data by specifying a logical host name. The data collection tools also provide options for limiting the amount of data that is collected.
For details on the data collection tools, see jajs_log.bat (Windows only) in 7. Commands.
- Important
-
When you execute the data collection tool, you must open the Command Prompt window as an administrator. If you are not an administrator, UAC will frequently open a confirmation dialog box.
(b) Check Windows event logs
Check Windows event logs in the Event Viewer pane of Windows. Also, write the logs to the file.
(c) Obtain a dump file
If a STOP error occurs in Windows or if an application crashes, you might have to obtain dump files (a memory dump and a crash dump) and a problem report.
The following describes how to obtain a dump file and a problem report.
■ How to obtain a dump file
The dump files output during the problem should be collected manually. However, in order to output a dump file when a problem occurs, it is necessary to configure the output beforehand.
Follow the procedure below to configure the dump file output.
• Memory dump output setting procedure
-
In Control Panel, click System.
The System dialog box opens.
-
Click Advanced systems settings.
The System Properties dialog box opens.
-
Click Settings button in Startup and Recovery on Advanced tab.
The Startup and Recovery dialog box opens.
-
Select the Complete memory dump in the Write debugging information, and specify the output destination file in Dump file.
Complete Memory Dump may not be displayed depending on the size of the installed memory. In that case, select Kernel Memory Dump.
- Cautionary note
-
The memory dump size depends on the real memory size. The larger the physical memory installed, the larger the size of the memory dump. Allocate enough disk space to collect a memory dump. Dor details see Microsoft documentation.
• Crash dump output setting procedure
If a problem occurs, you may need a crash dump (a file containing debug information at the time of the problem). Windows registry information must be set in order to output a crash dump. For detailed setting information, refer to Microsoft's Windows Error Reporting (WER) related support technical information. When setting, set to output complete dump information.
- Cautionary note
-
Crash dumps are output not only when JP1 crashes, but also when other application programs crash. In addition, when crash dumps are output, the amount of disk space is used up accordingly. Allocate sufficient disk space if you want to output crash dumps.
(d) Collect problem reports
You can detect the problem on the machine and investigate solutions for each problem. If a process on the JP1/AJS for Cloud Service Applications server stops due to an application error, follow the steps below to collect a problem report.
-
Right click Windows Start, click Run in Windows, enter wercon in the text box, and click OK.
The Problem Reports and Solutions dialog box is displayed.
-
On the left pane, click View Problem History.
The problems history will be listed.
-
Double-click the applicable problem.
Details about the problem report appear.
-
Click Copy to clipboard.
-
Copy the text into a text editor, and save the file.
Use the problem report text file as data for investigating the failure.
(e) Check the status of processes
Check the operating status of the JP1/AJS3 - Manager process at the connection destination in the Processes tab of the Windows Task Manager window.
For details about the JP1/AJS3 - Manager process, see Processes in the manual JP1/Automatic Job Management System 3 Troubleshooting.
(f) Check the operation data
For the problem that has occurred, check the operation data and record it. You need to check the following information:
-
Details about the operation
-
Time that the problem occurred
-
Machine configuration (the version of each OS, host name, JP1/AJS3 for Cloud Service Applications, JP1/AJS3 - Manager and JP1/AJS3 - Agent configuration)
-
Whether the problem is reproducible
-
Login user name for the Windows host using JP1/AJS3 for Cloud Service Applications
(g) Collect error information displayed on the screen
Make hard copies of the following:
-
Windows on the screen when an application error has occurred
-
Error message dialog box (and display the displayed information when a details button (if there is one) is clicked)
(h) Other information
Collect other necessary information.
-
Contents of System Information in Help and Support
Print the System Information from Help and Support.
(2) Collecting data for troubleshooting in Linux
(a) Execute the data collection tool
JP1/AJS3 for Cloud Service Applications provides the data collection tool (jajs_log).
Use this tool if you have not changed the output destinations of log files and other data from the defaults, or if you do not need to collect data other than the data collected by default.
The following shows examples of executing the data collection tool:
/opt/jp1ajs3csa/tools/jajs_log
By default, the results of executing the data collection tool are output under /tmp/jp1ajs2/trouble.
When you use the data collection tools in a cluster system, you can collect data by specifying a logical host name. The data collection tools also provide options for limiting the amount of data that is collected.
For details on the data collection tools, see jajs_log (Linux only) in 7. Commands.
(b) Obtain the contents of the core file
Obtain the contents of the core file if the file has been output.
The core file is output to one of the following directories:
-
User home directory
-
Current directory in which the command was executed
(c) Check the status of server processes
Use the ps command to check the operating status of processes.
(d) Check the operation data
For the problem that has occurred, check the operation data and record it. You need to check the following information:
-
Details about the operation
-
Time that the problem occurred
-
Machine configuration (the version of each OS, host name, JP1/AJS3 for Cloud Service Applications, JP1/AJS3 - Manager and JP1/AJS3 - Agent configuration)
-
Whether the problem is reproducible
-
Login user name for the Linux host using JP1/AJS3 for Cloud Service Applications
(e) Collect error information displayed on the screen
Make hard copies of the following:
-
Windows on the screen when an application error has occurred
-
Error message dialog box (and display the displayed information when a details button (if there is one) is clicked)