171.64.122.70 - Missing credits
Moderators: Site Moderators, FAHC Science Team
Re: 171.64.122.70 - Missing credits
Imran, it would appear by now that the server has lost the stats, and fixing the cause won't magically result in the server assigning past due credits. Can you therefore manually update credits for those folders who are able to produce valid logs as evidence (as I have done in an earlier post)? I guess you run the risk of someone faking a log, however.
(I don't envy you having to sort this mess out - best of luck).
(I don't envy you having to sort this mess out - best of luck).
Re: 171.64.122.70 - Missing credits
I can think of only one time when a server actually lost the stats -- when the disk filled up and the logs could not be stored.
There have been quite a few times when stats failed to automatically make their way to the stats system. When that happens, they're temporarily lost, but they can be recovered from the server logs. The Pande Group will not base the re-credit on logs that you post (faked or not) but rather on information that they already have. The logs that you post MIGHT be used to establish the duration of the problem, so that they have a start time and a finish time to reprocess, but they don't need a large quantity of logs to establish those times. By shutting down new assignments, they've established a finish time.
Recrediting is never a rapid process. Several different people are involved and the data is rechecked in a number of ways. I wouldn't expect any visible progress for many days -- sometimes it takes a number of weeks.
There have been quite a few times when stats failed to automatically make their way to the stats system. When that happens, they're temporarily lost, but they can be recovered from the server logs. The Pande Group will not base the re-credit on logs that you post (faked or not) but rather on information that they already have. The logs that you post MIGHT be used to establish the duration of the problem, so that they have a start time and a finish time to reprocess, but they don't need a large quantity of logs to establish those times. By shutting down new assignments, they've established a finish time.
Recrediting is never a rapid process. Several different people are involved and the data is rechecked in a number of ways. I wouldn't expect any visible progress for many days -- sometimes it takes a number of weeks.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: 171.64.122.70 - Missing credits
Any progress on this?
Re: 171.64.122.70 - Missing credits
Sorry, not yet. We have a paper deadline coming up shortly and that's been taking up all of my time.
I know, having to actually write about the science is just terrible
I know, having to actually write about the science is just terrible
Re: 171.64.122.70 - Missing credits
Were these WUs downloaded and uploaded from the same client and with the same User Name/Team No or were there some changes made during the run? Please post al revelant deatails from FAHlog.txt including the assignment/download/start, not just the finish/upload. Also include enough of UserID that it can be recognized from a list of your clients.bollix47 wrote:Here are two more (both from .70) that were processed today but no sign of points being credited:
Code: Select all
[18:58:31] Project: 5907 (Run 3, Clone 27, Gen 5) [18:58:32] + Results successfully sent [18:58:32] Thank you for your contribution to Folding@Home.
Code: Select all
[18:59:26] Project: 5907 (Run 9, Clone 36, Gen 5) [18:59:27] + Results successfully sent [18:59:27] Thank you for your contribution to Folding@Home.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: 171.64.122.70 - Missing credits
@Bruce
Unfortunately the -Prev log doesn't go that far back so I cannot find some of the info that you have requested and I don't remember which client(s) of my 5 Nvidia setups processed them. I can tell you that the user Name/Team was bollix47/39340 and there were no changes made during the run.
Sorry that I didn't include more info at the time and I will save the logs in the future if something similar happens again. I haven't received any of the P59XX WUs since that date(Mar 23).
I'm sure that you're attempting to find out what caused the missing credits but from my standpoint the issue is closed. I do appreciate your attempts but please don't spend a lot of time on my case.
Thanks
Unfortunately the -Prev log doesn't go that far back so I cannot find some of the info that you have requested and I don't remember which client(s) of my 5 Nvidia setups processed them. I can tell you that the user Name/Team was bollix47/39340 and there were no changes made during the run.
Sorry that I didn't include more info at the time and I will save the logs in the future if something similar happens again. I haven't received any of the P59XX WUs since that date(Mar 23).
I'm sure that you're attempting to find out what caused the missing credits but from my standpoint the issue is closed. I do appreciate your attempts but please don't spend a lot of time on my case.
Thanks
Re: 171.64.122.70 - Missing credits
There's some question about what the Pande Group will be able to find or not find. That server had a strange disk problem on the RAID and there are some inconsistencies in the stats reports. The hardware is being replaced, and then they'll make an effort to see what else can be recovered/regenerated.
bollix47 considers his part of this issue closed. To others who may be reading this, please don't flood this topic with additional information unless ihaque asks for it.
bollix47 considers his part of this issue closed. To others who may be reading this, please don't flood this topic with additional information unless ihaque asks for it.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: 171.64.122.70 - Missing credits
Received some unexpected points today!
Thanks
Thanks
Re: 171.64.122.70 - Missing credits
We found the error in the server logs, and have manually recredited all WUs associated with that error. I checked - every WU that was mentioned in this thread was in the recredit file (along with many others). The root problem can be traced back to a failed disk drive on the server - because it was unable to write out the returned data files, it decided not to write credit lines either. Thanks for bringing this to our attention, and thanks for your patience; it's been a really busy month for me, and I got to it when I finally had some time.
I think it's safe to say, case closed?
I think it's safe to say, case closed?
-
- Posts: 266
- Joined: Sun Dec 02, 2007 6:08 pm
- Location: Central New York
- Contact:
Re: 171.64.122.70 - Missing credits
ihaque, thank you for taking the time to do the manual crediting, and also for the note of explanation.
-
- Posts: 70
- Joined: Thu Jul 31, 2008 3:26 pm
- Hardware configuration: PC1//C2Q-Q9450,GA-X48-DS5-NinjaMini,GTX285,2x160GB Western Sata2,2x1GB Geil800,Tagan 800W;XP Pro SP3-32Bit;
PC2//C2Q-Q2600k.GB-P67UD4-Freezer 7Pro,GTX285Leadtek,260 GB Western Sata2,4x2GB GeilPC3,OCZ600W;Win7-64Bit;Siemens 22" - Location: Deutschland
Re: 171.64.122.70 - Missing credits
I sign and I thankihaque, thank you for taking the time to do the manual crediting, and also for the note of explanation
PC1//C2Q-Q9450,GA-X48-DS5-,2xGTX285,2x160GB Western Sata2,2x1GB Geil800,Tagan 800W;XP Pro SP3-32Bit
PC2//C2Q-Q2600k.GB-P67UD4-Freezer 7Pro,GTX285Leadtek,260 GB WeSata2,4x2GB GeilPC3,OCZ600W;Win7-64Bit;Siemens 22"stern
PC2//C2Q-Q2600k.GB-P67UD4-Freezer 7Pro,GTX285Leadtek,260 GB WeSata2,4x2GB GeilPC3,OCZ600W;Win7-64Bit;Siemens 22"stern