clverify.log file

The verbose output is saved to the /var/hacmp/clverify/clverify.log file. The log file is rotated; this helps you and IBM® Support obtain a history of what configuration changes have been made when you need to determine the root cause of a problem.

Ten copies of the log are saved, as follows:

drwxr-xr-x   3 root     system1024 Mar 13 00:02 .
drwxr-xr-x   6 root     system 512 Mar 11 10:03 ..
-rw-------   1 root     system165229 Mar 13 00:02 clverify.log
-rw-------   1 root     system165261 Mar 12 17:31 clverify.log.1
-rw-------   1 root     system165515 Mar 12 15:22 clverify.log.2
-rw-------   1 root     system163883 Mar 12 15:04 clverify.log.3
-rw-------   1 root     system164781 Mar 12 14:54 clverify.log.4
-rw-------   1 root     system164459 Mar 12 14:36 clverify.log.5
-rw-------   1 root     system160194 Mar 12 09:27 clverify.log.6
-rw-------   1 root     system160410 Mar 12 09:20 clverify.log.7
-rw-------   1 root     system160427 Mar 12 09:16 clverify.log.8
-rw-------   1 root     system160211 Mar 12 09:06 clverify.log.9

You can redirect the clverify.log file to write to a different location using the standard PowerHA SystemMirror logfile redirection mechanism. If the clverify.log file is redirected to a different location, the location of all the data saved in the subdirectories in the path /var/hacmp/clverify moves along with it. However, pre-existing data under /var/hacmp/clverify is not automatically moved if the clverify.log is redirected.