You can review the following installation log files to begin troubleshooting your installation:
|
Product |
Log File Location |
|---|---|
|
CA User Activity Reporting Module |
/tmp/pre-install_ca-elm.log /tmp/install_ca-elm.<timestamp>.log /tmp/install_ca-elmagent.<timestamp>.log |
|
CA Embedded Entitlements Manager |
/opt/CA/SharedComponents/EmbeddedIAM/eiam-install.log |
|
CA Directory |
/tmp/etrdir_install.log |
The CA User Activity Reporting Module installation copies content and other files to the CA EEM server for management. From the perspective of the CA EEM server, the CA User Activity Reporting Module reports and other files are imported. If the installation cannot connect to the CA EEM server, the installation of CA User Activity Reporting Module continues without importing the content files. You can import the content files manually when the installation is complete.
If you encounter any errors during installation, you may need to perform one or more of the following actions to complete your installation. Each of these actions involves logging into the CA User Activity Reporting Module server using the default account, caelmadmin, and then switching users to the root account.
After installation, if you are unable to access the CA User Activity Reporting Module server's user interface, you may have a network interface configuration error. You have two options to resolve the error:
To reconfigure network adapter ports from a command line
su -
system-config-network
The user interface to configure the network adapters displays.
service network restart
You can perform a quick check of the installation by verifying that the appropriate rpm package is installed.
To verify the rpm package
su - root
rpm -q ca-elm rpm -q ca-elmagent
The operating system returns the full name of the package if it is installed.
Symptom:
During installation, the CA User Activity Reporting Module application did not register successfully with the CA EEM server. The CA User Activity Reporting Module application depends on the CA EEM server for the management of user accounts and service configurations. If the CA User Activity Reporting Module application is not registered, the software will not run properly.
The shell script mentioned in the procedure that follows is automatically copied to the named directory during installation.
Solution:
Register the CA User Activity Reporting Module application with the CA EEM server manually.
To register the CA User Activity Reporting Module application
su -
./EEMRegister.sh
The shell script registers the CA User Activity Reporting Module application with the CA EEM server.
Symptom:
During installation, the digital certificates were not acquired from the CA EEM server correctly. Digital certificates are required to start and run the CA User Activity Reporting Module application.
The shell script mentioned in the procedure that follows is automatically copied to the named directory during installation.
Solution:
Acquire the certificates from the CA EEM server manually.
To acquire the digital certificates
su -
./EEMAcqCert.sh
The shell script performs the processing necessary to acquire the needed digital certificates.
Symptom:
During installation, the CA EEM server did not successfully import report content from the CA EEM server. You must import the report content to see event data after it is stored in the event log store.
The shell script mentioned in the procedure that follows is automatically copied to the named directory during installation.
Solution:
Import the report content manually.
To import report content
su -
./ImportCALMContent.sh
The shell script downloads the report content from the CA EEM server.
Symptom:
During installation, the CA EEM server did not successfully import the data mapping (DM) files. You must have the DM files to map incoming event data into the event log store.
The shell script mentioned in the procedure that follows is automatically copied to the named directory during installation.
Solution:
Import the DM files manually.
To import DM files
su -
./ImportCALMDM.sh
The shell script imports the DM files from the CA EEM server.
Symptom:
During installation, the CA EEM server did not successfully import the common event grammar (CEG) files. The CEG forms the underlying database schema for the event log store. You will not be able to store events in the CA User Activity Reporting Module event log store without the CEG files.
The shell script mentioned in the procedure that follows is automatically copied to the named directory during installation.
Solution:
Import the CEG files manually.
To import CEG files
su -
./ImportCALMCEG.sh
The shell script imports the common event grammar files.
Symptom:
During installation, the CA EEM server did not successfully import the correlation rule files. Correlation rules allow you to identify patterns of events that require investigation. You can import correlation groups or rule themselves.
The shell script mentioned in the procedure that follows is automatically copied to the named directory during installation.
Solution:
Import the correlation rule files manually.
To import correlation rule files
su -
./ImportCALMCorrelationGroups.sh
The shell script imports correlation rule groups.
./ImportCALMCorrelationRules.sh
The shell script imports the correlation rule files.
Symptom:
During installation, the CA EEM server did not successfully import the common agent management files. You cannot manage agents in the CA User Activity Reporting Module user interface without these files.
The shell script mentioned in the procedure that follows is automatically copied to the named directory during installation.
Solution:
Import the agent management files manually.
To import common agent management files
su -
./ImportCALMAgentContent.sh
The shell script imports the common agent management files.
Symptom:
During installation, the CA EEM server did not successfully import the configuration files. You can start CA User Activity Reporting Module but certain settings and values are missing from the Services configuration areas, and you cannot configure individual hosts centrally without these files.
The shell script mentioned in the procedure that follows is automatically copied to the named directory during installation.
Solution:
Import the configuration files manually.
To import configuration files
su -
./ImportCALMConfig.sh
The shell script imports the configuration files.
Symptom:
During installation, the CA EEM server did not successfully import the suppression and summarization files. You cannot use the out-of-the-box suppression and summarization rules in the CA User Activity Reporting Module user interface without these files.
The shell script mentioned in the procedure that follows is automatically copied to the named directory during installation.
Solution:
Import the suppression and summarization files manually.
To import suppression and summarization files
su -
./ImportCALMSAS.sh
The shell script imports the suppression and summarization files.
Symptom:
During installation, the CA EEM server did not successfully import the parsing token files. You cannot use out-of-the-box parsing tokens in the Message Parsing Wizard without these files.
The shell script mentioned in the procedure that follows is automatically copied to the named directory during installation.
Solution:
Import the parsing token files manually.
To import parsing token files
su -
./ImportCALMTOK.sh
The shell script imports the parsing token files.
Symptom:
During installation, the CA EEM server did not successfully import the user interface files. You cannot see or use the values in the dynamic time range drop down fields without these files.
The shell script mentioned in the procedure that follows is automatically copied to the named directory during installation.
Solution:
Import the user interface files manually.
To import user interface files
su -
./ImportCALMFlexFiles.sh
The shell script imports the user interface files.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|