Server installation and upgrade logs

Installation and upgrade log files are in the same directories, because those processes are completed by using the same installer. If you encounter any problems while installing or upgrading the server, refer to those log files for more information about any occurring errors.

Log files

There are several log files that are created either during the installation or upgrade, or only when the process failed or completed successfully. Each path starts with a variable that is specific to the operating system. Those variables are explained below the table.

Table 1. Installation and upgrade log files
Installation Status	Windows	Linux
In progress	%USERPROFILE%\BFI_9.2.16 %USERPROFILE%\ia.log `BESclient_installation_directory`\LMT\BFI_upgrade.log	$HOME/BFI_9.2.16 $HOME/ia.log `BESClient_installation_directory`\LMT\BFI_upgrade.log
Failed	%USERPROFILE%\BFI_9.2.16_`timestamp`_`uniqueID`_logs.zip	$HOME/BFI_9.2.16_`timestamp`_`uniqueID`_logs.tar.gz
Successful	`installation_directory`\BFI_9.2.16_`timestamp`_`uniqueID`_logs.zip	`installation_directory`/BFI_9.2.16_`timestamp`_`uniqueID`_logs.tar.gz

%USERPROFILE%: Home directory of the user who installed the server, for example C:\Users\Administrator\.
Important: When you upgrade by using a Fixlet, the upgrade runs under the NT AUTHORITY\SYSTEM user whose default home directory is C:\Windows\System32\config\systemprofile\.

$HOME: Home directory of the user who installed the BigFix client, for example /root/.

Log file contents

To understand the root cause of installation and upgrade problems, review logs for messages with a severity level of WARN or ERROR. The following example shows a warning message.

<Message Id="CODIN0215W" Severity="WARN">
 <Time Millis="1381929782997"> 2013-10-16 15:23:02.997+02:00</Time>
 <Server Format="IP">NC040226.kraklab.pl.ibm.com</Server>
 <ProductI>dCOD</ProductI>d
 <Component>Install</Component>
 <ProductInstance></ProductInstance>
 <LogText><![CDATA[CODIN0215W The following ports are in use: 9081, . 
The installation process can be continued but the server will not be started. 
The server has to be started manually after resolving the ports conflict.]]></LogText>
 <Source FileName="com.ibm.license.mgmt.install.ia.common.CommunicationCommon" 
 Method="okToContinue"/>
 <TranslationInfo Type="JAVA" Catalog="userLocales.InstallMessageEWI" MsgKey="checkPorts">
 <Param><![CDATA[9081, ]]></Param></TranslationInfo>
 <Principal></Principal>
</Message>

To learn more about errors and return codes that can appear in the logs, go to Server installation and uninstallation return codes.