10.8 Viewing Summaries of Failed or Incomplete Events from the *.out Log Files

In OES 11 SP2 and later, you can use the DotOutParser utility (/opt/novell/ncs/bin/dotoutparser.pl) print summaries of failed or incomplete events that have been recorded in a specified /var/opt/novell/log/ncs/<resource_name>.<script>.out log file. It also prints output (if any) from any commands that failed or got stuck. It optionally includes line numbers, so you can easily refer the summary output to the source lines in the *.out file. The higher the level of verbosity you specify, the more information you get in the summary output. By default, it prints the entries with plus (+) variable assignments. See Section A.5, DotOutParser Utility.

  1. Log in to the node as the root user.

  2. Copy the /var/opt/novell/log/ncs/<resource_name>.<script>.out log files of interest to a working location on the node.

  3. At a terminal console, enter

    /opt/novell/ncs/bin/dotoutparser.pl [-v|-vv|-vvv|-vvvv] /tmp/<resource_name>.<script>.out

    For example:

    /opt/novell/ncs/bin/dotoutparser.pl -v /tmp/POOL_09_SERVER.load.out

Fri May  3 11:51:59 2013 (#1):
2: + exit_on_error nss /poolact=POOL_09
9: + return 0
10: + exit_on_error ncpcon mount VOL_092=237
25: + return 0
26: + exit_on_error ncpcon mount VOL_091=238
41: + return 0
42: + exit_on_error add_secondary_ipaddress 192.168.1.9
94: + return 0
95: + exit_on_error ncpcon bind --ncpservername=CLUSTER1_POOL_09_SERVER --ipaddress=192.168.1.9
97: ++ ncpcon bind --ncpservername=CLUSTER1_POOL_09_SERVER --ipaddress=192.168.1.9
98: ... Executing " bind"
99:
100: Cannot bind server, failure reason = -632
101:
102: ... FAILED completion [elapsed time = 20 Seconds 2 msecs 671 usecs]
107: + exit 1