Monitoring the scan progress
Available from 9.2.5. In case of any problems with the software scan, you can check whether the scan was started or completed, and view some extra information about the scanned directories.
Log files
The run_hw.sh
and run_sw_and_pack.sh
commands are
the_console.sh
wrappers , and they redirect the script output into the
run_hw_std.log
and run_sw_and_pack_std.log
files. The default size
limit of a single log file is 1024 bytes. The limit can be changed in the
configure_scan.sh
file. To change the size limit provide a new
LIMIT
value. If during the next scan the log files exceed the size limit, the
existing files are renamed to run_hw_std.log.1
and
run_sw_and_pack_std.log.1
. However, only up to two such files can exist per
command. Therefore, if run_hw_std.log.1
and
run_sw_and_pack_std.log.1
already exist, the oldest log files are removed.
Checking the scanner version
To monitor the scan progress, you must have the scanner in version 2.8.0.0001, or higher. To check the current version, open the /etc/cit/cit.ini file.
CIT_Version = 2.8.0.0001
Checking the initiated scans
Information about the started and completed scans is written in the /etc/cit/logs/traceCIT.log file.
16/07/04 15:18:36 E [main.C] seMain: 308 IMPORTANT: ---START--- Software scan started. CIT Version = '2.8.0.0001'
16/07/04 15:20:14 E [cache.C] 2800 IMPORTANT: File system access on '/' (drive: '/:', type: 2, fs: 'os400fs')
16/07/04 15:22:02 E [cache.C] 2835 IMPORTANT: (OK) File system access on '/' (drive: '/:', type: 2, fs: 'os400fs')
16/07/04 15:22:02 E [cache.C] 2800 IMPORTANT: File system access on '/QSYS.LIB' (drive: '/QSYS.LIB:', type: 2, fs: 'qsysfs')
16/07/04 15:25:24 E [cache.C] 2835 IMPORTANT: (OK) File system access on '/QSYS.LIB' (drive: '/QSYS.LIB:', type: 2, fs: 'qsysfs')
...
16/07/04 15:41:31 E [main.C] seMain: 483 IMPORTANT: ---STOP--- Software scan finished with return code=0
Checking the scanned directories
You can check which directories are currently being scanned in the /etc/cit/logs/traceCIT_scanned_dirs.log file.
2016-07-04T15:20:14 '/'
2016-07-04T15:20:14 '/iso'
2016-07-04T15:20:14 '/maestro'
...
2016-07-04T15:25:23 '/QSYS.LIB/QAUTOMON.LIB'
If the scan is taking too long to complete or hangs on a particular directory, you can stop it by aborting the job that is running the scan. Then, exclude the directory from scanning, and repeat the scan.