Cloud CM-IPMP Guide de dépannage télécharger pdf (Page 33)

node-XXX/ - Instantiated Rhino node.

config/ - Directory containing configuration files.

savanna/ - Savanna configuration files.

work/ - Rhino working directory.

rhino.pid - File containing the current process

ID of Rhino.

start-rhino.sh/ - Temporary directory.

config/

log/ - Default destination for Rhino logging.

rhino.log - Log containing all Rhino logs.

audit.log - Log containing licensing auditing.

encrypted.audit.log - Encrypted audit log

config.log - Log containing useful configuration

information, written on startup.

deployments/ - Used for storing source code for compiling

SBBs etc.

tmp/ - Temporary directory.

lib/ -

state/ -

The

config/

directory contains a set conﬁgurations ﬁles that Rhino uses at start-up. These are only used when a node is

(re)started. Once the node has joined the cluster, it stores and retrieves settings from the in-memory database (“MemDB”).

Some ﬁles are overwritten in the

config/

directory by the Rhino SLEE. Speciﬁcally, the

logging.xml

ﬁle is updated by the

Rhino SLEE at run-time when the administrator changes the SLEE’s logging conﬁguration using management tools. Logging

conﬁguration is stored in each node’s

logging.xml

ﬁle because this conﬁguration is needed before the rest of the cluster’s

conﬁguration can be loaded from the database and the node joins the cluster.

The

tmp/

deployments/

and

start-rhino.sh/

directories are temporary directories. The

deployments/

directory stores

ﬁles that Rhino uses to compile SLEE services. The

start-rhino.sh

directory is used when starting the Rhino SLEE – the

ﬁles in the

config

directory are copied here, and then all variable substitutions are made. The process of variable substitutions

means that occurrences of

@variables@

in the conﬁguration ﬁles are replaced with their values from the

config_variables

ﬁle.

The

log/

directory contains a set of log ﬁles which are constantly written and rotated as the Rhino SLEE outputs logging

information. The total size of this directory is automatically managed to not become excessive.

4.8.2 Logging output

The Rhino SLEE uses the Log4J libraries for logging. In the default conﬁguration, logging output is sent to both the standard

error stream (i.e. the user’s console) and also to log ﬁles in the

work/log

directory.

There are three logging ﬁles:

rhino.log

config.log

and

audit.log

rhino.log

contains all logs that Rhino has out-

putted.

config.log

contains changes to Rhino’s conﬁguration, and

audit.log

contains auditing information. There is also an

encrypted version of the audit log for use by Open Cloud support staff.

This output is the result of how the Rhino SLEE’s logging system has been set up. Chapter 10 explains more about this logging

system and how to conﬁgure it.

Log File Format

Each statement in the log ﬁle has a certain structure. Here is an example:

2005-12-13 17:02:33.019 INFO [rhino.alarm.manager] <Thread-4>

Alarm 56875825090732034 (Node 101, 13-Dec-05 13:31:54.373): Major

[rhino.license] License with serial ’107baa31c0e’ has expired.

This line starts with the current date: “2005-12-13 17:02:33.019” – the 13th of December, 2005 at 5:02pm, 33 seconds and

19 milliseconds. The milliseconds value is often useful for determining if log messages are related; if they occur within a few

Open Cloud Rhino 1.4.3 Administration Manual v1.1 24

1 2 ... 28 29 30 31 32 33 34 35 36 37 38 ... 200 201

Cloud CM-IPMP Guide de dépannage Page 33

Commentaires sur ces manuels