Resuming... the project is going to the frak

Some will go, and some will stay, doesn't mean the project is going to go belly up, or frak as you put it. As I said before, people will come, people will return, you see it on all the projects. Not the end of the world in my eyes.

Enjoy! :-)

The users keep going up and the wu's 150k+ now, but when many users realize there is no benifit to run this for more credits it'll go down.


Yea, I need to find a back-up project now. Atleast Rosetta has been running good letely.

Hahaha... don't worry about that... wait and see... only that... Travis was pushed his 'self-destruction' button... Only wait, and see...:)

(sorry for my bad english)

Oh Logan, don't be afraid of your bad English; there are things that are worse...
Bad temper, bad logic, being sulky...

Have you ever read clusters posts regarding crediting policy?
And he is one of the most active optimizers and one of those sharing their appl.

The users keep going up and the wu's 150k+ now, but when many users realize there is no benifit to run this for more credits it'll go down.


Yea, I need to find a back-up project now. Atleast Rosetta has been running good letely.

toast

Travis... A lot of users were reported the same with stock app... Don't try to use the excuse of third party apps... The problem is in your side, and all of us know it...

I'm not blaming 3rd party apps, I'm just trying to narrow down where the error is. You're always so negative man :P

Our database settings got lost when everything went down, what I'm thinking is that we might have some kind of error where it might be dropping connections early or something along those lines, which is all i can think of that would be making the application crash, considering the applications were working fine before, and that we're not doing anything new when we're generating the workunits...

If the problem is with the stars files, then how come I can take the stars files from a machine not reporting any errors and copy them to another machine that has about 50% errors and still have the same problem?

Well, then that probably isn't the issue :P Are you using an optimized app? I'm wondering if something went wrong with them for whatever reason when the database got corrupted.

Again, it's pretty hard for me to debug an optimized application because they aren't something we've released, so it could be hardware problems or any other thing.

One thing I think might be happening is that when you use the stock app the boinc client tries to verify the downloaded workunit files with a checksum, and I'm pretty sure the client wont do this for an optimized application. So what might be happening is some of the workunit files might not be downloading completely or correctly, and the optimized app runs on them anyways and errors out.

I tried the zslip optimized application in my AMD 5200 X2 - Windows XP 64b but all the Wu crashed.
I'm asking if those applications are accepted by the project administrator !!!
Now I discard those application and return to a normal application.

http://www.zslip.com/

I did the same with a 64bit '03 intel server w/3.0 xeon's and cant get any of these apps. to work so I guess I'll go back to linux and PG.

I guess the problem was that the SSE3_x64 app on zslip.com was actually the GPU app for ATI cards.
Btw, there is a new version of it. I will post it in the code discussion forum.

Thanks Cluster Physik, I'll update zslip.com when I get to that code

[edit] zslip.com is updated with the above

Tryed the app. for 64bit windoz and this is what I get,any ideas?

2/12/2009 12:30:57 PM|Milkyway@home|Starting nm_s82_r10_623695_1234462983_0
2/12/2009 12:30:57 PM|Milkyway@home|Starting task nm_s82_r10_623695_1234462983_0 using milkyway version 17
2/12/2009 12:30:58 PM|Milkyway@home|Computation for task nm_s82_r10_623695_1234462983_0 finished
2/12/2009 12:30:58 PM|Milkyway@home|Output file nm_s82_r10_623695_1234462983_0_0 for task nm_s82_r10_623695_1234462983_0 absent

it happened again about 8 hours later. all the wu's erred and boinc rescheduled for 24 hours later, so it didn't update.