Sentinel 7.1.1.2 was released on February 11, 2014. Here is a list of
the new fixes included in this hotfix. (For the list of software fixes
and enhancements in previous releases, see the 'Sentinel 7.1
Documentation Web site'
(http://www.netiq.com/documentation/sentinel71).)

1.1 THE COPY PROCESS TRUNCATES FILES OVER 2 GB

Issue: In Sentinel 7.1.0.0, 7.1.0.1, 7.1.1.0, and 7.1.1.1, the copy
process that moves parsed event data partitions from primary storage to
secondary storage can truncate files larger than 2 GB. The copy process
copies the first 2 GB successfully, but does not copy the remainder of
the file and does not report any error. (BUG 860133)

This issue does not occur if secondary storage is disabled. This issue
is unlikely to occur if the event rate is low (less than 500 events per
second) or if there are multiple data retention policies in effect
(which increases the number of event partitions and therefore decreases
the probability that any individual event partition is larger than 2
GB). This issue does not affect raw (unparsed) data. For more
information on this issue, see TID 7014515 in the Novell Support
Knowledge Base.

Fix: Sentinel now uses a different copy process to avoid this error.
After copying an event data file to secondary storage, Sentinel runs
data checks automatically to verify that the copy completed
successfully. If the file check fails, Sentinel automatically retries
the copy. The default data check is a quick verification of file size to
detect file truncation. Sentinel also provides an alternate check that
compares strong checksums (hashes) of the source file and its copy to
detect file truncation and additionally many forms of data corruption.
However, the alternate check requires significant I/O and will impact
the system performance.

To enable the alternate check:


- Log in to the Sentinel server.
- Open the etc/opt/novell/sentinel/config/configuration.properties
file in an editor.
- Set the partition.archiver.quickintegritycheck property to false as
follows:
partition.archiver.quickintegritycheck=false
- Restart the Sentinel server.



1.2 THE EVENT TIME IN THE CSV FILE IS NOT IN THE STANDARD DATE FORMAT

Issue: When you export the search results to a CSV file, the date in the
EventTime (dt) field is not in a standard format. (BUG 855420)

Fix: The EventTime (dt) field in the CSV file now displays the date in a
standard readable format.

1.3 SENTINEL STOPS WORKING WHEN THE SENTINEL CONTROL CENTER IS LAUNCHED
ON DIFFERENT COMPUTERS SIMULTANEOUSLY

Issue: When you try launching the Sentinel Control Center on different
computers simultaneously, Sentinel stops working. (BUG 854759)

Fix: Sentinel now works properly when the Sentinel Control Center is
launched on different computers simultaneously


--
CeeDubbVA
------------------------------------------------------------------------
CeeDubbVA's Profile: https://forums.netiq.com/member.php?userid=4538
View this thread: https://forums.netiq.com/showthread.php?t=50310