2004-09-20 12:04:54 [SETI@home] Result 06my04ab.9911.22321.273584.238_2 exited with zero status but no 'finished' file
2004-09-20 12:04:54 [SETI@home] If this happens repeatedly you may need to reset the project.

What does that mean? How do I reset the project? Please help!

> 2004-09-20 12:04:54 [SETI@home] Result 06my04ab.9911.22321.273584.238_2 exited
> with zero status but no 'finished' file
> 2004-09-20 12:04:54 [SETI@home] If this happens repeatedly you may need to
> reset the project.
>
> What does that mean? How do I reset the project? Please help!
>

this should be posted in the Questions and Problems area.

Sounds like a bug to me. :) ...
<p>
For BOINC Documentaion: Click Me!

> 2004-09-20 12:04:54 [SETI@home] Result 06my04ab.9911.22321.273584.238_2 exited
> with zero status but no 'finished' file
> 2004-09-20 12:04:54 [SETI@home] If this happens repeatedly you may need to
> reset the project.
>
> What does that mean? How do I reset the project? Please help!
>
Martin,

I was getting this error a lot on one particular machine with boinc 4.08 on Win XP SP2, after many uninstalls, re-installs, then several looks in task manager, to find out what on earth was going on, why it wasn't processing at all, just looping with that silly error, I noticed that somehow, the CLI version of boinc was also being initiated, was running at the same time as the graphic version, and was causing a conflict.
I have installed boinc CLI as a service, but chose not to run it, because, I can't yet find a satifactory method of monitoring it, that doesn't involve installing god knows what in the way of extra support software; so the CLI service is set on manual/stopped (not paused).
I still don't know what was causing the CLI version to run without me telling it to do so, and, I'm sure I haven't changed anything since, but, on the exact same setup, it now behaves itself again, unfortunately, the problem cost me two CPDN wu's and countless SETI wu's.
I believe boinc 4.09 is setup to disallow running the CLI and the GUI together so problems like this shouldn't happen, but on the same machine, it just crunched seti all day long without touching the CPDN work, so I rolled back to 4.08.


Ken Phillips - UK

A big paste to give the idea.

SETI@home - 2004-09-20 13:54:13 - Restarting result 26ap04aa.7733.23617.928404.213_0 using setiathome version 4.03
SETI@home - 2004-09-20 13:55:47 - Result 26ap04aa.7733.23617.928404.213_0 exited with zero status but no 'finished' file
SETI@home - 2004-09-20 13:55:47 - If this happens repeatedly you may need to reset the project.
SETI@home - 2004-09-20 13:55:47 - Restarting result 26ap04aa.7733.23617.928404.213_0 using setiathome version 4.03
SETI@home - 2004-09-20 13:56:37 - Computation for result 26ap04aa.7733.23617.928404.213 finished
SETI@home - 2004-09-20 13:56:37 - Starting result 26ap04aa.7733.23570.211072.198_1 using setiathome version 4.03
SETI@home - 2004-09-20 13:56:37 - Started upload of 26ap04aa.7733.23617.928404.213_0_0
SETI@home - 2004-09-20 13:56:47 - Finished upload of 26ap04aa.7733.23617.928404.213_0_0
SETI@home - 2004-09-20 13:56:47 - Throughput 5556 bytes/sec
SETI@home - 2004-09-20 16:37:21 - Computation for result 26ap04aa.7733.23570.211072.198 finished
SETI@home - 2004-09-20 16:37:21 - Starting result 06my04ab.9911.21504.715898.84_3 using setiathome version 4.03
SETI@home - 2004-09-20 16:37:21 - Started upload of 26ap04aa.7733.23570.211072.198_1_0
SETI@home - 2004-09-20 16:37:31 - Finished upload of 26ap04aa.7733.23570.211072.198_1_0
SETI@home - 2004-09-20 16:37:31 - Throughput 6923 bytes/sec

So what's that all about then? It looks like it tried and tried and finally got it right.
No CLI versions running here.

Bug? Or bug eyed monster sending tricky signals?

> Martin,
>
> I was getting this error a lot on one particular machine with boinc 4.08 on
> Win XP SP2, after many uninstalls, re-installs, then several looks in task
> manager, to find out what on earth was going on, why it wasn't processing at
> all, just looping with that silly error, I noticed that somehow, the CLI
> version of boinc was also being initiated, was running at the same time as the
> graphic version, and was causing a conflict.
> I have installed boinc CLI as a service, but chose not to run it, because, I
> can't yet find a satifactory method of monitoring it, that doesn't involve
> installing god knows what in the way of extra support software; so the CLI
> service is set on manual/stopped (not paused).
> I still don't know what was causing the CLI version to run without me telling
> it to do so, and, I'm sure I haven't changed anything since, but, on the exact
> same setup, it now behaves itself again, unfortunately, the problem cost me
> two CPDN wu's and countless SETI wu's.
> I believe boinc 4.09 is setup to disallow running the CLI and the GUI together
> so problems like this shouldn't happen, but on the same machine, it just
> crunched seti all day long without touching the CPDN work, so I rolled back to
> 4.08.
>
>
> Ken Phillips - UK


Ken, thanks for this answer. Unfortunately I do not understand a word! What is a CLI version? What is CPDN? I run the 4.02 (latest) version on a Mac with MacOS X 10.3.5. As far as I know there is no GUI version yet.

hi!

Before boinc 4.09 if client (setiathome) died it was just waiting forever.
I've seen this once or twice, the sollution was to restart boinc.

With 4.09 if setiathome crash, then it is noticed and restarted.
As it is said: do not worry unless you get plenty of those error messages
with different WUs.

Why it is crashing? Who knows, computers are evil.

BR
Iztok

>
> > Martin,
> >
> > I was getting this error a lot on one particular machine with boinc 4.08
> on
> > Win XP SP2, after many uninstalls, re-installs, then several looks in
> task
> > manager, to find out what on earth was going on, why it wasn't processing
> at
> > all, just looping with that silly error, I noticed that somehow, the CLI
> > version of boinc was also being initiated, was running at the same time
> as the
> > graphic version, and was causing a conflict.

> >Snip

> > I believe boinc 4.09 is setup to disallow running the CLI and the GUI
> together
> > so problems like this shouldn't happen, but on the same machine, it just
> > crunched seti all day long without touching the CPDN work, so I rolled
> back to
> > 4.08.
> >
> >
> > Ken Phillips - UK
>
>
> Ken, thanks for this answer. Unfortunately I do not understand a word! What is
> a CLI version? What is CPDN? I run the 4.02 (latest) version on a Mac with
> MacOS X 10.3.5. As far as I know there is no GUI version yet.


Martin,

Sorry for the confusion, I really should have looked up your computers before I replied before, then I wouldn't have waffled on about GUI's etc, You are quite right (to my knowledge) Mac OS X, being based on linux/unix, so far does not a GUI version of boinc, all it has is the Command Line Interpreter version, therefore the problem I had won't be affecting you.

CPDN is Climate Prediction dot net, another DC project that uses boinc, on my poor machines each workunit is scheduled to take about 2000 hours to complete!

Do you get the 'zero status but no 'finished' file' problem on both your macs, or just one?

If you want to reset the project on your computer, assuming the syntax is the same as the windoze CLI version, and further assuming the program binary is also called the same as on windoze, you type in something like 'boinc_cli -reset_project http://setiweb.ssl.berkeley.edu', from the same directory that you start boinc from, having not done this before, I think you'll need to stop boinc first before entering the command above, but someone more knowledgeable than I hopefully will correct me, I'm only just getting to grips with linux myself at 'Dummy' level, so I'm not at all sure about the OS X implementation.

Best wishes,

Ken Phillips - UK

>
> Do you get the 'zero status but no 'finished' file' problem on both your macs,
> or just one?
>
> If you want to reset the project on your computer, assuming the syntax is the
> same as the windoze CLI version, and further assuming the program binary is
> also called the same as on windoze, you type in something like 'boinc_cli
> -reset_project http://setiweb.ssl.berkeley.edu', from the same directory that
> you start boinc from, having not done this before, I think you'll need to stop
> boinc first before entering the command above, but someone more knowledgeable
> than I hopefully will correct me, I'm only just getting to grips with linux
> myself at 'Dummy' level, so I'm not at all sure about the OS X
> implementation.
>
> Best wishes,
>
> Ken Phillips - UK


Ken,

thanks for the continued support! I only experience this on one machine (only twice). I think I'll just continue crunching and see what happens. Last couple of results passed without problem.

Thanks again!

> Ken, thanks for this answer. Unfortunately I do not understand a word! What is
> a CLI version? What is CPDN? I run the 4.02 (latest) version on a Mac with
> MacOS X 10.3.5. As far as I know there is no GUI version yet.

Martin,

Some of what you want to know should be in here ... if it is not, drop me an e-mail and it will be added. I don't think I have added cpdn yet (bad Paul) ... but it is climate prediction.net which has both a classic stand alone version and a BOINC version.

It is a work in progress, so there are rough places (sorry about that, but there is only me) ... I am constantly adding new material, correcting mistakes and adding new errors, etc.

It is a terse set of documents because of space limitations. I only have about 270 pages so far... :)

As part of an "unofficial" effort to document the SETI@Home Powered by BOINC, the following documents have been written to aid you in the use of SETI@Home Powered by BOINC:

Documentation Menu (pdb)
Release Notes =

> 2004-09-20 12:04:54 [SETI@home] Result 06my04ab.9911.22321.273584.238_2 exited
> with zero status but no 'finished' file
> 2004-09-20 12:04:54 [SETI@home] If this happens repeatedly you may need to
> reset the project.
>
> What does that mean? How do I reset the project? Please help!
>

This happened to me on one of my mine. Turned out I had unplugged a network cable to use to test another computer and had forgot to plug it back in.





Terry - k4vh

[/i]