S@H V5.17

[Simon]

Sorry,

but you're wrong.
5.17 has NOT been released to the main S@H project.

What you're experiencing is a direct result of you crunching Beta as well as the main project. Beta thinks 5.17 is the app you need, and BOINC seemingly cannot distinguish between the Beta and the standard app right now.

Again: 5.17 has NOT been released for the main S@H project. Please do not infer that is so

Regards,
Simon.

[Gecko_R7]

I crunch Beta as well and had the same issue as others have had.
BOINC can't distinguish between the projects. The app_info work-around doesn't mean one will receive 5.17-designated WUs for the main project, it just tells BOINC to report that the WU was completed by version 5.17 (when it was actually completed by 5.15).

My WU names on Beta start w/ 02ap.....and are crunching w/ 5.17 ap
On the main project, they start w/ 12ap, 13ap etc. and crunch w/ Simon's finest!

Easy to confirm on the WU info on the result ID.

Cheers!

[Bruno G Olsen]

I've just placed the following app_info.xml in the beta-folder, to see if that would help - don't know yet if it does, but I thought it was worth a try

< app_info>
    < app>
        < name>setiathome_enhanced< /name>
    < /app>
    < file_info>
        < name>setiathome_5.17_windows_intelx86.exe< /name>
        < executable/>
    < /file_info>
    < app_version>
        < app_name>setiathome_enhanced< /app_name>
        < version_num>517< /version_num>
        < file_ref>
            < file_name>setiathome_5.17_windows_intelx86.exe< /file_name>
            < main_program/>
        < /file_ref>
    < /app_version>   
< /app_info>

(note: added a space in all tags for this post)

[Bruno G Olsen]

nope, it didn't help. Currently running un-optimized

[Dirk Sadowski]

nope, it didn't help. Currently running un-optimized

Hello!

At S@H there is maybe a thread to help you!

Chicken apps and 5.17 release....

Greetings!

[pepperammi]

Hi. I notice I'm starting to get 5.17 wu's. My old app_info.xml file went up to 5.17 but never downloaded then before so has 5.17 maybe gone wild now? or just something slightly different with this app_info (with the rev2 apps)? I know you modified it so would be OK with the beta projects but as I say my last one was too.

[Simon]

That's entirely normal -

I included an updated app_info.xml in the 2.0 releases because there remain some problems with 5.4.x and prior BOINC versions when you run both the Beta and the main project for SETI. Thing is, if you do not include a 5.17 entry for those hosts, they will just error out a lot of WUs and make people very unhappy

So BOINC now thinking your app version being 5.17 and requesting WUs for that version is normal, and quite okay. For the moment, the main project does not send out any WUs that cannot be processed by 5.15 in any case.

HTH,
Simon.

[pepperammi]

Für Reinigung danke, die herauf.
Hoffnung übersetzte nicht die falsch.

[Simon]

ROFLMAO.

Er,

"For cleaning thanks, her upwards.
Hope (noun) translated not her wrong."

or, rather, maybe,

"Thanks for clearing that up.
Hope I/it didn't translate that incorrectly."

Well you're welcome, I think!

 

[pepperammi]

  I'll stick to English

[lgm]

Hi
I'm using the SSE 3 opt app for S@h, but am having severe troubles since starting to crunch for SETI Beta. I get the following messages:
|SETI@home|Can't handle task 07mr99aa.8657.16736.572166.3.136 in scheduler reply

and

|SETI@home|State file error: missing task 07mr99aa.8657.16736.572166.3.136

I've heard there is a problem with the app_info.xml file, and it arises from the inability to recognise the difference between the two project names.  However, this seems a little odd, as the opt app is in the S@h folder only, and I thought it should not affect the Beta project, that being held in a separate folder.

Any help on this subject would be well appreciated.

lgm

[lgm]

Isn't that just typical?
5 minutes after calling for help here, I find the answer on the SETI boads!

S@h doesn't recognise version 5.17, used by Beta.

I've edited the app_info.xml file to read version number 517, instead of 514.

Have I done good?

lgm

[Simon]

Yup!

Happy crunching,
Simon.

[lgm]

Apparently not!

Every downloaded WU I have received from S@h now has a compute error

18/12/2006 10:57:52 PM|SETI@home|No main program specified

18/12/2006 10:57:52 PM|SETI@home|Unrecoverable error for result 07mr99aa.8657.19105.865918.3.195_3 (Couldn't start or resume: -161)

My second machine hasn't had any of this trouble.  It's also crunching S@h and Beta.   It's a 1 Gig P3 running Server 2003.
The troublesome machine is running XP Pro SP2.  It's a 2.8 Gig Celeron with 1 Gig of RAM, if that's any help.

I've been battling thiese problems for over a week now.  I reformatted the HDD recently, and all was running sweetly.

It's a good job I keep my hair short, or I'd be pulling it out by now!

[lgm]

The saga continues... I hope I'm not boring you!
Machine 1 (XP SP2) seems to be running ok now.  I installed the version 2.0 opt app on both machines

However, machine (Server 2003) gives the following message:

No URL for file transfer of setiathome-5.15-kwsn-mmx.exe

and:

Can't initialise file transfer for setiathome-5.15-kwsn-mmx.exe

After pressing update to report a finished WU, I get the following:

Couldn't start download of setiathome-5.15-kwsn-mmx.exe
URL (null): invalid URL

I re-installed BOINC 5.4.11 on both machines, just in case there was a corruption somewhere.

Am I going insane?

You betcha!

I checked transfers, and found BOINC was attempting to upload setiathome-5.15-kwsn-mmx.exe
I aborted the transfer, and am now waiting patiently for the next problem.

If nothing else, this has increased my respect for programmers!