I hope to get an answer from someone in the know what could explain what I have witnessed over the past 24+hrs

the problem is WUs crunched but then seemingly disappear, no credit and I do not see them in pending and began after upgrading a persistent live linux distribution--more space. I began running boinc/seti on the new drive yesterday evening and realized early this morning the darned distribution inexplicably not persistent, i.e., I booted and discoveredno boinc/seti, nothing and immediately went back to the old distro. disaster.

of course, then the problem begins with which WUs crunched on the non-persistent distro. I am fairly certain I aborted the ones crunched and it was not that many after returning to the small but persistent distro.

question. could this absurdity throw a monkey in the credit approval process such that now the WUs are not recognized when submitted by this client?

NOTE: I am certain I am way past possible dups so this not about a bunch of dups re-crunched.

any thoughts and or explanations, and no laughing, would be appreciated. and no, I did not ensure the miserable distro persistent before booting.

just so you know, I am experimenting with very lite liveusb solutions and different thumbdrives, to explain what I mean by returning to previous distro, smaller usb.

thanks.

---

I was just investigating this issue regarding Sat 20 Sep 2008 11:00:37 PM EDT|SETI@home|Finished upload of 20au08ac.30922.7025.10.8.114_0_0 and found that the clent, in WU details, is presented as detached. that is inaccurate.

if any of you have an idea, please explain why the server suggests detached when this client not detached. I see the Detach option in the commands column of buttons.

this client is not detached but that is surely why I have had no credit now for 24+ hrs. I also wonder why it is the client would continue to crunch and upload results if detached.

please explain and recommendations welcome.

---

wow, you are a helpful lot.

decided to bit it and detach since the flawless servers suggest the cleint already there.

fingers crossed or another 2 year remedy break forthcoming.

thread dead.

---

wow, you are a helpful lot.

You didn't give us much to work with, and you asked for answers only from people who are "in the know."

Doesn't leave much wiggle-room.

---

My guess is that your live install did not have a chance to report the task(s) you had finished before your reboot. If the tasks are not reported they are in limbo and will eventually time out and be resent to other hosts. Tasks do not report immediately after upload to reduce the load on the server.

---

BOINC WIKI

BOINCing since 2002/12/8

wow, you are a helpful lot.

decided to bit it and detach since the flawless servers suggest the cleint already there.

fingers crossed or another 2 year remedy break forthcoming.

thread dead.

Wow, you're an impatient person. You gave it all of, what, a few hours?

wow, you are a helpful lot.

decided to bit it and detach since the flawless servers suggest the cleint already there.

fingers crossed or another 2 year remedy break forthcoming.

thread dead.

Well, I'm normally sleeping between 04:05:20 and 06:00:23 in the night, and besides, waiting less than 2 hours on an answer is really too little time even during the day...

Also, my Linux-experience is basically non-esistent, and I don't quote follow how you're running and not running BOINC... But, atleast, if it's a real "live" distro, as in booting from cd/dvd and not-write-anything-to-hd or other more permanent media, losing everything including BOINC on re-boot is normal.

As for "client detached", this normally happens due to users either duplicating their client-installations to multiple computers or across multiple OS-installations on same computer, or it's due to users restoring an older client-installation from backup.

---

"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."

I hope to get an answer from someone in the know what could explain what I have witnessed over the past 24+hrs

the problem is WUs crunched but then seemingly disappear, no credit and I do not see them in pending and began after upgrading a persistent live linux distribution--more space. I began running boinc/seti on the new drive yesterday evening and realized early this morning the darned distribution inexplicably not persistent, i.e., I booted and discoveredno boinc/seti, nothing and immediately went back to the old distro. disaster.

of course, then the problem begins with which WUs crunched on the non-persistent distro. I am fairly certain I aborted the ones crunched and it was not that many after returning to the small but persistent distro.

question. could this absurdity throw a monkey in the credit approval process such that now the WUs are not recognized when submitted by this client?

NOTE: I am certain I am way past possible dups so this not about a bunch of dups re-crunched.

any thoughts and or explanations, and no laughing, would be appreciated. and no, I did not ensure the miserable distro persistent before booting.

just so you know, I am experimenting with very lite liveusb solutions and different thumbdrives, to explain what I mean by returning to previous distro, smaller usb.

thanks.

The server tracks which client was sent the task. If a different client completes the task, it is rejected.

If a client completes the same task more than once, the duplicates are rejected.

Please remember that the people answering are a bunch of volunteers, and there is not someone available 24/7.

---

BOINC WIKI