Capacity scan return codes

Edit online

If the capacity scan fails, an error code that indicates why the scan failed is returned. Check what is the possible cause of scan failure that is indicated by each code and how to solve the problem.

Locating the return codes

  • On computers where the BigFix® client is installed

    If the capacity scan fails, first check whether the return code is related to the scanner, or to running the checkCapacityScanOutput.vbs script. If the log refers to the script, the return code is specific for the script. It indicates that the capacity scan results are incomplete. The problem is usually solved after the next scan or after the upgrade of the scanner to the latest version.

    Check for the error codes:
    • The scanner error codes for capacity scan are written in the BigFix client logs. The logs are stored in the following locations:
      • UNIX /var/opt/BESClient/__BESData/__Global/Logs
      • Windows C:\Program Files (x86)\BigFix Enterprise\BESClient\__BESData\__Global\Logs
    • To check the error codes that are related to running the checkCapacityScanOutput.vbs script, check the Run Capacity Scan and Upload Results action in the BigFix console. On the Computers tab, identify the computer on which the action failed by checking its status. Double-click this computer. The error code is written in execution details.
  • On disconnected computers
    Return codes are available in the following locations.
    • In the scanner_status.yml file that is located in the following directory. It is also added to every scan results package.
      • UNIX <disconnected_scanner_install_dir>/work
      • Windows <disconnected_scanner_install_dir>\work
    • In the log.txt file that is by default in the following location.
      • UNIX <disconnected_scanner_install_dir>/logs
      • Windows <disconnected_scanner_install_dir>\logs

Capacity scan return codes

Table 1. Capacity scan return codes
Return code Possible cause and solutions
0 No errors.
1 Wrong arguments were used during the capacity scan. Ensure that the capacity scan is triggered with an official fixlet. In case of disconnected computers, reinstall or upgrade the scanner. For more information, see: Updating the disconnected scanner (disconnected scenario).
2 The scanner configuration file is corrupted. Reinstall or upgrade the scanner. For more information, see the following links.
5 The user that runs the scan does not have read permission to the scanner configuration file. Ensure that the user has the read and write permissions to the following directory.
  • On computers where the BigFix client is installed.
    • UNIX /opt/tivoli/cit/config/
    • Windows C:\Program Files\tivoli\cit\config
  • On disconnected computers.
    • UNIX <disconnected_scanner_install_dir>/cit/config
    • Windows <disconnected_scanner_install_dir>\cit\config
8 Scanner internal error occurred. Gather scanner logs and contact IBM Support. By default, the log files are in the following directory.
  • On computers where the BigFix client is installed.
    • UNIX /usr/ibm/tivoli/common/CIT/logs or /var/ibm/tivoli/common/CIT/logs
    • IBM i /etc/cit/logs
    • Windows C:\Program Files\ibm\tivoli\common\CIT\logs
    If the logs are not in the default directory, check the value of the common_trace_path parameter in the following file for information about the location of the logs:
    • UNIX /opt/tivoli/cit/config/Cit.properties
    • Windows C:\Program Files\tivoli\cit\config\Cit.properties
  • On disconnected computers.
    • UNIX <disconnected_scanner_install_dir>/logs
    • Windows <disconnected_scanner_install_dir>\logs
11 Scan output file or directory is read only. Ensure that the scan output file or directory is writable. By default, the directory is in the following location.
  • On computers where the BigFix client is installed.
    • UNIX /var/opt/BESClient/LMT/CIT
    • Windows C:\Program Files (x86)\BigFix Enterprise\BESClient\LMT\CIT
  • On disconnected computers.
    • UNIX <disconnected_scanner_install_dir>/work
    • Windows <disconnected_scanner_install_dir>\work
13 The scanner configuration file was not found. Reinstall or upgrade the scanner. For more information, see the following links.
18 One of the scanner files could not be open. Ensure that the administrator or root of the computer on which the problem occurred has the read and write permissions to the following files.
Scanner configuration file CitHWConfig.xml, scanner properties file Cit.properties, and scanner trace file CitTrace.properties, which by default are in the following directory.
  • On computers where the BigFix client is installed.
    • UNIX /opt/tivoli/cit/config/
    • Windows C:\Program Files\tivoli\cit\config
  • On disconnected computers.
    • UNIX <disconnected_scanner_install_dir>/cit/config
    • Windows <disconnected_scanner_install_dir>\cit\config
21 The scanner configuration file is corrupted. Reinstall or upgrade the scanner. For more information, see the following links.
49 The user that runs the scan does not have the read permission to the scanner properties file Cit.properties. Ensure that the administrator or root of the computer on which the problem occurred has the read permissions to this file. By default, the file is in the following directory.
  • On computers where the BigFix client is installed.
    • UNIX /opt/tivoli/cit/config/
    • Windows C:\Program Files\tivoli\cit\config
  • On disconnected computers.
    • UNIX <disconnected_scanner_install_dir>/cit/config
    • Windows <disconnected_scanner_install_dir>\cit\config
54 The scan file cannot be compressed. Ensure that the administrator or root of the computer on which the problem occurred has the read and write permissions to the following directory.
  • On computers where the BigFix client is installed.
    • UNIX /var/opt/BESClient/LMT/CIT
    • Windows C:\Program Files (x86)\BigFix Enterprise\BESClient\LMT\CIT
  • On disconnected computers.
    • UNIX <disconnected_scanner_install_dir>/work
    • Windows <disconnected_scanner_install_dir>\work
127 Content of the scan results file is incorrect. Wait for the next scheduled capacity scan. If the problem repeats three times in a row, contact IBM Support.

Return codes greater than 128 or 256

Unix Some return codes are triggered by problems that are signaled by the operating system. These are the return codes greater than 128 in case of bash and 256 in case of ksh. To check what is the system signal, use the following calculations:
  • For bash: return code - 128 = operating system signal
  • For ksh: return code - 256 = operating system signal
To identify the issue, check the meaning of the signal in the operating system documentation.
The following table presents the list of the most common return codes, their possible cause and solution.
Table 2. Scanner return codes greater than 128
Return code Signal Possible cause and solution
134 6 - SIGABRT There might not be enough memory available for the process to work. Increase the memory limit for this process by changing ulimit for data seg size: ulimit -d. If the problem persists, contact IBM Support.
138 10 - SIGBUS There is not enough disk space on the computer. Free some disk space. If the problem persists, ensure that you use the latest version of the scanner.
139 11 - SIGSEGV There might not be enough memory available for the process to work. Increase the memory limit for this process by changing ulimit for data seg size: ulimit -d. If the problem persists, contact IBM Support.

Return codes related to the checkCapacityScanOutput.vbs script

Table 3. Return codes linked to the checkCapacityScanOutput.vbs script
Return code Possible cause Solution
Windows Other operating systems
1 A general VBS script error. The Windows Script Host could be disabled. n/a Enable Windows Script Host.
2 ComponentID is missing the SerialNumber attribute in capacity scan output file. Capacity scan output file is missing the PhysicalProcessor section. Update the scanner to the latest version. For more information, see: Installing the scanner (BigFix scenario).
3 SerialNumber attribute in the capacity scan output file does not contain any value. Capacity scan output file is missing the OperatingSystem section.
4 Capacity scan output file is missing the PhysicalProcessor section. Capacity scan output file is missing the Lpar section.
5 Capacity scan output file is missing the OperatingSystem section. n/a
6 Capacity scan output file is missing the Lpar section. n/a
7 Capacity scan output file is missing the ComponentID section. Capacity scan output file is missing the ComponentID section.