
Sentinel 6.1 Rapid Deployment Data Access Service
49
no
vd
ocx
(e
n)
13
Ma
y 20
09
# < Set level of specific loggers here >
#
# Turns off all logging (disabled by default)
#.level=OFF
######
NOTE:
The logger
.level
is a wildcard logger name that refers to all loggers. Setting this logger’s
level will affect all loggers.
The available logging levels are:
OFF:
disables all logging
SEVERE (highest value):
indication that a component has malfunctioned or there is a loss/
corruption of critical data
WARNING:
if an action can cause a component to malfunction in the future or if there is non-
critical data loss/corruption
INFO:
audit information
CONFIG:
for debugging
FINE:
for debugging
FINER:
for debugging
FINEST:
(lowest value) – for debugging
ALL:
will log all levels
When one specifies a logging level, all log messages of that level and higher (in the above list) will
actually be logged. For example, if one specifies the INFO level, then all INFO, WARNING and
SEVERE message will be logged.
NOTE:
At 10 second intervals, the logging properties file will be checked to see if any changes
have occurred since it was last read. If the file has changed, the LogManagerRefreshService will re-
read the logging properties file. Therefore, it is not necessary to restart the processes to begin using
the updated logging levels.
Log messages are written to
<I
nstall_Directory
>/log
in the following files:
das_binary_0.*.log
das_core_0.*.log
The 0 indicates the unique number to resolve conflicts and the * indicates a generation number to
distinguish rotated logs. For example,
das_query0.0.log
is the log with index 0 (latest) file in a
rotated set of log files for the DAS Query process.
Log messages are also written to the process’s console (standard output). However, since the
processes are running as services, users do not have access to the console output. It is possible,
however, to capture the console output in the
sentinel0.*.log file
. This is useful, for example,
if the process is producing an error that is not printed to the process’s own log file. This can be
enabled by adding the following line to the
sentinel_log.prop
file:
esecurity.base.process.MonitorableProcess.level=FINEST
Содержание Sentinel Rapid Deployment 6.1
Страница 4: ...4 Sentinel 6 1 Rapid Deployment Reference Guide novdocx en 13 May 2009 ...
Страница 24: ...24 Sentinel 6 1 Rapid Deployment Reference Guide novdocx en 13 May 2009 ...
Страница 36: ...36 Sentinel 6 1 Rapid Deployment Reference Guide novdocx en 13 May 2009 ...
Страница 50: ...50 Sentinel 6 1 Rapid Deployment Reference Guide novdocx en 13 May 2009 ...
Страница 54: ...54 Sentinel 6 1 Rapid Deployment Reference Guide novdocx en 13 May 2009 ...
Страница 120: ...120 Sentinel 6 1 Rapid Deployment Reference Guide novdocx en 13 May 2009 ...
Страница 124: ...124 Sentinel 6 1 Rapid Deployment Reference Guide novdocx en 13 May 2009 ...
Страница 132: ...132 Sentinel 6 1 Rapid Deployment Reference Guide novdocx en 13 May 2009 ...
Страница 136: ...136 Sentinel 6 1 Rapid Deployment Reference Guide novdocx en 13 May 2009 ...