Trace timeout

If you do not stop a trace manually, the trace runs until its trace duration expires. The default trace duration is 10 minutes, but you can set a different value in the mmprotocoltrace command.

Each node that participates in a trace starts a timeout process that is set to the trace duration. When a timeout occurs, the process checks the trace status. If the trace is active, the process stops the trace, writes the file location to the log file, and exits. If the trace is not active, the timeout process exits.

If a trace stops because of a timeout, you can use the mmprotocoltrace status command to find the location of the trace log file. The command gives an output similar to the following:

[root@ces5040-41 ~] mmprotocoltrace status
Trace ID:           f5d75a67-621e-4f09-8d00-3f9efc4093f2
State:              DONE
Protocol:           smb
Start Time:         15:24:30 25/09/19
End Time:           15:34:30 25/09/19
Trace Location:     /tmp/mmfs/smb.20190925_152430.trc
Origin Node:        ces5040-41.localnet.com
Client IPs:         10.0.100.42, 10.0.100.43
Trace results file: ces5040-41.localnet.com:/tmp/mmfs/smb.trace.20190925_152552.tar.gz
Syscall:            False
Syscall Only:       False
Nodes:
      Node Name:            ces5040-41.localnet.com
      State:                DONE

      Node Name:            ces5040-42.localnet.com
      State:                DONE

      Node Name:            ces5040-43.localnet.com
      State:                DONE