Log files for starting and stopping the server | IBM 51 specs

UNIX or Linux

$TIO_LOGS/uninstall

Log files for starting and stopping the server

Log files for starting and stopping the Tivoli Intelligent Orchestrator server are stored in the %TIO_LOGS% directory. Log files specific to WebSphere Application Server are located in the %WAS_HOME%\logs\server1 directory, where %WAS_HOME% is the default WebSphere Application Server home directory.

Table 5. Server startup and shutdown logs

File name	Location	Description

tio_start.log	Windows	This is the log file of the most
	Windows	recent startup of the Tivoli
	%TIO_LOGS%	recent startup of the Tivoli
	%TIO_LOGS%	Intelligent Orchestrator server.
		Intelligent Orchestrator server.
	UNIX or Linux	This log is overwritten each
	$TIO_LOGS	time the server is started.
		If startup happens with no
		errors, this file is very short. If
		there are errors, you might
		need to consult the
		WebSphere Application Server
		logs for additional
		information.

tio_stop.log	Windows	This is the log file of the most
	Windows	recent shutdown of the Tivoli
	%TIO_LOGS%	recent shutdown of the Tivoli
	%TIO_LOGS%	Intelligent Orchestrator server.
		Intelligent Orchestrator server.
	UNIX or Linux	This file is overwritten each
	$TIO_LOGS	time the server is stopped.

startServer.log	Windows	This is the log file for the
	%WAS_HOME%\logs\server1	startup of the WebSphere
	%WAS_HOME%\logs\server1	Application Server.
		Application Server.
	UNIX or Linux
	$WAS_HOME/logs/server1

stopServer.log	Windows	This is the log file for the
	Windows	shutdown of the WebSphere
	%WAS_HOME%\logs\server1	shutdown of the WebSphere
	%WAS_HOME%\logs\server1	Application Server.
		Application Server.
	UNIX or Linux	WebSphere is the last service
	$WAS_HOME/logs/server1	to stop when you shut down
		Tivoli Intelligent Orchestrator,
		so this log file is useful for
		verifying whether the
		shutdown completed.

SystemOut.log	Windows	This is the log file for
	Windows	WebSphere Application Server
	%WAS_HOME%\logs\server1	WebSphere Application Server
	%WAS_HOME%\logs\server1	output. You might want to
		output. You might want to
	UNIX or Linux	refer to this file when
	$WAS_HOME/logs/server1	WebSphere Application Server
		does not start.

46Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide

Image 58

IBM 51 manual Log files for starting and stopping the server, Unix or Linux

Contents

Problem Determination and Troubleshooting Guide Page Problem Determination and Troubleshooting Guide Page Contents Troubleshooting the agent Tivoli Common Agent Page Publications PrefaceWho should read this book Tivoli Intelligent Orchestrator library Prerequisite publications Related publications and resources Accessibility Accessing publications onlineOrdering publications Typeface conventions Tivoli software training Support informationConventions used in this book Monospace Introduction to troubleshooting Product and system overview Orchestrating provisioning Product comparisonTivoli Intelligent Orchestrator Tivoli Provisioning Manager Data center model Product architectureTivoli Intelligent Orchestrator components Policy engine Deployment engine Objective analyzerGlobal resource manager Automation packages Product maintenance Built-in troubleshooting featuresProblem classification Backing up the system Problem resolution Performing periodic checks and maintenanceClick Technical documentation on the left Problem determination methodologies Defining the problem Verifying whether the problem can be replicated Identifying the cause of the problemDetermining where the problem lies and what it is Checking whether the problem has occurred before Fixing the problem Troubleshooting the prerequisite installation DB2 Universal Database verification IBM Tivoli Directory Server verification Unix Windows LDAPInstallDirectory\var\ WebSphere Application Server verification Security.xml Sas.client.props Server.xmlJava.security SystemOut.log Secure Authentication Services Ldap Map Tivoli Intelligent Orchestrator resource references Applications Simple Object Access Protocol SoapHttp Transport Service Tcear Application Remote Method Invocation RMI Tivoli Intelligent Orchestrator installationStartup Complete Verifying subcomponent configuration Check the IBM Tivoli Directory Server schema Page Component-based problem determination Check the tioldap authentication Task-based problem determination Page Debug Using the available command line tools Accessing the knowledge basesTivoli Intelligent Orchestrator command line tools Wasadmin password ChangePassword.cmdPassword current ChangePassword.sh user DcmExport.cmd -d DcmQueryCommandt.cmdDcmQueryCommandt.sh OutputFilename IdeviceId RetrieveDetails.cmdRetrieveDetails.sh Repositoryname Siregister.cmdPackagelocation Repositorymountpoint Internaluserpassword CommandUpdateCredential.cmd WASAdminUser FileURL xmlImport.sh WebSphere Application Server command line toolsXmlImport.cmd fileURL FileURL fileURL IBM Tivoli Directory Server command line tools Name Location DescriptionPage Message ID format Log file typesMessage logs Code Subsystem Message text Message elementsMessage ID Explanation Trace logs Common Base Event logsPage Log locations Locating and configuring log filesLog directory files Log4j.prop Configuring logs with log4jLogging levels Windows Locating and configuring log files RollingFileAppender defaults Log level defaultsConfiguring log4j dynamically Preparing log files for review by IBM Tivoli Support ExamplePage Log files for the uninstall process Log files for product setupTivoli Intelligent Orchestrator log files Log files for starting and stopping the server Log files for the Web interface Deployment engine log files Workflow logs Logs for data collection and decision making Automation package logs This log file stores error Middleware prerequisite log files Installation log files for prerequisitesInstallation logs for individual prerequisites WebSphere Application Server Directory Server Runtime logs for prerequisitesWebSphere Application Server Linux and Solaris DB2 Universal Database Directory Server Tivoli Agent Manager Linux, you cannot create the user tioadmin Problems with installationCause Solution Microsoft Active Directory installation fails Environment variables not set for user tioadmin Cause On AIX, Linux, and Solaris Or, to uninstall silently Cause Solution Problems with loggingYou cannot log You cannot change your password Problems with workflows DB2 Universal Database creates a database state error Shell command error Resource temporarily unavailable Solution workflowLogExport tool $TIOHOME/tools Syntax for Unix Workflow does not install Example workflow log export Other common problems On Windows, Tivoli Intelligent Orchestrator does not start XML import does not work properly Capacity of the file system is not large enough Last line in the log is Solution Operating system requirements Excel requirements Common agents unable to communicate with the agent manager There is a maximum size for returnResult parameter storage Device Manager limitations Known report limitations Agent receives an Http Unauthorized 401 response codeRunning any report with too many objects selected fails Page Log files for the agent manager Troubleshooting the agent managerLocating the installation log files Packaging the log files Log file name Description Guid Locating the uninstallation log files Locating the remote registry logs Locating the DB2 Universal Database runtime logs Locating the runtime log filesLog File Description Verifying that the agent manager service is running Installation and uninstallation verificationsDetermining the version of agent manager Errors starting the agent manager application Verifying the installation of WebSphere Application ServerErrors starting the agent manager application server Verifying the connection to the registry Enabling tracing Task Value in Trace Specification text boxEnabling and disabling tracing Disabling tracing Ensure that Enable Trace is not checked Click OK Common problems Registration and communication failures As a Windows service Problems using the WebSphere Administrative ConsoleCannot start the WebSphere Administrative Console Using a Windows command StopServer server1 startServer server1 Page Contacting IBM Tivoli Software Support General data to collect for Tivoli Support Syntax PackageLog ZIP toolLocation Returned file Prerequisites Linux and UnixPage COPCOM001E The system cannot delete the VALUE0 file Tivoli Intelligent Orchestrator messagesCommon subsystem messages COPCOM003E The system cannot find the VALUE0 dcm policy COPCOM012E The server VALUE0 does not have a locale value COPCOM015E The system cannot get a Jndi context COPCOM016E The directory VALUE0 does not exist COPCOM024E The system cannot use the VALUE0 JMS destination COPCOM042E The system cannot read the VALUE0 XML file COPCOM040E The system failed to load the VALUE0 XML fileCOPCOM041E The system failed to parse the VALUE0 XML file COPCOM050E Application VALUE0 not found COPCOM061E The system cannot find customer VALUE0 COPCOM058E The system cannot find application tier VALUE0COPCOM059E The system cannot find a rule at position VALUE0 COPCOM063E The system cannot find the DCM object ID VALUE0 COPCOM071E The system cannot find the load balancer VALUE0 COPCOM082E The system cannot find power outlet VALUE0COPCOM083E The system cannot find power unit VALUE0 COPCOM075E The system cannot find NIC VALUE0 COPCOM090E The system cannot find the VALUE0 software stack COPCOM096E The system did not find the VALUE0 switch portCOPCOM097E The system cannot find the VALUE0 switch COPCOM091E The system cannot find the VALUE0 software state COPCOM115E There is not enough data to complete the task COPCOM124E a Telnet error occurredCOPCOM125E a Telnet error occurred COPCOM116E The operation timed out COPCOM143E a shell command error VALUE0 occurred COPCOM136E The system cannot find error VALUE0COPCOM140E An error occurred VALUE0 COPCOM155E The system cannot find the VALUE0 boot server COPCOM161E The system cannot find the resource VALUE0 COPCOM159E The system cannot find the VALUE0 access ruleCOPCOM158E The system cannot find the VALUE0 interface card COPCOM170E The system cannot find this route VALUE0 COPCOM195E The system cannot find the VALUE0 volume manager COPCOM194E The system cannot find the VALUE0 storage volumeCOPCOM191E The system cannot find the VALUE0 disk manager COPCOM203E The system cannot find the VALUE0 data path COPCOM197E The system cannot find the VALUE0 logical volumeCOPCOM198E The system cannot find the VALUE0 file system COPCOM204E The system cannot find the VALUE0 zone set COPCOM226E The VALUE0 server template is not valid COPCOM217E The system cannot create the output file VALUE0COPCOM219E The database cannot complete the query COPCOM230E The system cannot find the VALUE0 host platform COPCOM237E The system cannot find the VALUE0 software module COPCOM243E The system cannot find the VALUE0 router COPCOM269E The switch endpoint mode VALUE0 is not valid COPCOM274E The system cannot find the discoverable VALUE0 COPCOM278E The system cannot find the VALUE0 storage manager COPCOM282E Port VALUE0 is already connected to port VALUE1 COPCOM303E VALUE0 already exists COPCOM302E Port number VALUE0 is not uniqueCOPCOM305E The Vlan name cannot be null COPCOM321E The system cannot find the VALUE0 image COPCOM317E The system cannot find the VALUE0 image typeCOPCOM323E The policy type VALUE0 is not valid COPCOM353E The service with ID VALUE0 cannot be found COPCOM354E The offering with ID VALUE0 cannot be found COPCOM357E The Order of ID VALUE0 cannot be found COPCOM358E The service with name VALUE0 cannot be foundCOPCOM355E The scheduled task type VALUE0 is not valid COPCOM360E The subscription of ID VALUE0 cannot be found COPCOM378E AgentManager did not find the Agent ID VALUE0 COPCOM377E Internal Error Null AgentGUID was specifiedCOPCOM385E The system cannot find the report VALUE0 COPCOM400E No TCM Gateways were found for Hostname VALUE0 COPCOM395E The TCM object type VALUE0 was not foundCOPCOM396E The filter format is not valid. Filter VALUE0 COPCOM401E The endpoint lookup returned null for VALUE0 COPCOM408E The Endpoint subscriber VALUE0 does not exist COPCOM405E The Profile Manager is VALUE0COPCOM407E Profile VALUE0 is not a managed profile COPCOM417E The filter VALUE0 lacks a parent component COPCOM430E The instance permission VALUE0 is unknown COPCOM431E The instance access role VALUE0 is unknownCOPCOM432E The access domain VALUE0 is unknown COPCOM433E The domain role VALUE0 is unknown COPCOM457E An unknown event type VALUE0 occured COPCOM442E The type VALUE0 is not a valid filter typeCOPCOM443E The system cannot create the file VALUE0 COPCOM458E An unknown event consumer VALUE0 occured COPCOM465E a Security Group with name VALUE0 already exists COPCOM468E The SI image resource VALUE0 registers an errorCOPCOM473E The LCF installation directory is not specified COPCOM466E Bad SI package image format with VALUE0 COPCOM482E The Login Interval is not correct COPCOM480E The value for Http Disable must be a 0, 1, 2 orCOPCOM481E The value for Broadcast Disable must be a 0 or COPCOM494E Unable to connect to endpoint using RXA COPCOM502E The system cannot create the directory VALUE0 COPCOM499E Error copying file using RXA VALUE0COPCOM503E Error converting path VALUE0 to DOS style path COPCOM514E The database sequence VALUE0 does not exist COPCOM533E The DCM object VALUE0 cannot be updated COPCOM521E Unable to read xml config file VALUE0COPCOM532E The server VALUE0 cannot be accessed or updated COPCOM525E Cannot find DCM Property Id VALUE0 Deployment engine subsystem messages COPCOM539E Task VALUE0 Task Id VALUE1 failed COPDEX005E The VALUE0 logical operation does not exist COPDEX001E The system cannot get a Jndi contextCOPDEX002E The system cannot use the VALUE0 JMS destination COPDEX008E break cannot be used inside of a finally block COPDEX020E The system requires the VALUE0 attribute COPDEX033E Error code for unit tests onlyCOPDEX019E The condition VALUE0 is not valid COPDEX022E The ID VALUE0 is not an integer COPDEX041E a deployment error occurred COPDEX038E a database error occurred VALUE0COPDEX039E a configuration error occurred COPDEX040E a deployment engine exception occurred VALUE0 COPDEX063E An XML data parsing error VALUE0 occurred COPDEX060E a workflow XML parser error VALUE0 occurredCOPDEX062E a data insert error VALUE0 occurred COPDEX069E The system cannot process the data update VALUE0 COPDEX083E The input file VALUE0 is empty COPDEX081E The system cannot specify an input fileCOPDEX082E The system cannot find the input file VALUE0 COPDEX084E The operation type VALUE0 is not identifiedPage COPDEX127E The VALUE0 variable is already declared COPDEX129E a workflow compiler error occurred VALUE0COPDEX130E The deployment request id=VALUE0 was cancelled COPDEX128E The VALUE0 variable does not exist COPDEX141E The specified LDO VALUE0 is not found COPDEX140E The deployment request VALUE0 is not foundCOPDEX142E The specified workflow VALUE0 is not found COPDEX151E Duplicate permission VALUE0 for parameter VALUE1 COPDEX149E No such parameter VALUE0COPDEX150E Unknown instance permission VALUE0 COPDEX153E The size of input arrays are different COPDEX178E To do VALUE0 COPDEX170E The VALUE0 Java plug-in does not existCOPDEX176E The parameter VALUE0 cannot be null COPDEX183E DCM object VALUE0 does not have attribute VALUE1 Job Distribution Service JDS subsystem messages J2ee subsystem messages COPJEE009E This feature is not supported COPJEE032E The system cannot recognize the database type COPJEE035E The system cannot find the RSA credentials VALUE0 COPJEE055E No software stack is associated with VALUE0 COPJEE049E The operating mode VALUE0 is not validCOPJEE050E The specified resource pool VALUE0 is not valid COPJEE056E The requested object VALUE0 is already locked COPJEE068E The deployment request parameter VALUE0is missing COPJEE082E The system cannot load datasource VALUE0 COPJEE086E a monitoring configuration was not selectedCOPJEE093E The specified position is already occupied COPJEE106E The upgrade type is not valid COPJEE101E a user interface error occurred VALUE0COPJEE105E An error occurred VALUE0 COPJEE112E a power outlet already exists COPJEE167E The server ID is not valid COPJEE199E The upgrade type is not validCOPJEE201E Both objects must be of the type DcmObject COPJEE207E a discovery technology was not selected COPJEE232E The VALUE0 module type is not valid COPJEE272E Problem ID UIVALUE0 COPJEE271E UI Exception Problem ID UIVALUE0, user=VALUE1COPJEE240E The system cannot create the deployment plan COPJEE289E The deployment request ID VALUE0 does not exist COPJEE299E The system cannot realize the deployment planPage COPJEE333E The system cannot find DB driver VALUE0 COPJEE334E The access to DB driver VALUE0 is not allowedCOPJEE326E The system failed to delete deployment request COPJEE335E Instantiation of DB driver VALUE0 failed COPJEE351E The system cannot process the data update VALUE0 COPJEE345E Multiple Password credentials were returnedCOPJEE350E a data insert error VALUE0 occurred COPJEE356E a system error VALUE0 occurred COPJEE379E The workflow was already added COPPEZ008E The system cannot estimate Number of servers Policy engines subsystem messagesCOPPEZ005E The system cannot create the Snmp connection COPPEZ009E The system cannot open the VALUE0 file COPPEZ047E The data acquisition thread is not working COPPEZ042E VALUE0 is not a valid device typeCOPPEZ044E VALUE0 is not valid for a VALUE1 context COPPEZ049E VALUE0 is not a valid VALUE1 metric COPPEZ079E a resource broker error occurred COPPEZ073E An Snmp IO error occurredCOPPEZ077E An error VALUE0 occurred COPPEZ110E a task library lookup error occurred COPPEZ116E The endpoint label is null or empty Common agent subsystem messagesCOPPEZ115E The system cannot obtain a application tier ID COPTCA001E Cannot get proxy for interface on Agent VALUE0 TC driver manager subsystem messages COPTDM003E The application is not specified COPTDM009E The system cannot copy the file VALUE0 to VALUE1 COPTDM026E The system cannot open the VALUE0 file COPTDM030E The system cannot save the changes COPTDM063E The system cannot allocate the server COPTDM060E The Jdbc driver caused an SQL exceptionCOPTDM062E The system cannot allocate the IP address COPTDM064E The system cannot allocate virtual server VALUE0 COPTDM082E The system cannot find the RSA credentials VALUE0 COPTDM099E The system cannot reboot device ID VALUE0 COPTDM089E The system cannot find the switch port ID VALUE0COPTDM098E The system cannot move port COPTDM111E The SSH path is not valid COPTDM108E The integer value VALUE0 is not validCOPTDM109E The load balancing algorithm VALUE0 is not valid COPTDM112E The SSH user name VALUE0 is not valid COPTDM133E The timeout value VALUE0=VALUE1 is not valid COPTDM121E a driver error occurredCOPTDM131E The SecureShell SSH configuration is not valid COPTDM119E No device is associated with SAP ID VALUE0 COPTDM152E The TCDriver VALUE0 is missing item VALUE1 COPTDM162E a deployment error occurredCOPTDM165E a RemoteInstaller error occurred COPTDM157E The request timed out after VALUE0 milliseconds COPTDM183E Upgrade of TCDriver VALUE0 is not allowed COPTDM184E Overwriting of file VALUE0 is not allowed Utilities subsystem messages COPUTL023E Processing Migration Step VALUE0 COPUTL043E Error Message VALUE0COPUTL015E Try to obtain file VALUE0 from environment COPUTL033E Failed SQL Message VALUE0 Compliance Messages Tivoli Intelligent Orchestrator messages Group Messages Networking Messages COPNET026E The system cannot find the VALUE0 access rule COPNET015E The switch endpoint mode VALUE0 is not validCOPNET018E The switch port VALUE0 is already connected COPNET014E The system cannot find Vlan VALUE0 CTGRI0008E a unique directory could not be created RXA MessagesCTGRI0002E Session not established CTGRI0009E pathname cannot be removed CTGRI0019E RSH could not bind to any local privileged port CTGRI0015E The native Windows service binary cannot be readCTGRI0018E An error occurred in SCP communication CTGRI0020E Could not find the remote user RemoteUser Software Distribution Messages DISSP6016E An error occurred saving the package Message Variables where file nameDISSP6015E An error occurred loading the package Correctly installed on your OS/400 DISSP6023E Directory not found DISSP6020E Failed to export file nameDISSP6021E Failed to import file name DISSP6024E Link not found DISSP6031W The sample file file name was not found DISSP6030W The configuration file file name was not foundDISSP6037W The configuration file specified is not valid DISSP6033W Unable to create the working directory DISSP6046E An error occurred while unpacking the SPB DISSP6044E Enter a value in the suggested range Password are defined in Tivoli Provisioning Manager WebUI BTC0006I The common agent has stopped Tivoli Common Agent Services messagesCommon Agent messages BTC0007I The common agent MBeanServer has started Name at port number BTC1034I Certificate revocation list has been Renewed BTC1031I The common agent has been resetBTC1039I Credentials have been renewed BTC1042I command to renew the certificate revocation list BTC1044I command to reset the security credentials Tivoli Common Agent Services messages BTC1050I true Administrator Response To correct this problemBTC1051I false BTC2200I The system is restarting the common agent BTC2205I The common agent is stopping BTC2407E The JLog service JLogService was not found BTC2404I command to set the locale to the languageBTC2406I command to get the locale language and/or region BTC2209I The common agent is being initialized BTC3005E The update source file, bundlename, was not found BTC2412I Locale was not set. The defaultBTC3004E The update target file, bundlename, was not found BTC2411I Locale was successfully set to BTC3104I Bundle was successfully Uninstalled BTC3010E The installation of the bundlename bundle failedBTC3101I The bundle was successfully updated BTC3011E Updating the bundlename bundle failed BTC3107I System has invoked preUpdate LifecycleActivator for BTC3115E The post installation failed BTC3119I command to update the specified bundle BTC3117E The preupdate of the bundle, bundlename failedBTC3118I command to install a bundle from the specified URL BTC3120I command to uninstall the specified bundle BTC3143I Update to the bundlename bundle Failed. cause BTC3140I Bundlename bundle was Successfully installedBTC3142I Bundlename bundle was Successfully updated BTC3144I Bundlename bundle was uninstalled Successfully BTC3166I Installed BTC3163I Unknown subagent bundle commandBTC3164I Unknown common agent command BTC3170I Uninstalled BTC3175I command to get the state of the specified bundle BTC4004I Connector service has been stopped Undeployed BTC4022I Connector is active BTC4014I To get help for a serviceBTC4019I Commands available BTC4023I command to check if the connector service is alive BTC4032I command to regenerate the ID of the common agent BTC4027I command to restart the common agentBTC4030I command to get the ID of the common agent BTC4028I unknown parameter BTC4045E The connection from IPaddress was rejected BTC4046I configfileBTC4047I servicename BTC5006I Processname status collection Process is starting BTC5018I Status report for host hostname, URI BTC5007I Processname status collection Process is endingWas delivered successfully BTC5045I The common agent upgrade completed successfully BTC5042I command to upgrade a common agentBTC5043I command to upgrade a common agent and its JRE BTC5027I Status has been sent Exception Page About the error that occurred Administrator Response No action required Value specified is value. The defaultBTC5073I command args Agent Manager messages Tivoli Common Agent Services messages Page CTGEM0011E The certificate authority was not initialized Administrator Response Contact IBM CustomerCTGEM0015E Use a secure connection Https for this request CTGEM0016E The parametername parameter cannot be Null Tivoli Common Agent Services messages Page Tivoli Common Agent Services messages Guid Guid Tivoli Common Agent Services messages Page AuthXMLAddUser userID password typename typename Page CTGEM0152I The recovery listener classname was loaded CTGEM0150I Initializing the recovery serviceCTGEM0151I Loading the recovery listeners CTGEM0154E The recovery service cannot be initialized CTGEM0156I The registration server was missing CTGEM0155I The recovery service started successfullyCTGEM0162I The recovery service received a recovery request CTGEM0157I Registration server trust failure Tivoli Common Agent Services messages Page CTGEM2124I applicationname version version build build Page Contents of the CASservice.zip file Appendix A. Common Agent serviceability toolRunning the serviceability tool Components MSinfo output file Windows only File name File path Html service fileAll files from config directory Key files from base directory All files from logs\install directory File name File path All files from logs directoryPage Search the Internet Appendix B. Support informationSearching knowledge bases Obtaining fixes Contacting IBM Software Support Submit your problem to IBM Software Support Determine the business impact of your problemDescribe your problem and gather background information SeverityPage Appendix C. Notices 229 Trademarks Index DB2 Unix Windows Page Page SC32-2216-00