I have started getting a lot of "exited with zero status but no "finished" file" messages and it keeps telling me to Reset BOINC.
What does that mean exactly? I have closed it and restarted it, and also rebooted the computer that is happening on but it is still happening. I had a total power failure in the computer room yesterday, a UPS was found to be tripping the GFI outlet in the room.
The interesting thing is that they do not seem to log an errored WU.
SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

I have started getting a lot of "exited with zero status but no "finished" file" messages and it keeps telling me to Reset BOINC.

The message is:
"If this happens repeatedly you may need to reset the project."

Don't do that (the reset) - it will not help.
This message is intended for stock users in case they received broken .exe file (e.g. partial download)

"exited with zero status but no 'finished' file" may be caused by:
- heavy load on the CPU/HDD by some other program (e.g. antivirus scheduled scan)
- realtime antivirus protection locking files for too long (while checking them 'on-the-fly')
- computer clock fluctuating back/forth in time (by more than 30 s)

("exited with zero status but no 'finished' file" does not cause the tasks to error, they restart from the checkpoint)

I have started getting a lot of "exited with zero status but no "finished" file" messages and it keeps telling me to Reset BOINC.

The message is:
"If this happens repeatedly you may need to reset the project."

Don't do that (the reset) - it will not help.
This message is intended for stock users in case they received broken .exe file (e.g. partial download)

"exited with zero status but no 'finished' file" may be caused by:
- heavy load on the CPU/HDD by some other program (e.g. antivirus scheduled scan)
- realtime antivirus protection locking files for too long (while checking them 'on-the-fly')
- computer clock fluctuating back/forth in time (by more than 30 s)

("exited with zero status but no 'finished' file" does not cause the tasks to error, they restart from the checkpoint)

Thanks, and that is exactly what is happeinging. Something is going wrong with my WHS Connector software on this computer and it causes the normally 100% use on each core to drop to near zero. I did not associate the two happenings.

As for the misquote, that is what happens when you can not cut and paste between computers (unless I were to pay for LogMeIn).

I am going to have to try a complete system restore as the restore of the Connector software fails with a missing file message. As long as I do not try to backup this computer to the server, all runs as it should. Again, right on and Thanks.
SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

If that causes lost net connection - yes, I think I remember something about 'bug' in BOINC (or in libcurl.dll ?)
- boinc.exe uses synchronous DNS and waits 'forever' for response from DNS server so boinc.exe do not communicate with the apps for too long and they exit.

can not cut and paste between computers (unless I were to pay for LogMeIn)

I'm currently having the task restart problem as well. I think what I'll do for a start is (a) suspend computation when the virus scanning is taking place (around 4 AM) and (b) also tell my backup program (Carbonite) not to back up any of my SETI files.

I'm currently having the task restart problem as well. I think what I'll do for a start is (a) suspend computation when the virus scanning is taking place (around 4 AM) and (b) also tell my backup program (Carbonite) not to back up any of my SETI files.

I presume this is your Windows system. This can happen when your on-board clock doesn't keep very close time and is adjusted from the network infrequently enough that the correction becomes large. First check in Control Panel that your clock is set to synchronise to "internet time", and set your preferred server to an NTP server close to you. Then check and optionally change the Registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\SpecialPollInterval using regedit -- the default is 604800 (seconds, i.e. a week), I have mine set to 14400 (four hours).

OK. I've done that. I'll check back in a couple of days to see how it's gone. BTW, my Ubuntu 12.04 LTS box is having similar problems. How do I check on doing NTP there?

Look up ntp and ntpd (e.g.here) -- for me it usually "just works". On my Ubuntu server there's a control programme in /etc/init.d/ntp which has a note that it runs by default in run-levels 2, 3, 4, and 5. Information on what servers to poll is held in /etc/ntp.conf. The command 'ntpq -p' will show what servers you are currently synchronised with (if any). The default polling interval appears to be 1024 seconds, but can be controlled by minpoll and maxpoll parameters in /etc/ntp.conf.

You may also need to allow the connection on your firewall. NTP uses UDP port 123. So you would have to allow an outbound connection from your LAN to "any" address on the WAN/internet on UDP port 123.

Cheers
Jeff

Another option may be to have the machine send its NTP request to the router. Which would be configured to sync its time form the internet. This is what I do at home.SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the BP6/VP6 User Group today!