18
Novell Sentinel Log Manager 1.0.0.4 Release Notes
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
7 Documentation Conventions
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items
in a cross-reference path.
A trademark symbol (
®
,
TM
, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party
trademark
8 Legal Notices
Novell, Inc. makes no representations or warranties with respect to the contents or use of this
documentation, and specifically disclaims any express or implied warranties of merchantability or
fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication
and to make changes to its content, at any time, without obligation to notify any person or entity of
such revisions or changes.
524671
Issue: Integrators threads are not started when server starts.
Currently, the Sentinel Link Integrator is not initialized and started until
they receive their first event from an action. This is because it may have
events stored in its queue that should be forwarded. When the Integrator
starts, a background thread is also started to process this.
Workaround: If Integrator is not sending events, either because no events
are happening or events are being filtered by rules, you must generate a
fake event that does not get filtered in order to get your Integrator started.
To determine if the Integrator thread is started, search for a message in
the log that indicates that the Integrator has started. It will be logged by the
StoreAndForward logger
(esecurity.ccs.comp.Integrator.slink.StoreAndForward), and will have a
message similar to the following:
Thread processing messages from store and forward queue
starting up
.
or
SentinelLinkStoreAndForward thread starting up
.
NOTE:
The actual message might change, so search for messages
logged by the StoreAndForward logger.
526364
Issue: Some connector documentation has the wrong version of the
connector stated in the documentation. For example, the documentation
may say 6r5 when the version of the connector is really 6r6.
Workaround: This is a typo. To determine the correct version of the
connector, open the Event Source Manager Interface, select the
connector from the list of connectors on the left hand side of the interface,
and click the
info
button.
Issue Number
Description
