2002-07-29 19:01:38 +00:00
|
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
|
|
|
|
|
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
|
|
|
|
|
<html lang="en">
|
|
|
|
|
<head>
|
|
|
|
|
<title>Core Client: Debugging</title>
|
|
|
|
|
<meta name="generator" content="BBEdit 6.1.2">
|
|
|
|
|
</head>
|
|
|
|
|
<body>
|
|
|
|
|
<h2>Core Client: Debugging</h2> <h3>Core client logging and error
|
|
|
|
|
output</h3>
|
2002-04-30 22:22:54 +00:00
|
|
|
<p>
|
2002-07-29 19:01:38 +00:00
|
|
|
The core client writes error messages to stderr. This mechanism is
|
|
|
|
|
reserved for serious problems, i.e. those that reflect bugs in the core
|
|
|
|
|
client program or conditions that require user intervention.
|
|
|
|
|
Specifically, The client verifies that arguments to functions have valid
|
|
|
|
|
values, and will print a message to stderr on an invalid argument. These
|
|
|
|
|
error messages are formatted as <tt>error: CLASS_NAME.function:
|
|
|
|
|
error_statement argument</tt>. Common errors of this type include
|
|
|
|
|
unexpected NULL pointer arguments and negative lengths. Error numbers
|
|
|
|
|
are defined in <b>lib/error_numbers.h</b>.
|
|
|
|
|
</p>
|
2002-04-30 22:22:54 +00:00
|
|
|
<p>
|
2002-07-29 19:01:38 +00:00
|
|
|
In addition, the core client can write a variety of "logging"
|
|
|
|
|
information to stdout. The logging options are read from a file
|
|
|
|
|
<b>log_flags.xml</b>. This file has the following format:
|
|
|
|
|
</p>
|
2002-04-30 22:22:54 +00:00
|
|
|
<pre>
|
2002-07-29 19:01:38 +00:00
|
|
|
<log_flags>
|
2002-04-30 22:22:54 +00:00
|
|
|
[ flags ]
|
2002-07-29 19:01:38 +00:00
|
|
|
</log_flags>
|
|
|
|
|
</pre> The flags are as follows:
|
2002-04-30 22:22:54 +00:00
|
|
|
<dl>
|
2002-07-29 19:01:38 +00:00
|
|
|
<dt>
|
|
|
|
|
<task/>
|
|
|
|
|
</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
Log the start, restart and completion of computational tasks.
|
|
|
|
|
</dd>
|
|
|
|
|
<dt>
|
|
|
|
|
<file_xfer/>
|
|
|
|
|
</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
Log the start, restart and completion of file transfers.
|
|
|
|
|
</dd>
|
|
|
|
|
<dt>
|
|
|
|
|
<sched_ops/>
|
|
|
|
|
</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
Log connections with scheduling servers.
|
|
|
|
|
</dd>
|
|
|
|
|
<dt>
|
|
|
|
|
<state_debug/>
|
|
|
|
|
</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
Log changes to the "client state" data structures.
|
|
|
|
|
</dd>
|
|
|
|
|
<dt>
|
|
|
|
|
<task_debug/>
|
|
|
|
|
</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
Log debugging information about task execution.
|
|
|
|
|
</dd>
|
|
|
|
|
<dt>
|
|
|
|
|
<file_xfer_debug/>
|
|
|
|
|
</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
Log debugging information about file transfers.
|
|
|
|
|
</dd>
|
|
|
|
|
<dt>
|
|
|
|
|
<sched_op_debug/>
|
|
|
|
|
</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
Log the request and reply messages of exchanges with scheduling
|
|
|
|
|
servers.
|
|
|
|
|
</dd>
|
|
|
|
|
<dt>
|
|
|
|
|
<http_debug/>
|
|
|
|
|
</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
Log debugging information about HTTP operations.
|
|
|
|
|
</dd>
|
|
|
|
|
<dt>
|
|
|
|
|
<time_debug/>
|
|
|
|
|
</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
Log the passage of time.
|
|
|
|
|
</dd>
|
|
|
|
|
<dt>
|
|
|
|
|
<net_xfer_debug/>
|
|
|
|
|
</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
Log debugging information about network communication.
|
|
|
|
|
</dd>
|
2002-04-30 22:22:54 +00:00
|
|
|
</dl>
|
2002-07-29 19:01:38 +00:00
|
|
|
<h3>Application error output</h3>
|
2002-04-30 22:22:54 +00:00
|
|
|
<p>
|
2002-07-29 19:01:38 +00:00
|
|
|
The stderr of applications is automatically directed to a file. The
|
|
|
|
|
contents of this file are returned to the scheduling server and stored
|
|
|
|
|
in the database.
|
|
|
|
|
</p>
|
|
|
|
|
</body>
|
|
|
|
|
</html>
|
