Page 1 of 1
No upload of finished projects to 128.252.203.4
Posted: Tue Jul 10, 2018 4:23 pm
by mattifolder
Hello,
I've three finished GPU projects, that don't upload to 128.252.203.4. Connection to 128.252.203.4:8080 and 128.252.203.4:80 in Web browser and all internet connectivity from client pc is o.k. The server going on distributing new project to my client. What is wrong there ? If the projects not uploading, I can also stop the client.
Re: No upload of finished projects to 128.252.203.4
Posted: Tue Jul 10, 2018 4:55 pm
by bruce
You didn't specify what project(s) are queued up. The server seems to be operating normally except for the fact that a Collection Server isn't enabled.
Do you happen to have a configuration that specifies BETA? If so, remove that option. If you'r problem is with a beta project, please report it in the beta forum where there's already a discussion going on.
Yes, you can stop the client using FAHControl ... or stop individual slots if you have more than one. Use the (global) PAUSE button or right-click on the Folding_Slot.
Re: No upload of finished projects to 128.252.203.4
Posted: Tue Jul 10, 2018 4:58 pm
by Joe_H
The server was down and has been restarted recently.
The only GPU projects I am aware of currently being served by that WS are in Beta. If you are getting them without the Beta flag being set please report that. Otherwise remove the flag if you are not part of the beta test team as Bruce suggests.
Re: No upload of finished projects to 128.252.203.4
Posted: Tue Jul 10, 2018 5:23 pm
by HayesK
p13816 is also on 128.252.2014. I have been catching p13816 on slots with no client-type flag set (blank). None currently in progress, but successfully returned a few with 6.44 MB uploads earlier today, about 7 hours ago.
Re: No upload of finished projects to 128.252.203.4
Posted: Tue Jul 10, 2018 5:33 pm
by mattifolder
Sorry, folded with beta flag. The outstanding GPU projects are P13815, that in beta state. So my request isn't right here.
Re: No upload of finished projects to 128.252.203.4
Posted: Tue Jul 10, 2018 7:25 pm
by bruce
There are risks associated with folding BETA projects. There are lots of 13815 projects queued up for that server -- and you have accepted that risk. Similarly, using your max-packet-size setting also subjects yourself to getting huge projects.
It's unfortunate if you have a 13816 project queued up, but there's no way for the server to sort out which results are *15 and which are *16 until they're received by the server. The invalid use of the BETA flag has made life difficult for not only yourself, but for others who are following the proper policies.