I have a workunit, 2x82_000157746_0, which has recently started over for some reason. No indications as to why this occurred, but it had sent up the 11th trickle. I run the CLI version of BOINC set up as a service. This is somewhat disconcerting. It has sent up the 1st trickle since restarting, but doesn\'t report anything on the web page for that workunit. I\'m wondering if it is even still functioning properly anymore. I am also running another model on the other processor, so I don\'t just want to detach/reattach, since that would toss the other model, which is running properly. Any thoughts/suggestions would be appreciated.

If the same model restarts the trickles will not be recounted. Once it gets past the place it was before the trickles will start being counted again.
<br>John Keck -- BOINCing since 2002/12/08 -- <a href="http://www.boinc.dk/index.php?page=user_statistics&amp;project=cpdn&amp;userid=191"><img border="0" height="80" src="http://191.cpdn.sig.boinc.dk?188"></a>

&gt; If the same model restarts the trickles will not be recounted. Once it gets
&gt; past the place it was before the trickles will start being counted again.
&gt; <br>John Keck -- BOINCing since 2002/12/08 -- <a> href="http://www.boinc.dk/index.php?page=user_statistics&amp;project=cpdn&amp;userid=191"&gt;<img> border="0" height="80" src="http://191.cpdn.sig.boinc.dk?188"&gt;</a>
&gt;
&gt;
Any idea why this would occur in the first place? There must be a error somewhere for this to occur. Is there someplace I can check to see what that error might be?

Go to BOINC folder look at Stderr or Stdout, they may have some info on the problem,

&gt; Go to BOINC folder look at Stderr or Stdout, they may have some info on the
&gt; problem,
&gt;
&gt;
Actually, the files have not been written to since 10/31, about when I switched from the GUI to the CLI running as a service. I don't know if the CLI client is supposed to be writing to these files or not.

&gt; Actually, the files have not been written to since 10/31, about when I
&gt; switched from the GUI to the CLI running as a service. I don't know if the
&gt; CLI client is supposed to be writing to these files or not.

The CLI client service doesn't write to those files. It used to write messages to the application event log, but that was disabled because they were swamping everything else. The CLI client service now silently discards all BOINC log messages. In any case, you're more likely to get useful information from the CPDN specific logs in the climatepredition.net/2x82_000157746 directory.

You won't see any more trickles for the job on your account page until it gets to its 12th trickle (timestep 129624).
<br><a href="http://www.teampicard.net"><img src="http://www.teampicard.net/templates/fisubice/images/phpbb2_logo.jpg"></a><a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/team_display.php?teamid=3">Join us here</a>

&gt; The CLI client service doesn't write to those files. It used to write
&gt; messages to the application event log, but that was disabled because they were
&gt; swamping everything else. The CLI client service now silently discards all
&gt; BOINC log messages. In any case, you're more likely to get useful information
&gt; from the CPDN specific logs in the climatepredition.net/2x82_000157746
&gt; directory.

stdout_um.txt was updated at about the same time as the restart:

Starting hadsm3 model for ID# 2x82_000157746...
Changing to slots directory C:\Program Files\BOINC\slots\1