Go to main content
Oracle® Fabric OS 1.0.2 Administration Guide

Exit Print View

Updated: November 2016
 
 

Troubleshoot With System Log Files

You can gather information from the fabric and some host information, and compile the information into compressed files. You can then send these files to Oracle Customer Support for diagnosis. Fore more information, see Types of Log Files. You can perform this task using either the CLI or the GUI. For the GUI procedure, refer to Collect Device Log Files in Oracle Fabric Manager 5.0.2 Administration Guide. This procedure is for the CLI.

  1. View the installed software.
    [OFOS] show software
  2. Redirect content to an output file.

    The redirection switch ( >) sends the current show tech-support command contents to an output file, which can be sent to Oracle Customer Support. There is no progress indicator or completion message. When the command prompt returns, the command has completed.

    [OFOS] show tech-support > July2016
  3. Gather log files.

    Use any of the following options:

    -files output-file -all
    get log-files output-file -noarchives
    get log-files output-file -nocores
    get log-files output-file -silent

    This example shows how to gather all available files, logs, and cores, as well as the output of the show tech-support command. These files are placed into a gzipped tar file, which you can send to Oracle Customer Support.

    [OFOS] get-log-files -all
    copying /log/cli.log...
    copying /log/createdb.log...
    copying /log/daemon.log...
    copying /log/dumpster.log...
    copying /log/ib.log...
    copying /log/install.log...
    copying /log/kern.log...
    copying /log/osm.log...
    copying /log/postgresql.log...
    copying /log/syslog.log...
    copying /log/upgrade.log...
    copying /log/upgrade_sw.log...
    copying /log/user-debug.log...
    copying /log/user-debug_old.log...
    copying /log/user.log...
    copying /log/xdsd.log...
    copying /log/xms.log...
    copying /log/createdb.log.1.gz...
    copying /log/dmesg.1.gz...
    copying /log/dmesg.2.gz...
    copying /log/dmesg.3.gz...
    copying /log/dmesg.4.gz...
    copying /log/ib.log.1.gz...
    copying /log/ib.log.2.gz...
    copying /log/ib.log.3.gz...
    copying /log/ib.log.4.gz...
    copying /log/ib.log.5.gz...
    copying /log/osm.log.1.gz...
    copying /log/osm.log.2.gz...
    copying /log/postgresql.log.1.gz...
    copying /log/postgresql.log.2.gz...
    copying /log/syslog.log.1.gz...
    copying /log/user-debug.log.10.gz...
    copying /log/user-debug.log.1.gz...
    copying /log/user-debug.log.2.gz...
    copying /log/user-debug.log.3.gz...
    copying /log/user-debug.log.4.gz...
    copying /log/user-debug.log.5.gz...
    copying /log/user-debug.log.6.gz...
    copying /log/user-debug.log.7.gz...
    copying /log/user.log.8.gz...
    copying /log/user.log.9.gz...
    copying /log/wtmp.1.gz...
    copying /log/coredumps/dmsg_iocard-8_ts67_0...
    copying /log/coredumps/dmsg_iocard-8_ts68_0...
    copying /log/coredumps/dmsg_iocard-8_ts74_0...
    copying /log/coredumps/dmsg_iocard-8_ts86_0...
    copying /log/coredumps/mimm.1727.core...
    *** output file is xsigo-logs.tar.gz (49.12M)
    You can use the 'file copy' command to transfer it off the Oracle system

Related Information