restarted the machine and then this

12/27/2014 10:51:37 PM | SETI@home | Didn't resend lost task 06my12ai.21138.8349.438086664203.12.62_0 (expired)

how can they expire in 3 minutes ?

bummer

---

I came down with a bad case of i don't give a crap

Reminds me of ghost work units we used to get a lot of back in the old days.

---

[/quote]

Old James

restarted the machine and then this

12/27/2014 10:51:37 PM | SETI@home | Didn't resend lost task 06my12ai.21138.8349.438086664203.12.62_0 (expired)

how can they expire in 3 minutes ?

bummer

If the resend lost work feature cannot resend a task, it kills it by marking it as past deadline (so another replication will be created and go to another host ASAP). That's the expired part. Figuring out why those 117 tasks were lost and were not resent is more difficult, you haven't given enough details.

                                                                   Joe

restarted the machine and then this

12/27/2014 10:51:37 PM | SETI@home | Didn't resend lost task 06my12ai.21138.8349.438086664203.12.62_0 (expired)

how can they expire in 3 minutes ?

bummer

If the resend lost work feature cannot resend a task, it kills it by marking it as past deadline (so another replication will be created and go to another host ASAP). That's the expired part. Figuring out why those 117 tasks were lost and were not resent is more difficult, you haven't given enough details.

                                                                   Joe

Why the tasks weren't resent was because none of the app_versions have any 'Number of tasks completed', So no APR yet,
until they have their 11 validations tasks tend to get expired rather than resent,

Why they got lost in the first place is the real question.

Claggy

Well i have taken that machine offline until i can figure out what is causing the issue with it

sry about the busted WU's

---

I came down with a bad case of i don't give a crap

Well i have taken that machine offline until i can figure out what is causing the issue with it

sry about the busted WU's

What does the logs say? Did it have some failed scheduler contacts at the time those Wu's were attempted to be sent?

Claggy

Well it seems nothing was written in the logs so i assume there is something wrong with the boinc install

but looking at my windows machine right now it seems it cannot download any WU's either , seems the download servers need their pipes roto rootered

judging by that all my cuda WU's are processed and uploaded and the regular CPU WU's are getting low it couldn't make a connection for quiet a while

there is a gazillion WU's waiting for download

---

I came down with a bad case of i don't give a crap

Well it seems nothing was written in the logs so i assume there is something wrong with the boinc install

There's unlikely to be anything wrong with the boinc install.

Please post the Event Log from about 28 Dec 2014, 2:30:00 UTC, to 5:00:00 UTC,
If it doesn't show in the Event Log now, you should be able to find that time peroid in the stdoutdae.txt or stdoutdae.old files in the /var/lib/boinc-client directory (assuming that is the Data directory)

Claggy

already nuked the machine from orbit (only way to make sure...) and re installed

will be going up in about an hour then i will see what happens

---

I came down with a bad case of i don't give a crap