Folding@Home News 2nd - 9th June June

Strange things happening here, my bigadv is 20% through a new unit but nothing is showing as being uploaded on EOC or stanford from earlier today.

The fah log shows the unit to have finished fine at 09:27 (which I think is an hour behind so 10:27), langouste shows at 9:30 -
Local: received 627 bytes, sent 24674573 bytes
Remote: received 24674573 bytes, sent 627 bytes

So where has it gone? Surely it would have shown up on stanfords stats by now at least? Don't know if I'm just being overly paranoid but considering going back to windows bigadv if this doesn't go through, it will have been the 2nd bigadv I've lost in 3 days :(
 
Strange things happening here, my bigadv is 20% through a new unit but nothing is showing as being uploaded on EOC or stanford from earlier today.

The fah log shows the unit to have finished fine at 09:27 (which I think is an hour behind so 10:27), langouste shows at 9:30 -
Local: received 627 bytes, sent 24674573 bytes
Remote: received 24674573 bytes, sent 627 bytes

So where has it gone? Surely it would have shown up on stanfords stats by now at least? Don't know if I'm just being overly paranoid but considering going back to windows bigadv if this doesn't go through, it will have been the 2nd bigadv I've lost in 3 days :(

Does the log say: "Thank you for your contribution to Folding@Home" or "Server reports problem with unit"? if it's the latter then that would be your answer :(
 
Neither, just Sending work to server, I think that's to do with langouste though, I've restarted the client and told it not to use a proxy to see if it is the langouste that is causing the problem for the next one. Also double checked my username and team number as well.
 
yep :(, fingers crossed this one goes through ok. I just had a look in the fah client files, there is a pretty big .dat file which I'm guessing is the work, is there anyway to send this manually?
 
I've switched back to windows bigadv, I saw that on the vmware log the client had tried to send the previous work unit again but failed, now that the langouste proxy was out of the question I thought it must be something to do with the VMware network adapter.

So I foolishly switched it to NAT, and when I restarted the machine everything was gone :( 3 units lost now and I don't have time to faff around with it any more, so back to windows for me.
 
It's also my home file / media server, I was running ubuntu natively for a while and it did work but it took ages to set things up, driver issues, my lack of linux knowledge etc.

I was pretty much there in the end, but I still couldn't get some key things to work properly like backups of the server and sound over HDMI. So when an opportunity came up to swith to Server 2008 I went for that.

I'll give the vmware another go at some point but just don't have the time at the moment.
 
Back
Top Bottom