Sentinel 6.0.0.0 SP2 Hotfix 04
This document (5023932) is provided subject to the disclaimer at the end of this document.
patches this patch supersedes
| File | Product | Status | Patch |
|---|---|---|---|
| 2008-03-03_SENTINEL_6.0.0.0_SP2_HOTFIX_03.zip | Sentinel 6 SP2 | Obsolete | Sentinel 6.0.0.0 SP2 Hotfix 03 |
patches that supersede this patch
patch attributes
document
abstract
This hot fix must be applied on all Sentinel 6.0.0.0 SP2 machines where DAS, Collector Manager, or Sentinel Control Center processes are running.
details
How to Install
==============
*****************
For Linux/Solaris:
*****************
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Perform these steps on all machines where DAS, Collector Manager, or Sentinel Control Center are installed.
Failing to perform these steps on DAS, Collector Manager, and Sentinel Control Center installations
will result in the system not behaving as expected.
Oracle database must be patched before restarting the Sentinel service.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
1. Login as esecadm user.
2. Unzip the hotfix zip file.
3. Stop the Sentinel service on this machine.
- To stop the Sentinel service: $ESEC_HOME/bin/sentinel.sh stop
4. Make a backup copy of agent-manager.jar, ccsapp.jar, ccsbase.jar, common.jar, communications.jar, console.jar, contentinstaller.jar, libuuid.jar, and dataobjects.jar from $ESEC_HOME/lib.
ESEC_HOME is an environment variable that points to the directory where Sentinel is installed.
5. Copy agent-manager.jar, ccsapp.jar, ccsbase.jar, common.jar, communications.jar, console.jar, contentinstaller.jar, libuuid.jar, and dataobjects.jar from lib\ directory of the unzipped hotfix folder into $ESEC_HOME/lib.
6. Make a backup copy of libagents.so from $ESEC_HOME/lib.
7. Copy libagents.so
For Solaris - Copy lib/solaris/libagents.so from the unzipped hotfix folder into $ESEC_HOME/lib.
For Linux Kernel version2.6.* - Copy lib/linux2.6/libagents.so from the unzipped hotfix folder into $ESEC_HOME/lib.
For Linux Kernel version2.4.* - Copy lib/linux2.4/libagents.so from the unzipped hotfix folder into $ESEC_HOME/lib.
- To find the kernel version on linux execute "uname -r" command.
8. Follow the instructions in "Database Patch Installation on Oracle" to patch Oracle database.
9. Start the Sentinel service on this machine.
- To start the Sentinel service: $ESEC_HOME/bin/sentinel.sh start
10. For any Solution Packs that were created using a previous version of Sentinel, open them in Solution Designer and save again to include the updates in this hotfix. Then re-import the Solution Packs using Solution Manager.
Database Patch Installation on Oracle
=====================================
The following steps must be performed on the machine with the Oracle Sentinel Database installed.
There is one main patch script for Oracle Sentinel Database (PatchDb.sh).
There are several prerequisites to running the patch script for Oracle:
* The patch must be copied to a machine that is running a UNIX operating system supported for Sentinel
* User must have the Oracle client application sqlplus in its PATH
* User must have the environment variable ORACLE_HOME set to the directory where the Oracle software is installed.
* User must have the Java 1.5 executable java in its PATH
Although it is easiest to run the script directly on the database server machine, local policies may prohibit this (for example, if you cannot install Java on the database server). Therefore, this script can be run remotely from any machine that has Java version 1.5 and the Oracle client tools installed.
TIP: Any machine with Sentinel 6.0 or above already has the necessary version of Java installed. However, the $ESEC_HOME/jre directory does not allow the oracle user access by default. Therefore, you can add the oracle user to the esec group (for example, groupmod -A esec oracle), temporarily modify the permissions on the directory (for example, chown -R oracle $ESEC_HOME/jre), or install a second instance of Java.
If using a non-Sentinel machine, the Java version and PATH variable settings can be verified by running the following command from a command line: java -version. If necessary, the PATH environment variable can be updated to include the java installation directory, for example:
export PATH=/opt/novell/sentinel6/jre/bin:$PATH
If Java is not installed on the non-Sentinel machine, the correct Java version [Java Runtime Environment (JRE) 5.0] can be downloaded from the following URL:
http://java.sun.com/javase/downloads/index_jdk5.jsp
To run the main patch script for Oracle:
1. Shut down the Sentinel Server processes (if they are running).
2. Log in to the database server or another machine as a user that meets the installation prerequisites for this script.
3. Verify that your machine meets the Java prerequisites for running this script.
4. Extract the Hotfix zip file.
5. On the command line, go into the Hotfix top level directory that was just extracted.
6. Change directories to the following directory under extracted Hotfix top level directory.
db_patch/bin
7. Enter the following command.
./PatchDb.sh
8. Follow the prompts and enter the following information:
* Hostname or static IP address of the Oracle Sentinel Database that you want to patch.
* Port number of the Oracle Sentinel Database that you want to patch.
* Database net service name.
* Database service name of the Oracle Sentinel Database that you want to patch.
* Esecdba user password.
After you press Enter the final time, the script will verify the entered information and begin the database patch.
9. After the script is done applying the patch, check for any errors. If there are no errors, you are done with the Sentinel Database patch. If there are errors, resolve the errors and re-run the PatchDb utility.
10. Restart the Sentinel servces.
************
For Windows:
************
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Perform these steps on all machines where DAS, Collector Manager, or Sentinel Control Center are installed.
Failing to perform these steps on DAS, Collector Manager, and Sentinel Control Center installations
will result in the system not behaving as expected.
SQL Server database must be patched before restarting the Sentinel service.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
1. Unzip the hotfix zip file.
2. Stop the Sentinel service on this machine using the Windows Service Manager.
3. Make a backup copy of agent-manager.jar, ccsapp.jar, ccsbase.jar, common.jar, communications.jar, console.jar, contentinstaller.jar, libuuid.jar, and dataobjects.jar from %ESEC_HOME%\lib.
ESEC_HOME is an environment variable that points to the directory where Sentinel is installed.
4. Copy agent-manager.jar, ccsapp.jar, ccsbase.jar, common.jar, communications.jar, console.jar, contentinstaller.jar, libuuid.jar, and dataobjects.jar from lib\ directory of the unzipped hotfix folder into %ESEC_HOME%\lib.
5. Make a backup copy of agents.dll from %ESEC_HOME%\lib.
6. Copy lib\windows\agents.dll from the unzipped hotfix folder into %ESEC_HOME%\lib.
7. Follow the instruction on "Database Patch Installation on SQL Server" to patch SQL Server database.
NOTE: If you have already applied Sentinel 6.0.0.0 SP2 Hotfix1, 2, or 3, you don't need to apply the database patch again. If you are unsure if you've already applied the database patch, reapplying the patch will not do any harm.
8. Start the Sentinel service on this machine using Windows Service Manager.
9. For any Solution Packs that were created using a previous version of Sentinel, open them in Solution Designer and save again to include the updates in this hotfix. Then re-import the Solution Packs using Solution Manager.
Database Patch Installation on SQL Server
=========================================
NOTE: If you have already applied Sentinel 6.0.0.0 SP2 Hotfix1, 2, or 3, you don't need to apply the database patch again. If you are unsure if you've already applied the database patch, reapplying the patch will not do any harm.
The following steps must be performed on the machine with a Microsoft SQL Server database to prepare the database for SP2 Hotfix1. There is one main patch script for SQL Server (PatchDb.bat).
Main Patch Scripts for SQL Server
There are several prerequisites to running the pre-patch script for SQL Server:
* The patch must be copied to the machine that is running the Sentinel database.
* The patch must be run using the Sentinel Database User credentials (esecdba by default)
To run the database patch script for database on MSSQL with Windows Authentication:
1. Log into the database machine as the Windows Domain user that is the Sentinel Database User.
2. Shut down the Sentinel Server processes (if this has not already been done).
3. Extract the Hotfix ZIP file (if this has not already been done).
4. Open a command prompt.
5. Change directories to the following directory under the extracted Hotfix directory:
db_patch\bin
6. Enter the command:
.\PatchDb.bat
7. Follow the prompts and enter the following information:
* Hostname or static IP address of the SQL Server Sentinel Database machine
* SQL Server Database instance name, if any
* Port number of the SQL Server database
* Name of the SQL Server database to patch (ESEC by default).
* 1 for the Windows Authentication option
After you press Enter the final time, the script will verify the entered information and proceed if authentication is successful.
8. Enter the language character set support option (1 for Unicode Database or 2 for ASCII Database).
NOTE: For the character set support prompt, select the same option you selected when you initially installed the Sentinel 6.0 Database. If your database was initially installed using Sentinel 5.x, it was installed as an ASCII database.
After you press Enter, the script will begin applying the database patch.
9. After the script is done applying the patch, check for any errors. If there are errors, resolve the errors and re-run the PatchDb utility.
10. After the patch runs with no errors, Sentinel services can be restarted.
To run the database patch script for database on MSSQL with SQL Authentication:
1. Log into the database machine as user that has access to MSSQL database client tools.
2. Shut down the Sentinel Server processes (if this has not already been done).
3. Extract the Hotfix ZIP file (if this has not already been done).
4. Open a command prompt.
5. Change directories to the following directory under the extracted Hotfix directory:
db_patch\bin
6. Enter the command:
.\PatchDb.bat
7. Follow the prompts and enter the following information:
* Hostname or static IP address of the SQL Server Sentinel Database machine
* SQL Server Database instance name, if any
* Port number of the SQL Server database
* Name of the SQL Server database to patch (ESEC by default).
* 2 for the SQL Authentication option
* Esecdba users password
After you press Enter the final time, the script will verify the entered information and proceed if authentication is successful.
8. Enter the language character set support option (1 for Unicode Database or 2 for ASCII Database).
NOTE: For the character set support prompt, select the same option you selected when you initially installed the Sentinel 6.0 Database. If your database was initially installed using Sentinel 5.x, it was installed as an ASCII database.
After you press Enter, the script will begin applying the database patch.
9. After the script is done applying the patch, check for any errors. If there are errors, resolve the errors and re-run the PatchDb utility.
10. After the patch runs with no errors, Sentinel services can be restarted.
########### Bug Fixes and Enhancements ###########
- WORKFLOW_INFO_RPT_V view was missing in from Sentinel 6.0 SP2
File(s) Affected : database installer scripts
OS Affected : Windows,Solaris,Linux
Bug No : DAT-345
Fix : The view is added to hotfix
- Solution Designer was saving the Solution Pack even when the Save As dialog was cancelled
File(s) Affected : contentinstaller.jar
OS Affected : Windows,Solaris,Linux
Bug No : SEN-7671
Fix : When user clicks on 'X' button, the dialog is closed and the zip file is unchanged.
- Reports added to Solution Designer in Windows and deployed to *nix (and vice versa) sometimes failed because the slashes ("\" and "/") were hard-coded into the path.
File(s) Affected : contentinstaller.jar
OS Affected : Windows,Solaris,Linux
Issue No : SEN-7681
Fix : Fix file separator issue so that the report files are installed in the local directory in Windows and *nix
- Correlation rules referring to dynamic lists were not resolved correctly
File(s) Affected : contentinstaller.jar
OS Affected : Windows,Solaris,Linux
Bug No : SEN-7688, SEN-7689
Fix : A correction has been made to the Correlation Rule dependency checker in order to properly extract dynamic list names from zero or more "inlist" correlation rule operators.
- State names were standardarized to INSTALLED (formerly DEPLOYED) and NOT INSTALLED (formerly UNDEPLOYED)
File(s) Affected : database installer scripts
OS Affected : Windows,Solaris,Linux
Bug No : DAT-346, SEN-7697
Fix : "deployed/undeployed" has been changed to "installed/uninstalled".
- Hostname added to destination and source aggregation tables to improve report performance.
File(s) Affected : ccsbase.jar, ccsapp.jar, dataobjects.jar
OS Affected : Windows,Solaris,Linux
Bug No : SEN-7677
Fix : This is an enhancement that hostname is added to destination and source aggregation tables to improve report performance
- Solution Pack Manager publishes only platform-appropriate reports (SQL Server, Oracle, or platform-independent reports).
File(s) Affected : ccsbase.jar, ccsapp.jar, dataobjects.jar, contentinstaller.jar
OS Affected : Windows,Solaris,Linux
Bug No : SEN-7683
Fix : This is an enhancement that Solution Manager publishes only platform-appropriate reports. Reports must be labelled as "Oracle," "SQL Server," or "Platform-independent" in the Solution Designer.
- Improved internal auditing of Sentinel actions.
File(s) Affected : ccsbase.jar, ccsapp.jar, dataobjects.jar, contentinstaller.jar
OS Affected : Windows,Solaris,Linux
Bug No : SEN-7552
Fix : This is an enhancement that some additional data are stored within solution pack audit events to facilitate audit report creation.
- Improved formatting of the PDF generated in Solution Manager.
File(s) Affected : ccsbase.jar, ccsapp.jar, dataobjects.jar, contentinstaller.jar
OS Affected : Windows,Solaris,Linux
Bug No : SEN-7570
Fix : This is an enhancement to increase the number of characters displayed in the Table of Contents, right-justify page numbers in the Table of Contents, and insert page breaks between controls in the body of the document.
- "Reload Solution Manager" dialog is display if a control is installed or uninstalled, even though the solution pack was not updated.
File(s) Affected : ccsbase.jar, dataobjects.jar, contentinstaller.jar
OS Affected : Windows,Solaris,Linux
Bug No : SEN-7675
Fix : The "Reload Solution Manager" dialog will now only display if the solution pack is updated while a Solution Manager is open.
- Uninstalling a control that contains a dynamic list through Solution Manager results in an error, which causes the installation state of the dynamic list to be incorrect.
File(s) Affected : ccsbase.jar, ccsapp.jar, communications.jar
OS Affected : Windows,Solaris,Linux
Bug No : SEN-7675
Fix : The error causing this issue was fixed such that when the dynamic list is uninstalled, the state of the list in the Solution Manager is correct after uninstallation.
- Uninstalling a control that has content that was originally installed as part of the Sentinel DB installation (i.e., seed data) results in a NullPointerException
File(s) Affected : contentinstaller.jar
OS Affected : Windows,Solaris,Linux
Bug No : SEN-7675
Fix : Uninstalling seed data content now works properly, without resulting in an error.
- PCI-DSS solution pack import fails sporadically with an InvocationTargetException
File(s) Affected : ccsbase.jar
OS Affected : Windows,Solaris,Linux
Bug No : SEN-7724
Fix : Race condition in temp file management used by solution pack import has been fixed to address this problem.
- Correlation rules installed from a solution pack do not get undeployed from correlation engines when the corresponding control is uninstalled.
File(s) Affected : ccsapp.jar, contentinstaller.jar
OS Affected : Windows,Solaris,Linux
Bug No : SEN-7730
Fix : Correlation rules are now successfully undeployed from the correlation engine when the corresponding control is uninstalled.
- Shutdown task does not work on some machines, DAS processes may not exit cleanly
File(s) Affected : ccsapp.jar
OS Affected : Linux
Bug No : SEN-6681
Fix : Fixed the handling of the host addresses so that the Sentinel containers shutdown gracefully now.
- Clicking on ESM Graph view node is sluggish when there are a lot of nodes (approx. 1000)
File(s) Affected : console.jar, ccsapp.jar
OS Affected : Windows, Solaris, Linux
Bug No : SEN-7739
Fix : Improved responsiveness of GUI when there are many nodes.
- NullPointerException appears in Collector Manager log if it is stopped before it full initialized
File(s) Affected : ccsapp.jar
OS Affected : Windows, Solaris, Linux
Bug No : SEN-7746
Fix : If the Collector Manager is stopped before it is full initialized, it will behave correclty.
- Null Pointer Exception in Collector Manager when stopping Collector
File(s) Affected : agent-manager.jar
OS Affected : Windows, Solaris, Linux
Bug No : SEN-7747
Fix : Collector Manager behaves correctly when stopping Collector.
- If Sentinel process does not exit cleanly (e.g., exit value != 0), the process is not automatically restarted.
File(s) Affected : ccsapp.jar, console.jar
OS Affected : Solaris, Linux
Bug No : SEN-7743
Fix : The Sentinel watchdog process will now properly handle the condition if a child process does not exit cleanly (e.g., exit value != 0).
- Many Event Sources (>2000) on one Collector Manager can cause out of memory exceptions
File(s) Affected : ccsapp.jar, ccsbase.jar
OS Affected : Windows, Solaris, Linux
Bug No : SEN-7757
Fix : Optimized the Collector Manager to use less memory for each Event Source.
Hotfix4 bug fixes:
- Audit Connector generates a java.lang.NullPointerException when writing to the Raw Data File
File(s) Affected : ccsapp.jar
OS Affected : Windows, Solaris, Linux
Bug No : SEN-7784
Fix : Audit Connector behaves normally when writing to the Raw Data File
- Collector Manager doesn't log the exit code when the agentengine exits.
File(s) Affected : agent-manager.jar
OS Affected : Windows, Solaris, Linux
Bug No : SEN-7783
Fix : Collector Manager now log the exit code correctly when the agentengine exits.
- Attempting to stop Collector Manager with Server View results in Interrupted Exception and process doesn't appear to stop
File(s) Affected : ccsbase.jar
OS Affected : Windows, Solaris, Linux
Bug No : SEN-7772
Fix : Attemping to stop Collector Manager with Server View behaves correctly.
- Sporadic ConcurrentModificationException when starting/stopping a lot (1000s) of nodes at once
File(s) Affected : ccsbase.jar
OS Affected : Windows, Solaris, Linux
Bug No : SEN-7767
Fix : No ConcurrentModificationException is seen anymore when starting/stopping a lot (1000s) of nodes at once
- Memory leak when using arrays in lookup file called from LOOKUP cmd that had a String Var as its "Lookup File Name" argument
File(s) Affected : agents.dll, libagents.so
OS Affected : Windows, Solaris, Linux
Bug No : WIZ-1856
Fix : No memory leak is seen when when using arrays in lookup file called from LOOKUP cmd that had a String Var as its "Lookup File Name" argument
- das_binary is confused about Oracle database usage and reports database usage incorrectly
File(s) Affected : none
OS Affected : Solaris, Linux
Bug No : DAT-348
Fix : das_binary now reports database usage correctly
file contents
| Files Included | Size | Date |
|---|---|---|
| 2008-04-25_SENTINEL_6.0.0.0_SP2_HOTFIX_04.zip | 31.3 MB (32849074) | 2008-04-30 12:08:33 |
| readme_5023932.html | N/A | 2008-05-05 09:50:44 |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
Novell is a registered trademark of Novell, Inc. in the United States and other countries. SUSE is a registered trademark of SUSE Linux AG, a Novell business. *All third-party trademarks are the property of their respective owners.
© 2007 Novell, Inc. All Rights Reserved.