Changes between Version 7 and Version 8 of ServerDebug

Timestamp:

Mar 28, 2012, 2:20:31 PM (13 years ago)

Author:

davea

Comment:

--

ServerDebug

@@ -6 +6 @@
 
 Each server component (scheduler, feeder, transitioner, etc.) has its own log file.
-Most error conditions are reported in the log files;
-make sure you know where they are.
-If you're interested in the history of a particular WU or result,
+These files are in the '''log_HOSTNAME''' subdirectory of the project directory.
+Most error conditions are reported in the log files.
+
+If you're interested in the history of a particular job,
 grep for `WU#12345` or `RESULT#12345` (where 12345 represents the ID) in the log files.
 The [HtmlOps html/ops pages] also provide an interface for this.
@@ -16 +17 @@
  * Scheduler: set the desired [ProjectOptions#Scheduler:logging logging options]
  * File upload handler: set [ProjectOptions#misc fuh_debug_level].
- * Other components: pass "-d N" (1=least verbose, 3=most verbose)
+ * Other components: pass "-d N" (1=least verbose, 4=most verbose)
 
 == Debugging the scheduler ==
@@ -32 +33 @@
 {{{
 gdb cgi
-(set a breakpoint)
+(set a breakpoint if desired)
 r < scheduler_request_X.xml
 }}}
@@ -41 +42 @@
 
 This is useful for figuring out why your project is generating 'no work available' messages.
+
 As an alternative to this, edit `sched/handle_request.cpp`,
 and put a call to `debug_sched("debug_sched");` just before `sreply.write(fout, sreq);`.
@@ -63 +65 @@
 == Database query tracing ==
 
-If you run server components with debug level 4,
+If you run server components with '''-d 4''',
 their database queries will be logged.
 This is verbose but extremely useful for tracking down database-level problems.