Understanding the log file
When a server is started, the initial entries in the
log file contain useful information about the server's
configuration. The following text is an exert from a
Realm Server log during startup:
[Tue Jan 04 15:22:18 GMT 2005],Log,Startup: Starting
realm server scheduler entries
[Tue Jan 04 15:22:18 GMT 2005],Log,================================================
[Tue Jan 04 15:22:18 GMT 2005],Log, Copyright ©
my-Channels. All rights reserved
[Tue Jan 04 15:22:18 GMT 2005],Log,Start date = Tue
Jan 04 15:22:18 GMT 2005
[Tue Jan 04 15:22:18 GMT 2005],Log,
[Tue Jan 04 15:22:18 GMT 2005],Log,Realm Server Details
:
[Tue Jan 04 15:22:18 GMT 2005],Log, Realm Server name
= Nirvana
[Tue Jan 04 15:22:18 GMT 2005],Log, Realm Server version
= $Name: $ - $Revision: 1.2 $
[Tue Jan 04 15:22:18 GMT 2005],Log, Build Number = Build
3551
[Tue Jan 04 15:22:18 GMT 2005],Log, Build Date = December
10 2004
[Tue Jan 04 15:22:18 GMT 2005],Log, Data Directory =
C:\Nirvana 3.0.3551\server\Nirvana\data
[Tue Jan 04 15:22:18 GMT 2005],Log, Realm(s) Reloaded
= 1
[Tue Jan 04 15:22:18 GMT 2005],Log, Channels Reloaded
= 6
[Tue Jan 04 15:22:18 GMT 2005],Log, Queues Reloaded
= 0
[Tue Jan 04 15:22:18 GMT 2005],Log, Interfaces Reloaded
= 1
[Tue Jan 04 15:22:18 GMT 2005],Log,
[Tue Jan 04 15:22:18 GMT 2005],Log,Operating System
Environment :
[Tue Jan 04 15:22:18 GMT 2005],Log, OS Name = Windows
XP
[Tue Jan 04 15:22:18 GMT 2005],Log, OS Version = 5.1
[Tue Jan 04 15:22:18 GMT 2005],Log, OS Architecture
= x86
[Tue Jan 04 15:22:18 GMT 2005],Log,
[Tue Jan 04 15:22:18 GMT 2005],Log,Java Environment
:
[Tue Jan 04 15:22:18 GMT 2005],Log, Java Vendor = Sun
Microsystems Inc.
[Tue Jan 04 15:22:18 GMT 2005],Log, Java Vendor URL
= http://Java.sun.com/
[Tue Jan 04 15:22:18 GMT 2005],Log, Java Version = 1.4.2_04
[Tue Jan 04 15:22:18 GMT 2005],Log, Memory Allocation
= 512 MB
[Tue Jan 04 15:22:18 GMT 2005],Log, Memory Warning =
435 MB
[Tue Jan 04 15:22:18 GMT 2005],Log, Memory Emergency
= 481 MB
[Tue Jan 04 15:22:18 GMT 2005],Log, Clock Adjustment
= 0ms
[Tue Jan 04 15:22:18 GMT 2005],Log, Time Zone = Greenwich
Mean Time
[Tue Jan 04 15:22:18 GMT 2005],Log, Security Provider
0 = SUN version 1.42
[Tue Jan 04 15:22:18 GMT 2005],Log, Security Provider
1 = SunJSSE version 1.42
[Tue Jan 04 15:22:18 GMT 2005],Log, Security Provider
2 = SunRsaSign version 1.42
[Tue Jan 04 15:22:18 GMT 2005],Log, Security Provider
3 = SunJCE version 1.42
[Tue Jan 04 15:22:18 GMT 2005],Log, Security Provider
4 = SunJGSS version 1.0
[Tue Jan 04 15:22:18 GMT 2005],Log,================================================
[Tue Jan 04 15:22:18 GMT 2005],Log,Startup: Realm Server
Startup sequence completed
[Tue Jan 04 15:22:18 GMT 2005],Log,Startup: Starting
Realm status monitoring
[Tue Jan 04 15:22:18 GMT 2005],Security,Startup: Generated
RSA Key Pair of 1024 bits
[Tue Jan 04 15:22:18 GMT 2005],Log,Startup: Stored Certificate
and private key in servers keystore
[Tue Jan 04 15:22:18 GMT 2005],Log,Startup: Completed
Realm Public and Private RSA Key
[Tue Jan 04 15:22:18 GMT 2005],Log,Startup: Cluster
cryptograhic initialisation, complete
The above sequence of log entries can be found at the
beginning of the Nirvana log file, and shows information
such as when the realm was started, the build number
and build date of the Nirvana Server, as well as environmental
informaiton like, OS, Java version, timezone.
Each log entry contains a date, the log level as well
as the log message itself, in the format:
[DATE_TIME],LOG_LEVEL,Message
The Nirvana log level is a level from 0 to 7 that
determines what information is written to the log. Log
level 0 is the most verbose level of logging and on
a heavily utilised server will produce a lot of log
output. Log level 7 is the least verbose level, and
will produce low levels of log output. The log level
of each log message corresponds to a value from 0 to
7. The following list explains the log file messages
levels and how they correspond to the values:
0 - Success (Log level 0 will output any log entries
with a level of 0 or above)
1 - Informative (Log level 1 will output any log entries
with a level of 1 or above)
2 - Warning (Log level 2 will output any log entries
with a level of 2 or above)
3 - Failure (Log level 3 will output any log entries
with a level of 3 or above)
4 - Fatal (Log level 4will output any log entries
with a level of 4 or above)
5 - Security (Log level 5 will output any log entries
with a level of 5 or above)
6 - Audit (Log level 6 will output any log entries
with a level of 6 or above)
7 - Log (Log level 7will output only log entries with
a level of 7)
Log levels can be changed dynamically on the server
by using the Config
Panel. The log file has a maximum size associated
with it. When the maximum file size is reached, the
log file will automatically roll, and rename the old
log file to _old and create a new log file . The maximum
size for a log file is set to 10000000 bytes (approximately
10MB). This value can be changed within the nserver.lax
file in the server/bin directory of your install. You
need to modify the -DLOGSIZE property within this file
to change the size.
The LogFile Panel
The Enterprise Manager provides a panel for each realm
where the log file can be viewed. To view the log file,
click on the realm node from the namespace and select
the panel labelled 'LogFile'. This will show the live
log messages for the selected realm. The log panel will
automatically replay the last 20 log entries from the
Realm Server and then each entry thereafter. The image
below shows an example of the log panel for a selected
realm:
The log panel also provides the ability to stream the
log messages to a local file. Clicking on the button
labelled 'Start' from the log panel will prompt you
to enter the name of the file you wish to stream the
log messages to. The stream can be stopped by clicking
the same button again.
|
