Failed to connect to 171.64.65.104:80
Moderators: Site Moderators, FAHC Science Team
Re: Failed to connect to 171.64.65.104:80
I don't want to my delete WU. I just don't want it to disappear when it expires because it never got collected due to a server error.
Re: Failed to connect to 171.64.65.104:80
It's unfortunate that there's going to be a lot more computing power lost over the next couple of days if this server's issue isn't resolved. The last of the WUs assigned before the server went down on the 17th will be expiring on or before Wednesday while they sit completed and waiting to be turned in.
The WUs are important to me and I hope they're important to the folks receiving them, but it sends an odd message to have a server out of space for a full week.
The WUs are important to me and I hope they're important to the folks receiving them, but it sends an odd message to have a server out of space for a full week.
-
- Posts: 2040
- Joined: Sat Dec 01, 2012 3:43 pm
- Hardware configuration: Folding@Home Client 7.6.13 (1 GPU slots)
Windows 7 64bit
Intel Core i5 2500k@4Ghz
Nvidia gtx 1080ti driver 441
Re: Failed to connect to 171.64.65.104:80
jadeshi says: Sorry for the delay. p92xx should be accepting work requests again.
viewtopic.php?f=24&t=28976
viewtopic.php?f=24&t=28976
-
- Site Admin
- Posts: 7927
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2 - Location: W. MA
Re: Failed to connect to 171.64.65.104:80
Looking at the Project Summary page, this appears to involve a move to a different server. So for the moment there are two IP addresses listed for each project. I recall this causing problems for some monitoring tools.
WS 171.64.65.104 is still shown as in Reject status.
WS 171.64.65.104 is still shown as in Reject status.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Re: Failed to connect to 171.64.65.104:80
Yes. jadeshi's 'fix' seams to be that the server only sends out new work maybe, caus I'm stll unable to send in my old result.
Re: Failed to connect to 171.64.65.104:80
The environment variable %appdata% is set to C:\Users\<logon_name>\AppData\Roaming\ so that's the same as what foldy said, provided you're logged on as bsbs_texas wrote:^ hey thanks... But, but I had to search around and found it was actually in C:\Users\bs\AppData\Roaming\FAHClient\work.
foldy wrote: %appdata%\FAHClient\work
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
-
- Posts: 177
- Joined: Tue Aug 26, 2014 9:48 pm
- Hardware configuration: 10 SMP folding slots on Intel Phi "Knights Landing" system, configured as 24 CPUs/slot
9 AMD GPU folding slots
31 Nvidia GPU folding slots
50 total folding slots
Average PPD/slot = 459,500 - Location: Dallas, TX
Re: Failed to connect to 171.64.65.104:80
I'm having the same problem as Simplex0: My rigs are correctly downloading, folding and uploading new p92xx assignments. However, the old p92xx work units completed before the server mishap still will not upload. They are stuck getting the same "PLEASE_WAIT (464)" error message on failed upload attempts. Tried pausing the client, unpausing to restart upload, but to no avail. Also tried shutting down and restarting the client, which also has no impact. Is there any fix, or is it time to dump these work units?
Hardware config viewtopic.php?f=66&t=17997&p=277235#p277235
-
- Site Admin
- Posts: 7927
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2 - Location: W. MA
Re: Failed to connect to 171.64.65.104:80
As the last WU's download from the 171.64.65.104 WS are approaching the final deadline of 10 days, they should be dumped automatically. As I posted, the projects were moved to a new WS and the old WU's will not upload to the new WS. Their destination WS and CS would have been set when the WU was downloaded. I do not have further information, but the need to move the projects from this WS would imply to me that there was more wrong than just running out of space.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Re: Failed to connect to 171.64.65.104:80
While this looks like what's going to happen, the problem is more a lack of communication about the server status. Not a big deal, but my machines have spent about 30 GB of bandwidth with the client trying to upload these WUs to the listed CS since the WS rejected them. Just a little frustrating to know that I could have manually dumped them if the server was never coming back up on the listed IP addresses.Joe_H wrote:they should be dumped automatically
Re: Failed to connect to 171.64.65.104:80
Well, my last WU from this server was dumped. Sad.
Re: Failed to connect to 171.64.65.104:80
This. I wish someone would have given us some kind of ongoing status update to let us know what was going on. That's where most of my frustration is from.MahlRem wrote:While this looks like what's going to happen, the problem is more a lack of communication about the server status.