Folding Forum

It's been over a week with nothing but crickets, tumbleweed, and rejection.

Seven lonely finished work units with no place to go.

I downloaded them before the server went down. And yes, two of them have now expired, but had not at the time I first attempted to upload them. This one will expire in twenty-two hours and just now failed to upload - --- Opening Log file [June 27 12:20:00 UTC] # Windows GPU Console Edition #########...

Thank you for returning 171.67.108.11 to full service. However, I am still unable to upload finished work units to 171.67.108.21. The server status is showing a zero for all data fields except CPU load.

Thanks for alerting Stanford of the issue. The .11 server has been in reject mode and all attempts to communicate with .21 show failure in the log files, although the assignment server is still routing to it. I confirm the time frame as starting no later than noon PDT, 17 June.

Good to know it's a server issue and not the core_11 EoL. I thought it was probably the server when my G92 wasn't even able to get a core_15 work unit. Is anyone getting core_15 WUs?

I am also seeing similar failures from this server. Two on the 13th and then another this morning. Upload times are normal, but followed by a fail to send message. Further attempts are rejected by the server. This is not the first time this server has had similar issues. Logfiles to follow. ---- edi...

The next to the last option in the main configuration screen is a file size option. By default the maximum download or upload file size should be no larger than 10MBs. I am routinely assigned A3 work units with a 20MB upload file even if I set the option to small which is no file 5MBs or larger.

Yesterday I eventually received a 6023 from 171.64.65.54 which I know from previous experience violates my configuration settings. It processed for a minute or two and then hard locked the system. Deleted defective WU. Later I received a 6025 from 171.64.65.54 which I know from previous experience v...

For a period of ten minutes or so I saw my client get assigned to the 130.237.232.140 server and then fail repeatedly to connect. Although maybe it's just as well since every work unit I have processed from the 130.237.232.140 server has violated my configuration settings. And sadly, still no assign...

Still failing here as well.

--- edit ---

Server status is showing .54 iced (blue activity blocks) with all quantities zeroed out.

Created a new instance of the client. It failed the same.

Yep, 171.67.108.21 seems to have run a muck and is failing to send or receive any work units. It also appears to be preventing the assignment server from sending work units from any other GPU server! This issue is rapidly approaching the 24 hour mark. Did all the staff have that much fun on Valentin...

it will upload immediately I wish I could forget my dial-up connection as well. My clients always finish and then ask me to connect. On a very positive note the use of two clients does allow me to keep the system crunching a WU while the finished WU uploads. With an average connection speed of abou...

Oops, another assumption bites the dust. Yeah, when I put a nearly finished WU on hold I use a procedure similar to sneaker netting. Work folder, queue.dat, and unitinfo.txt into a hold folder. I still have no problems with any other server than this "new and improved" system. However, I a...

What do you mean by "the duplicate time frame"? Projects 3860-3864 have a preferred deadline of either 6 or 8 days and a final deadline of 60 days. Please let us know the PRCG of each WU with a problem. Also, when was each WUs downloaded and when did each one start getting the error messa...