When requesting investigation by Fujitsu technical support as part of the action taken in response to an output message, login using root permissions and collect the following resources.
Collect resources in a state that is as close as possible to the state when the phenomena occurred.
In the information collected after the phenomena has ended or the system has been restarted, the state of the system has changed, and this may make investigation impossible.
Output results of the resource collection tool (pdfssnap.sh and the fjsnap command)
Use pdfssnap.sh and the fjsnap command to collect the troubleshooting data. Collect from all servers that shared the DFS, as far as possible.
Refer to "Executing pdfssnap.sh".
Refer to "Executing fjsnap".
Crash dump
If there was a panic on the server, for example, also collect the crash dump file as part of the troubleshooting data. Refer to "Collecting the crash dump" for details.
Execution results of the pdfsck command
Collect if there is a mismatch in the DFS and it needs to be restored. Refer to "Execution results of the pdfsck command".
Collecting the core image for the daemon
As part of the actions in response to DFS error messages, it may be necessary to collect core images as they relate to various daemons. Refer to "Collecting the core image for a daemon" for details.
When it is necessary to send the troubleshooting data quickly, collect the following as the initial troubleshooting data:
Output results of the resource collection tool (pdfssnap.sh)
/var/log/messages*
After collecting the resources for initial investigation, ensure that other resources are also collected.
Log in to the server where the data will be collected using root permissions.
Execute pdfssnap.sh.
# /etc/opt/FJSVpdfs/bin/pdfssnap.sh <Enter>
Note
With pdfssnap.sh, the troubleshooting data is output to the directory where the command is executed. For this reason, at least 100 MB of free space must be available in the file system that will execute the command.
Log in to the server where the data will be collected using root permissions.
Execute the fjsnap command.
# /opt/FJSVsnap/bin/fjsnap -a anyFileName <Enter>
This is normally saved in a folder named "/var/crash/time of panic" when the server is started after a panic. Collect on all servers where a system panic has occurred.
# pdfsck -N -o nolog blockParticularFileForTheRepresentativePartition <Enter>
Collect core images on all DFS admin servers.
The procedure is explained below using the example of collecting the core image of the pdfsfrmd daemon.
Determining the process ID
Identify the process ID by using the ps command. Change the argument of the grep command if the target is other than the pdfsfrmd daemon.
# /bin/ps -e | /bin/grep pdfsfrmd <Enter> 5639 ? 00:00:25 pdfsfrmd
The beginning of the output is the process ID of the pdfsfrmd daemon. This is not output if the pdfsfrmd daemon is not running. Collect on another server if it is not operating.
Information
When collecting the MDS core image, specify pdfsmg in the argument of the grep command.
See
Refer to the online Help for information on the ps and grep commands.
Getting the core image
Collect the core image of pdfsfrmd to the /var/tmp/pdfsfrmd_node1.5639 file by using the gcore command. After that, compress the file with the tar command.
# /usr/bin/gcore -o /var/tmp/pdfsfrmd_node1 5639 <Enter> gcore: /var/tmp/pdfsfrmd_node1.5639 dumped # /bin/tar czvf /var/tmp/pdfsfrmd_node1.5639.tar.gz /var/tmp/pdfsfrmd_node1.5639 <Enter> # /bin/ls -l /var/tmp/pdfsfrmd_node1.5639.tar.gz <Enter> -rw-rw-r-- 1 root other 1075577 June 12 16:30 /var/tmp/ pdfsfrmd_node1.5639.tar.gz
See
Refer to the online Help for information on the tar command.
