Page 1 of 1

171:67:108.22 Results successfully sent Jan 30 not appearing

Posted: Wed Feb 03, 2010 9:16 am
by MonsterSound
Hello,
Is there any chance of checking a bigadv WU that was completed on Jan 30 where it appears that the results were successfully sent, but did not show up for myself (MonsterSound) and the team (54196).

- Connecting to assignment server
- Successful: assigned to (171:67:108.22).
+ News From Folding@Home: Welcome to Folding@Home
Loaded queue successfully.
Project: 2681 (Run 15, Clone 11, Gen 34)

+ Attempting to send results [January 30 19:47:35 UTC]
+ Results successfully sent
Thank you for your contribution to Folding@Home
+ Number of Units Completed: 4

I've been GPU and SMP folder for a while but just started with bigadv.
So far I've lost some WU time with the msg "CoreStaus = FF (255)"
Once at 22% and once at 93%. :?
Any advice is appreciated. Thank you.
P.s. I'm looking into the back up script now (better late than never).

Re: 171:67:108.22 Results successfully sent Jan 30 not appearing

Posted: Wed Feb 03, 2010 9:43 am
by toTOW
Last BigWU I see was credited on 2010-01-30 16:17:14 for 0 points ... WU is project 2681 Run 15 Clone 11 Gen 34.

If you have a more complete log, it would be useful to see what happened before and after the send.

Re: 171:67:108.22 Results successfully sent Jan 30 not appearing

Posted: Wed Feb 03, 2010 8:08 pm
by bruce
How many clients do you have that run the bigadv WU?

Re: 171:67:108.22 Results successfully sent Jan 30 not appearing

Posted: Sun Feb 07, 2010 12:16 pm
by MonsterSound
Sorry for the late reply (life eh?).
I am only running the one client.
Unfortunately, I deleted my 6.24 client (along with the logs) as I updated to 6.29.
The Jan 30 bigadv WU that did complete (which was later in the evening than 2010-01-30 16:17:14, I thought) was having connection issues and the "Results successfully sent Jan 30" were on a 5th attempt after 4 failures to connect.
Oh well, I hope the result was actually received at least.
btw, 6.29 seems to be working well.
& Thanks very much for your response.