Manuals / IBM / Computer Equipment / Network Router

IBM 51 manual Runtime logs for prerequisites, WebSphere Application Server, Directory Server

Models: 51

1 248

Download 248 pages 41.4 Kb

Page 64

Directory Server

The log files for the IBM Tivoli Directory Server are:

vldap.stderr

vldap.stdout

vldapinst.log

Runtime logs for prerequisites

For additional information on errors that do not pertain to Tivoli Intelligent Orchestrator, you might want to consult the error and trace logs for the middleware prerequisites. The names and the locations of these log files are provided below.

WebSphere Application Server

The runtime WebSphere Application Server logs are located in the %WAS_HOME%\logs and the %WAS_HOME%\logs\server1 directories, where %WAS_HOME% is the WebSphere Application Server home directory. The runtime transaction logs for WebSphere Application Server are stored in the %WAS_HOME%\tranlog directory.

The default value for %WAS_HOME% is:

Windows

C:\Program Files\WebSphere\AppServer

AIX /usr/WebSphere/AppServer

Linux and Solaris

/opt/WebSphere/AppServer

Check the following log files for errors:

vSystemOut.log

vstartServer.log

vstopServer.log

vSystemErr.log

SystemOut.log

This is the log file for WebSphere output. It contains messages that are generated when the applications running inside the WebSphere Application Server are being started or stopped. You might want to refer to this file when WebSphere does not start. The log file is located in the %WAS_HOME%\logs\server1 directory on Windows systems ($WAS_HOME/logs/server1 on UNIX or Linux).

After the Tivoli Intelligent Orchestrator is successfully started, use the tail -f SystemOut.log command to monitor this log file for any problems that might occur.

startServer.log

This is the log file for the startup of the WebSphere Application Server, located in the %WAS_HOME%\logs\server1 directory on Windows systems ($WAS_HOME/logs/server1 on UNIX or Linux).

Look for open for e-business for a successful startup of the WebSphere

Application Server.

stopServer.log

This is the log file for the shutdown of the WebSphere Application Server.

52Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide

Image 64

IBM 51 manual Runtime logs for prerequisites, WebSphere Application Server, Directory Server, Linux and Solaris

Contents

Problem Determination and Troubleshooting Guide Page Problem Determination and Troubleshooting Guide Page Contents Troubleshooting the agent Tivoli Common Agent Page Preface Who should read this bookPublications Tivoli Intelligent Orchestrator libraryPrerequisite publications Related publications and resourcesAccessibility Accessing publications onlineOrdering publications Tivoli software training Support information Conventions used in this bookTypeface conventions MonospaceIntroduction to troubleshooting Product and system overviewOrchestrating provisioning Product comparisonTivoli Intelligent Orchestrator Tivoli Provisioning Manager Product architecture Tivoli Intelligent Orchestrator componentsData center model Policy engineObjective analyzer Global resource managerDeployment engine Automation packagesBuilt-in troubleshooting features Problem classificationProduct maintenance Backing up the systemProblem resolution Performing periodic checks and maintenanceClick Technical documentation on the left Problem determination methodologies Defining the problemIdentifying the cause of the problem Determining where the problem lies and what it isVerifying whether the problem can be replicated Checking whether the problem has occurred beforeFixing the problem Troubleshooting the prerequisite installation DB2 Universal Database verificationIBM Tivoli Directory Server verification UnixWindows LDAPInstallDirectory\var\ WebSphere Application Server verification Security.xmlServer.xml Java.securitySas.client.props SystemOut.logSecure Authentication Services Ldap Map Tivoli Intelligent Orchestrator resource referencesSimple Object Access Protocol Soap Http Transport ServiceApplications Tcear ApplicationRemote 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 ChangePassword.cmd Password currentWasadmin password ChangePassword.sh userDcmQueryCommandt.cmd DcmQueryCommandt.shDcmExport.cmd -d OutputFilenameIdeviceId RetrieveDetails.cmdRetrieveDetails.sh Siregister.cmd PackagelocationRepositoryname RepositorymountpointCommand UpdateCredential.cmdInternaluserpassword WASAdminUserWebSphere Application Server command line tools XmlImport.cmd fileURLFileURL xmlImport.sh FileURL fileURLIBM Tivoli Directory Server command line tools Name Location DescriptionPage Log file types Message logsMessage ID format Code SubsystemMessage elements Message IDMessage text ExplanationTrace logs Common Base Event logsPage Log locations Locating and configuring log filesLog directory files Configuring logs with log4j Logging levelsLog4j.prop WindowsLocating 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 filesWorkflow logs Logs for data collection and decision making Automation package logsThis log file stores error Installation log files for prerequisites Installation logs for individual prerequisitesMiddleware prerequisite log files WebSphere Application ServerRuntime logs for prerequisites WebSphere Application ServerDirectory Server Linux and SolarisDB2 Universal Database Directory ServerTivoli 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 errorShell command error Resource temporarily unavailable Solution workflowLogExport tool$TIOHOME/tools Syntax for UnixWorkflow does not install Example workflow log exportOther 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 requirementsCommon agents unable to communicate with the agent manager There is a maximum size for returnResult parameter storage Device Manager limitationsKnown report limitations Agent receives an Http Unauthorized 401 response codeRunning any report with too many objects selected fails Page Troubleshooting the agent manager Locating the installation log filesLog files for the agent manager Packaging the log filesLog file name Description GuidLocating the uninstallation log files Locating the remote registry logsLocating 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 Verifying the installation of WebSphere Application Server Errors starting the agent manager application serverErrors starting the agent manager application Verifying the connection to the registryTask Value in Trace Specification text box Enabling and disabling tracingEnabling tracing Disabling tracingEnsure that Enable Trace is not checked Click OK Common problems Registration and communication failuresProblems using the WebSphere Administrative Console Cannot start the WebSphere Administrative ConsoleAs a Windows service Using a Windows commandStopServer server1 startServer server1 Page Contacting IBM Tivoli Software Support General data to collect for Tivoli SupportPackageLog ZIP tool LocationSyntax Returned filePrerequisites Linux and UnixPage Tivoli Intelligent Orchestrator messages Common subsystem messagesCOPCOM001E The system cannot delete the VALUE0 file COPCOM003E The system cannot find the VALUE0 dcm policyCOPCOM012E The server VALUE0 does not have a locale value COPCOM015E The system cannot get a Jndi contextCOPCOM016E The directory VALUE0 does not exist COPCOM024E The system cannot use the VALUE0 JMS destinationCOPCOM040E The system failed to load the VALUE0 XML file COPCOM041E The system failed to parse the VALUE0 XML fileCOPCOM042E The system cannot read the VALUE0 XML file COPCOM050E Application VALUE0 not foundCOPCOM058E The system cannot find application tier VALUE0 COPCOM059E The system cannot find a rule at position VALUE0COPCOM061E The system cannot find customer VALUE0 COPCOM063E The system cannot find the DCM object ID VALUE0COPCOM082E The system cannot find power outlet VALUE0 COPCOM083E The system cannot find power unit VALUE0COPCOM071E The system cannot find the load balancer VALUE0 COPCOM075E The system cannot find NIC VALUE0COPCOM096E The system did not find the VALUE0 switch port COPCOM097E The system cannot find the VALUE0 switchCOPCOM090E The system cannot find the VALUE0 software stack COPCOM091E The system cannot find the VALUE0 software stateCOPCOM124E a Telnet error occurred COPCOM125E a Telnet error occurredCOPCOM115E There is not enough data to complete the task COPCOM116E The operation timed outCOPCOM136E The system cannot find error VALUE0 COPCOM140E An error occurred VALUE0COPCOM143E a shell command error VALUE0 occurred COPCOM155E The system cannot find the VALUE0 boot serverCOPCOM159E The system cannot find the VALUE0 access rule COPCOM158E The system cannot find the VALUE0 interface cardCOPCOM161E The system cannot find the resource VALUE0 COPCOM170E The system cannot find this route VALUE0COPCOM195E 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 COPCOM197E The system cannot find the VALUE0 logical volume COPCOM198E The system cannot find the VALUE0 file systemCOPCOM203E The system cannot find the VALUE0 data path COPCOM204E The system cannot find the VALUE0 zone setCOPCOM217E The system cannot create the output file VALUE0 COPCOM219E The database cannot complete the queryCOPCOM226E The VALUE0 server template is not valid COPCOM230E The system cannot find the VALUE0 host platformCOPCOM237E The system cannot find the VALUE0 software module COPCOM243E The system cannot find the VALUE0 routerCOPCOM269E The switch endpoint mode VALUE0 is not valid COPCOM274E The system cannot find the discoverable VALUE0COPCOM278E The system cannot find the VALUE0 storage manager COPCOM282E Port VALUE0 is already connected to port VALUE1COPCOM303E 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 foundCOPCOM358E The service with name VALUE0 cannot be found COPCOM355E The scheduled task type VALUE0 is not validCOPCOM357E The Order of ID VALUE0 cannot be found COPCOM360E The subscription of ID VALUE0 cannot be foundCOPCOM378E AgentManager did not find the Agent ID VALUE0 COPCOM377E Internal Error Null AgentGUID was specifiedCOPCOM385E The system cannot find the report VALUE0 COPCOM395E The TCM object type VALUE0 was not found COPCOM396E The filter format is not valid. Filter VALUE0COPCOM400E No TCM Gateways were found for Hostname VALUE0 COPCOM401E The endpoint lookup returned null for VALUE0COPCOM405E The Profile Manager is VALUE0 COPCOM407E Profile VALUE0 is not a managed profileCOPCOM408E The Endpoint subscriber VALUE0 does not exist COPCOM417E The filter VALUE0 lacks a parent componentCOPCOM431E The instance access role VALUE0 is unknown COPCOM432E The access domain VALUE0 is unknownCOPCOM430E The instance permission VALUE0 is unknown COPCOM433E The domain role VALUE0 is unknownCOPCOM442E The type VALUE0 is not a valid filter type COPCOM443E The system cannot create the file VALUE0COPCOM457E An unknown event type VALUE0 occured COPCOM458E An unknown event consumer VALUE0 occuredCOPCOM468E The SI image resource VALUE0 registers an error COPCOM473E The LCF installation directory is not specifiedCOPCOM465E a Security Group with name VALUE0 already exists COPCOM466E Bad SI package image format with VALUE0COPCOM480E The value for Http Disable must be a 0, 1, 2 or COPCOM481E The value for Broadcast Disable must be a 0 orCOPCOM482E The Login Interval is not correct COPCOM494E Unable to connect to endpoint using RXACOPCOM499E Error copying file using RXA VALUE0 COPCOM503E Error converting path VALUE0 to DOS style pathCOPCOM502E The system cannot create the directory VALUE0 COPCOM514E The database sequence VALUE0 does not existCOPCOM521E Unable to read xml config file VALUE0 COPCOM532E The server VALUE0 cannot be accessed or updatedCOPCOM533E The DCM object VALUE0 cannot be updated COPCOM525E Cannot find DCM Property Id VALUE0Deployment engine subsystem messages COPCOM539E Task VALUE0 Task Id VALUE1 failedCOPDEX001E The system cannot get a Jndi context COPDEX002E The system cannot use the VALUE0 JMS destinationCOPDEX005E The VALUE0 logical operation does not exist COPDEX008E break cannot be used inside of a finally blockCOPDEX033E Error code for unit tests only COPDEX019E The condition VALUE0 is not validCOPDEX020E The system requires the VALUE0 attribute COPDEX022E The ID VALUE0 is not an integerCOPDEX038E a database error occurred VALUE0 COPDEX039E a configuration error occurredCOPDEX041E a deployment error occurred COPDEX040E a deployment engine exception occurred VALUE0COPDEX060E a workflow XML parser error VALUE0 occurred COPDEX062E a data insert error VALUE0 occurredCOPDEX063E An XML data parsing error VALUE0 occurred COPDEX069E The system cannot process the data update VALUE0COPDEX081E The system cannot specify an input file COPDEX082E The system cannot find the input file VALUE0COPDEX083E The input file VALUE0 is empty COPDEX084E The operation type VALUE0 is not identifiedPage COPDEX129E a workflow compiler error occurred VALUE0 COPDEX130E The deployment request id=VALUE0 was cancelledCOPDEX127E The VALUE0 variable is already declared COPDEX128E The VALUE0 variable does not existCOPDEX141E The specified LDO VALUE0 is not found COPDEX140E The deployment request VALUE0 is not foundCOPDEX142E The specified workflow VALUE0 is not found COPDEX149E No such parameter VALUE0 COPDEX150E Unknown instance permission VALUE0COPDEX151E Duplicate permission VALUE0 for parameter VALUE1 COPDEX153E The size of input arrays are differentCOPDEX170E The VALUE0 Java plug-in does not exist COPDEX176E The parameter VALUE0 cannot be nullCOPDEX178E To do VALUE0 COPDEX183E DCM object VALUE0 does not have attribute VALUE1Job Distribution Service JDS subsystem messages J2ee subsystem messagesCOPJEE009E This feature is not supported COPJEE032E The system cannot recognize the database type COPJEE035E The system cannot find the RSA credentials VALUE0COPJEE049E The operating mode VALUE0 is not valid COPJEE050E The specified resource pool VALUE0 is not validCOPJEE055E No software stack is associated with VALUE0 COPJEE056E The requested object VALUE0 is already lockedCOPJEE068E 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 COPJEE101E a user interface error occurred VALUE0 COPJEE105E An error occurred VALUE0COPJEE106E The upgrade type is not valid COPJEE112E a power outlet already existsCOPJEE167E 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 validCOPJEE272E 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 COPJEE334E The access to DB driver VALUE0 is not allowed COPJEE326E The system failed to delete deployment requestCOPJEE333E The system cannot find DB driver VALUE0 COPJEE335E Instantiation of DB driver VALUE0 failedCOPJEE345E Multiple Password credentials were returned COPJEE350E a data insert error VALUE0 occurredCOPJEE351E The system cannot process the data update VALUE0 COPJEE356E a system error VALUE0 occurredCOPJEE379E The workflow was already added Policy engines subsystem messages COPPEZ005E The system cannot create the Snmp connectionCOPPEZ008E The system cannot estimate Number of servers COPPEZ009E The system cannot open the VALUE0 fileCOPPEZ042E VALUE0 is not a valid device type COPPEZ044E VALUE0 is not valid for a VALUE1 contextCOPPEZ047E The data acquisition thread is not working COPPEZ049E VALUE0 is not a valid VALUE1 metricCOPPEZ073E An Snmp IO error occurred COPPEZ077E An error VALUE0 occurredCOPPEZ079E a resource broker error occurred COPPEZ110E a task library lookup error occurredCommon agent subsystem messages COPPEZ115E The system cannot obtain a application tier IDCOPPEZ116E The endpoint label is null or empty COPTCA001E Cannot get proxy for interface on Agent VALUE0TC driver manager subsystem messages COPTDM003E The application is not specified COPTDM009E The system cannot copy the file VALUE0 to VALUE1COPTDM026E The system cannot open the VALUE0 file COPTDM030E The system cannot save the changesCOPTDM060E The Jdbc driver caused an SQL exception COPTDM062E The system cannot allocate the IP addressCOPTDM063E The system cannot allocate the server COPTDM064E The system cannot allocate virtual server VALUE0COPTDM082E 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 COPTDM108E The integer value VALUE0 is not valid COPTDM109E The load balancing algorithm VALUE0 is not validCOPTDM111E The SSH path is not valid COPTDM112E The SSH user name VALUE0 is not validCOPTDM121E a driver error occurred COPTDM131E The SecureShell SSH configuration is not validCOPTDM133E The timeout value VALUE0=VALUE1 is not valid COPTDM119E No device is associated with SAP ID VALUE0COPTDM162E a deployment error occurred COPTDM165E a RemoteInstaller error occurredCOPTDM152E The TCDriver VALUE0 is missing item VALUE1 COPTDM157E The request timed out after VALUE0 millisecondsCOPTDM183E Upgrade of TCDriver VALUE0 is not allowed COPTDM184E Overwriting of file VALUE0 is not allowedUtilities subsystem messages COPUTL043E Error Message VALUE0 COPUTL015E Try to obtain file VALUE0 from environmentCOPUTL023E Processing Migration Step VALUE0 COPUTL033E Failed SQL Message VALUE0Compliance Messages Tivoli Intelligent Orchestrator messages Group Messages Networking Messages COPNET015E The switch endpoint mode VALUE0 is not valid COPNET018E The switch port VALUE0 is already connectedCOPNET026E The system cannot find the VALUE0 access rule COPNET014E The system cannot find Vlan VALUE0RXA Messages CTGRI0002E Session not establishedCTGRI0008E a unique directory could not be created CTGRI0009E pathname cannot be removedCTGRI0015E The native Windows service binary cannot be read CTGRI0018E An error occurred in SCP communicationCTGRI0019E RSH could not bind to any local privileged port CTGRI0020E Could not find the remote user RemoteUserSoftware Distribution Messages Message Variables where file name DISSP6015E An error occurred loading the packageDISSP6016E An error occurred saving the package Correctly installed on your OS/400DISSP6020E Failed to export file name DISSP6021E Failed to import file nameDISSP6023E Directory not found DISSP6024E Link not foundDISSP6030W The configuration file file name was not found DISSP6037W The configuration file specified is not validDISSP6031W The sample file file name was not found DISSP6033W Unable to create the working directoryDISSP6046E An error occurred while unpacking the SPB DISSP6044E Enter a value in the suggested rangePassword are defined in Tivoli Provisioning Manager WebUI Tivoli Common Agent Services messages Common Agent messagesBTC0006I The common agent has stopped BTC0007I The common agent MBeanServer has startedName 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 credentialsTivoli 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 stoppingBTC2404I command to set the locale to the language BTC2406I command to get the locale language and/or regionBTC2407E The JLog service JLogService was not found BTC2209I The common agent is being initializedBTC2412I Locale was not set. The default BTC3004E The update target file, bundlename, was not foundBTC3005E The update source file, bundlename, was not found BTC2411I Locale was successfully set toBTC3010E The installation of the bundlename bundle failed BTC3101I The bundle was successfully updatedBTC3104I Bundle was successfully Uninstalled BTC3011E Updating the bundlename bundle failedBTC3107I System has invoked preUpdate LifecycleActivator for BTC3115E The post installation failedBTC3117E The preupdate of the bundle, bundlename failed BTC3118I command to install a bundle from the specified URLBTC3119I command to update the specified bundle BTC3120I command to uninstall the specified bundleBTC3140I Bundlename bundle was Successfully installed BTC3142I Bundlename bundle was Successfully updatedBTC3143I Update to the bundlename bundle Failed. cause BTC3144I Bundlename bundle was uninstalled SuccessfullyBTC3163I Unknown subagent bundle command BTC3164I Unknown common agent commandBTC3166I Installed BTC3170I UninstalledBTC3175I command to get the state of the specified bundle BTC4004I Connector service has been stopped UndeployedBTC4014I To get help for a service BTC4019I Commands availableBTC4022I Connector is active BTC4023I command to check if the connector service is aliveBTC4027I command to restart the common agent BTC4030I command to get the ID of the common agentBTC4032I command to regenerate the ID of the common agent BTC4028I unknown parameterBTC4046I configfile BTC4047I servicenameBTC4045E The connection from IPaddress was rejected BTC5006I Processname status collection Process is startingBTC5018I Status report for host hostname, URI BTC5007I Processname status collection Process is endingWas delivered successfully BTC5042I command to upgrade a common agent BTC5043I command to upgrade a common agent and its JREBTC5045I The common agent upgrade completed successfully BTC5027I Status has been sentException Page About the error that occurred Value specified is value. The default BTC5073I command argsAdministrator Response No action required Agent Manager messagesTivoli 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 CTGEM0150I Initializing the recovery service CTGEM0151I Loading the recovery listenersCTGEM0152I The recovery listener classname was loaded CTGEM0154E The recovery service cannot be initializedCTGEM0155I The recovery service started successfully CTGEM0162I The recovery service received a recovery requestCTGEM0156I The registration server was missing CTGEM0157I Registration server trust failureTivoli Common Agent Services messages Page CTGEM2124I applicationname version version build build Page Appendix A. Common Agent serviceability tool Running the serviceability toolContents of the CASservice.zip file ComponentsFile name File path Html service file All files from config directoryMSinfo output file Windows only Key files from base directoryAll files from logs\install directory File name File path All files from logs directoryPage Appendix B. Support information Searching knowledge basesSearch the Internet Obtaining fixesContacting IBM Software Support Determine the business impact of your problem Describe your problem and gather background informationSubmit your problem to IBM Software Support SeverityPage Appendix C. Notices 229Trademarks Index DB2Unix Windows Page Page SC32-2216-00