Search found 14 matches
- Fri Jun 25, 2021 9:45 pm
- Forum: V7.6.x Public Release Windows/Linux/MacOS X
- Topic: No GPU WU, shortage or other cause?
- Replies: 14
- Views: 18464
Re: No GPU WU, shortage or other cause?
Thanks for the detailed answer. Still, it would be good to report a problem right away. Then everyone affected knows that it has been recognized and that work is being carried out to rectify it, instead of looking for errors elsewhere or even giving up.
- Fri Jun 25, 2021 12:05 pm
- Forum: V7.6.x Public Release Windows/Linux/MacOS X
- Topic: No GPU WU, shortage or other cause?
- Replies: 14
- Views: 18464
Re: No GPU WU, shortage or other cause?
It's frustrating. Tens thousands of people worldwide are ready to make their computers and power resources available in the fight against diseases, but the FAH support team does not communicate with us if there are problems with the provision of work packages. The FAH support team should report prob...
- Thu Apr 09, 2020 6:20 pm
- Forum: Issues with a specific server
- Topic: Can't upload to 140.163.4.231 again
- Replies: 102
- Views: 30260
Re: Can't upload to 140.163.4.231 again
Yes,thanks.Upload was possible now.
- Thu Apr 09, 2020 3:05 pm
- Forum: Issues with a specific server
- Topic: Can't upload to 140.163.4.231 again
- Replies: 102
- Views: 30260
Re: Can't upload to 140.163.4.231 again
A look at https://apps.foldingathome.org/serverstats shows in the line "IP 140.163.4.231" in the columns "Warnings = 1" and "Has CS = No". If you move the cursor over it, "Collection server not connected" and "Failed: fah4.eastus.cloudapp.azure.com" ...
- Sun Mar 29, 2020 5:05 pm
- Forum: Issues with a specific server
- Topic: 40.114.52.201 & 13.90.152.57 Killing QRB
- Replies: 13
- Views: 3719
Re: 40.114.52.201 & 13.90.152.57 Killing QRB
Everything you write about the server overload is now known. The really positive cause of these problems is known. I am also patient and move on. But that's not the issue here. The point is that FAH should not reduce the points previously achieved when calculating the packets because the FAH server...
- Sun Mar 29, 2020 4:58 pm
- Forum: Issues with a specific server
- Topic: 40.114.52.201 & 13.90.152.57 Killing QRB
- Replies: 13
- Views: 3719
Re: 40.114.52.201 & 13.90.152.57 Killing QRB
The point is that FAH should not reduce the points previously achieved when calculating the packets because the FAH servers either do not establish a connection or accept the data only very slowly. The packages are not large, only between 20 and 50 MiB. Each of us has enough fast internet connectio...
- Wed Mar 25, 2020 5:22 pm
- Forum: Issues with a specific server
- Topic: 40.114.52.201 & 13.90.152.57 Killing QRB
- Replies: 13
- Views: 3719
Re: 40.114.52.201 & 13.90.152.57 Killing QRB
The servers are under very high load and have been for a couple of weeks now. As pointed out in the sticky threads viewtopic.php?f=61&t=33193 and viewtopic.php?f=61&t=32424, there has been about a 15x increase in the number of F@h users over the past month or so. The servers went from distr...
- Wed Mar 25, 2020 2:06 pm
- Forum: Issues with a specific server
- Topic: 40.114.52.201 & 13.90.152.57 Killing QRB
- Replies: 13
- Views: 3719
Re: 40.114.52.201 & 13.90.152.57 Killing QRB
It is true that it is more important that the results arrive at all than that the points previously reached do not shrink because the FAH servers cannot receive the data. I am also aware of this. But that doesn't mean that the points system shouldn't be adapted to the new circumstances anyway. FAH h...
- Wed Mar 25, 2020 11:50 am
- Forum: Issues with a specific server
- Topic: 40.114.52.201 & 13.90.152.57 Killing QRB
- Replies: 13
- Views: 3719
Re: 40.114.52.201 & 13.90.152.57 Killing QRB
It is demotivating to see how the previously score points melt away, while the FAH servers do not allow a connection and the upload then drips down over a long period of time. :( It's not fair. The cause are not the donors, so FAH should change that. Each donor has sufficient upload capacity to uplo...
- Sat Mar 21, 2020 8:07 pm
- Forum: GPU Projects and FahCores
- Topic: Project unspecified
- Replies: 2
- Views: 1197
Re: Project unspecified
Thanks for your answer. I am aware, that the researchers have a lot to do and we all, who support them with our PCs, hope that there will be a success soon.
- Sat Mar 21, 2020 9:06 am
- Forum: GPU Projects and FahCores
- Topic: Project unspecified
- Replies: 2
- Views: 1197
Project unspecified
for many projects, no description is displayed via the web control. If you select the project via https://apps.foldingathome.org/psummary, you only get the message "Project unspecified". This is especially the case for those GPU-OPENMM-22 projects that are managed by voelz, totowfr and jos...
- Thu Mar 19, 2020 10:44 am
- Forum: CPU Projects - released FAHCores _a7 & _a8 (a4 retired)
- Topic: Server did not like results, dumping
- Replies: 7
- Views: 2530
Re: Server did not like results, dumping
The same problem here. WU started at 05:16:16 and ended at 09:57:34 = 04:40:48 GPU time wasted. *********************** Log Started 2020-03-18T19:01:35Z *********************** ******************************* Date: 2020-03-19 ******************************* 05:09:58:WU02:FS01:Connecting to 65.254.11...
- Mon Mar 16, 2020 12:53 pm
- Forum: Issues with a specific server
- Topic: Send Errors - 155.247.164.213 & .214
- Replies: 178
- Views: 51439
Re: Send Errors - 155.247.164.213 & .214
Well, down means DOWN. It's the middle of the night anywhere in th USA right now and volunteers should be sleeping ... preparing their immune system for another day of exposure to some random viruses. I don't know who will be reponsible for fiuring out why the servers are down and fixing it but it ...
- Mon Mar 16, 2020 9:05 am
- Forum: Issues with a specific server
- Topic: Send Errors - 155.247.164.213 & .214
- Replies: 178
- Views: 51439
Re: Send Errors - 155.247.164.213 & .214
But why is the Estimated Credit constantly reduced? It was previously worked hard and now it is shrinking minute by minute while the Collection Server 155.247.164.214 is not receiving any data. That's not OK.