Page 1 of 1
169.229.194.42
Posted: Mon Mar 10, 2014 1:46 am
by absolutefunk
Howdy!
Long time lurker, first time poster
169.229.194.42 has been not accepting for almost a week now, and I have a couple boxes with completed WUs in the queue waiting to be sent out. Any word on when this server will be accepting?
Thanks!
Re: 169.229.194.42
Posted: Mon Mar 10, 2014 9:32 am
by bollix47
Welcome to the folding@home support forum absolutefunk and thank you for your report.
PG has been notified of the situation and hopefully we will have more information later today.
Re: 169.229.194.42
Posted: Mon Mar 10, 2014 4:26 pm
by gbowman
Thank you for pointing this out, I'm looking into it now.
Re: 169.229.194.42
Posted: Thu Mar 13, 2014 8:09 pm
by mikepcap
It's been 3 days since the last post. I see the IP is reporting as up now, but I still have a WU (10146) that is not getting through and is close to expiration. Any status report? Thanks
Re: 169.229.194.42
Posted: Fri Mar 14, 2014 3:13 am
by gbowman
Sorry for the delay. A hard drive failure has wiped out the machine and we're trying to restore it. I suspect we won't have it solved before your WU times out, unfortunately.
Re: 169.229.194.42
Posted: Fri Mar 14, 2014 10:06 pm
by mikepcap
Unfortunately, you were right...
12:13:02:WU01:FS00:Server responded UNKNOWN_ENUM (1010792557)
12:13:02:WARNING:WU01:FS00:Failed to send results, will try again later
16:14:14:WARNING:WU01:FS00:Past final deadline 2014-03-14T16:14:13Z, dumping
Thanks for the update
Re: 169.229.194.42
Posted: Sat Mar 15, 2014 5:15 am
by gbowman
Sorry for the inconvenience:(
Re: 169.229.194.42
Posted: Sat Mar 15, 2014 7:14 am
by Jesse_V
gbowman wrote:Sorry for the delay. A hard drive failure has wiped out the machine and we're trying to restore it. I suspect we won't have it solved before your WU times out, unfortunately.
Even with RAID? I'm sorry to hear that. Those kinds of issues can be disastrous.
Good luck to you with this.
Re: 169.229.194.42
Posted: Mon Mar 17, 2014 10:01 pm
by gbowman
Thanks, yes, something went wrong enough that we're having to rebuild the array from scratch, sigh.