Well since there are a lot of errors cropping up of different types, maybe we should start asking people to turn on the logging options.

Why I say this.
There is extra logging for
-file transfers (lots).
-screensaver. !
-scheduler choices.
-shared memory use
-lots of info about starting and stopping and checkpointing of tasks.

We could get people to delete the current error-log files run for a bit and then post some results.

Of course it will take time for us to understand a lot of it BUT we will and also the project may notice problems.

Link to the BOINC client debugging page
http://boinc.berkeley.edu/client_msgs.php

...
The following messages are disabled by default (typically they generate lots of output, and are used for specific debugging purposes):

<cpu_sched> CPU scheduler actions (preemption and resumption)
<cpu_sched_debug> Explain CPU scheduler decisions
<rr_simulation> Results of the round-robin simulation used by CPU scheduler and work-fetch
<debt_debug> Changes to project debt
<task_debug> Low-level details of process start/end (status codes, PIDs etc.), and when applications checkpoint.
<work_fetch_debug> Work fetch policy decisions
<unparsed_xml> Show any unparsed XML
<state_debug> Show summary of client state after scheduler RPC and garbage collection; also show garbage collection actions, and when state file is read/written.
<file_xfer_debug> Show completion status of file transfers
<sched_op_debug> Details of scheduler RPCs
<http_debug> Debugging information about HTTP operations
<proxy_debug> Debugging information about HTTP proxy operations
<time_debug> Updates to on_frac, active_frac, connected_frac.
<http_xfer_debug> Debugging information about network communication
<measurement_debug> Debugging information about CPU benchmarks, platform, disk space, etc.
<poll_debug> Show what poll functions do
<guirpc_debug> Debugging information about GUI RPC operations
<scrsave_debug> Debugging information about the screen saver.
<app_msg_debug> Shared-memory messages from applications.
<mem_usage_debug> Application memory usage.
<network_status_debug> Network status (whether need physical connection).

---

Team mauisun.org

For example, to see what responses are made when the screensaver/graphics or has started and stopped... I don't know what happens when it crashed as it never has for me.

You would stop boinc
create a file called cc_config.xml

<cc_config>
<log_flags>
<scrsave_debug>1</scrsave_debug>
</log_flags>
</cc_config>

and save it in the boinc folder.
Start boinc again.

On later version of boinc 5.6.x+ I think, it tells you at the start which log flags oare active.
Not sure with 5.4.9/11, sorry.



Typical output in messages tab (boinc 5.7.2)
08/11/2006 15:33:05||Starting BOINC client version 5.7.2 for windows_intelx86
08/11/2006 15:33:05||log flags: task, file_xfer, sched_ops, scrsave_debug
08/11/2006 15:33:05||Libraries: libcurl/7.15.5 OpenSSL/0.9.8a zlib/1.2.3

Some message I get 'testing' the screensaver in display properties (boinc running in background)
08/11/2006 16:11:50||[scrsave_debug] ACTIVE_TASK::check_graphics_mode_ack(): got graphics ack <mode_hide_graphics/> for 1dtj__ETABLE_TEST_ABRELAX_rhh13sm6__1470_174_0, previous mode <mode_fullscreen/>
08/11/2006 16:11:50||[scrsave_debug] SS_LOGIC::reset(): resetting 1dtj__ETABLE_TEST_ABRELAX_rhh13sm6__1470_174_0
08/11/2006 16:11:50||[scrsave_debug] ACTIVE_TASK::request_graphics_mode(): requesting graphics mode <mode_hide_graphics/> for 1dtj__ETABLE_TEST_ABRELAX_rhh13sm6__1470_174_0
08/11/2006 16:11:50||[scrsave_debug] SS_LOGIC::stop_ss(): stopping screen saver
08/11/2006 16:11:50||[scrsave_debug] ACTIVE_TASK::check_graphics_mode_ack(): shutting down the screensaver
08/11/2006 16:11:50||[scrsave_debug] CLIENT_STATE::get_next_graphics_capable_app(): get_next_app: 1dtj__ETABLE_TEST_ABRELAX_rhh13sm6__1470_174_0

Launching Graphics in BoincManger
08/11/2006 16:34:18||[scrsave_debug] ACTIVE_TASK::request_graphics_mode(): requesting graphics mode <mode_window/> for 1hz6A_ETABLE_TEST_ABRELAX_rhh13sm6__1470_178_0
08/11/2006 16:34:20||[scrsave_debug] ACTIVE_TASK::check_graphics_mode_ack(): got graphics ack <mode_window/> for 1hz6A_ETABLE_TEST_ABRELAX_rhh13sm6__1470_178_0, previous mode <mode_hide_graphics/>

---

Team mauisun.org