Novell Sentinel Log Manager 1.0.0.5 Release Notes
9
no
vd
ocx
(e
n)
19
Fe
bru
a
ry
20
10
4.3 Issues Fixed in Sentinel Log Manager 1.0.0.3 Release
This section lists the issues fixed in Novell Sentinel Log Manager 1.0.0.3 Release.
Table 4
Issues fixed in Sentinel Log Manager 1.0.0.3 Release
495806
Issue: Export search result has the same event count limit as search
refinement (50,000).
Fixed: The 50,000 limit for exporting results has been removed. Now the
user will be prompted to enter the number of results they want to export.
Issues Fixed
Description
563948
Issue: A message stating that no events have been found by the search is
displayed even before the search is completed.
Fixed: The
no events found
message only appears if no events are
found after the completion of a search.
560580
Issue: Occasional searches run from the search tool bar used the previous
search string instead of the new search string.
Fixed: A new search run from the search tool bar uses the new search
string.
556411
Issue: Squashfs indexes that were mounted by a previous running
instance of the server are not cleaned up when the server starts, resulting
is failed searches.
Fixed: The server now detects if old mounts need to be cleaned up and
cleans them up allowing searches to complete normally.
552519
Issue: The softwarekey.sh script was not included in the install, making it
difficult to reset the license key with the server turned off.
Fixed: The softwarekey.sh script is now included.
549582
Issue: An event is not searchable by its original timestamp if it arrives
more than a day late.
Fixed: The event is searchable by its original timestamp no matter how
late it arrives.
546324
Issue: A rule or data retention policy configured with a filter that is just a full
text search (i.e., no field such as
sev:5
is specified) results in an error on
the server that prevents any users from logging into the Web interface or
ESM user interface.
Fixed: The bug is fixed so that all valid filters are now accepted and
evaluated properly. Filter validation is also done before allowing a user to
save a filter to prevent an invalid filter from being saved that would cause
logins to fail.
Issues Fixed
Description
