14.3.30 snapshot (collects logs, settings, hardware information, and network information)

(1) Description

This subcommand collects the files listed below and saves them as archive files.

Note that files with the extensions .tar, .tar.gz, and .tgz are excluded.

• EADS log information

  • Active EADS servers' thread dumps

  • Files in the directory specified in the eads.logger.dir parameter in the server properties

    Note that eads_command_* files (*: any string of zero or more characters) are excluded.

  • eads_command_* files (*: any string of zero or more characters) directly under the directory specified in the eads.command.logger.dir parameter in the command properties

  • eads_command_* files (*: any string of zero or more characters) directly under the maintenance directory in the directory specified in the eads.command.logger.dir parameter in the command properties

  • management-directory/hs_err_pid*.log (*: any string of zero or more characters)

    Note: This is an output file name for a JavaVM error report file.

• EADS settings

  • Function property files (property files under management-directory/app)

  • Property files (files under management-directory/conf)

  • Management directory configuration information (management-directory/logs/snapshot_info/eads_info/eads_info_ls.txt)

  • List of cache data files (management-directory/logs/snapshot_info/cache_file_info/eads_data_cache-name_cache-property-file-sequence-number.txt)

  • List of cache information files (management-directory/logs/snapshot_info/cache_file_info/eads_info cache-name.txt)

  • List of cache index files (management-directory/logs/snapshot_info/cache_file_info/eads_index_cache-name.txt)

• Hardware and network information

  • OS version information (management-directory/logs/snapshot_info/eads_info/eads_info_version.txt)

  • CPU information (management-directory/logs/snapshot_info/eads_info/eads_info_cpu.txt)

  • Memory information (management-directory/logs/snapshot_info/eads_info/eads_info_memory.txt)

  • Disk information (management-directory/logs/snapshot_info/eads_info/eads_info_df.txt)

  • Network connection information (management-directory/logs/snapshot_info/eads_info/eads_info_netstat.txt)

  • Kernel parameter net.core information (management-directory/logs/snapshot_info/eads_info/eads_info_netcore.txt)

  • Correspondence between host IPs and IP addresses (/etc/hosts file)

  • Network interface information (management-directory/logs/snapshot_info/eads_info/eads_info_ifconfig.txt)

  • System resources limitation information (management-directory/logs/snapshot_info/eads_info/eads_info_ulimit.txt)

Note that a gz file is output under the directory specified in the eads.logger.dir parameter in the server properties.

If the eads.logger.dir parameter is not specified in the server properties, the file is output under management-directory/logs.

A file name is in the following format:

snapshot_[EADS-server-name]_[YYYYMMDDhhmmss].tar.gz

Legend:

YYYYMMDDhhmmss: Command execution date and time

YYYY: year, MM: month, DD: day, hh: hour (00 through 23), mm: minute, ss: second

To Page Top

(2) Rules

• This subcommand can be executed regardless of the status of the cluster or the EADS servers.

• If the -sd or --safedump option is specified and the cluster status is available (AVAILABLE) or partically available (PARTIALLY_AVAILABLE), this subcommand can be executed only if the status of each target EADS server is one of the following:

  • Initialized

  • Running

  • Closed

  • Isolated

• If the -sd or --safedump option is specified and the cluster status is unavailble (NOT_AVAILABLE), this subcommand can be executed if a target EADS server is in the following status:

  • Isolated

• When the -fd or --forcedump option is specified, the subcommand can be executed on EADS servers that are in any of the following statuses, regardless of the cluster's status:

  • Initializing

  • Initialized

  • Running

  • Closing

  • Closed

  • Isolated

  • Stopping

To Page Top

(3) Format

eztool snapshot [-sd|-fd]

To Page Top

(4) Options and arguments

To Page Top

(5) Return code

0: Normal termination

Other than 0: Error

To Page Top

(6) Notes

• A gz file created by this subcommand is not deleted automatically. There is no limit to the number of files that can be created. If you execute this subcommand periodically, pay attention to the amount of disk space used.

• If this subcommand's processing does not terminate, the file system might be corrupted. In such a case, forcibly terminate the subcommand, and then check the file system for any corruption.

• If the subcommand does not have read permission for the files to be collected, the files cannot be archived.

• While this subcommand is executing, the logs shown below are output to the message log file that is output during command execution. These logs are used internally by EADS to collect information. They are not available for use by the user.

  • When no options are specified

    snapshot, -v, -t, 60

    snapshot --listconf, -s, -t, 60

  • When the -fd option is specified

    snapshot, -v, -t, 60

    snapshot, -s, -v, -t, 60

    snapshot --listconf, -s, -t, 60

  • When the -sd option is specified

    snapshot, -v, -t, 60

    snapshot, -s, -v, -t, 60

    snapshot, --lock, -t, 60^#

    snapshot, --unlock, -t, 60^#

    snapshot --listconf, -s, -t, 60

    #: The log is not output for an isolated EADS server.

• When this subcommand is executed, the directories and files listed below are created temporarily. These directories and files are deleted after archive files have been output. If this deletion processing fails, delete them manually as necessary.

  • EADS server thread dumps immediately under management-directory/logs/

    Once the subcommand has output archive files, it deletes thread dumps that were in existence before the subcommand executed. These thread dumps are deleted even if the -sd or --safedump option or the -fd or --forcedump option is not specified. The archive files also contain past thread dumps. If you need a thread dump after you have executed the subcommand, expand the archive files to obtain the thread dump.

  • snapshot_info directory, that is created directly under management-directory/logs/ and the files directly under the snapshot_info directory

To Page Top