After some days of no instances;
PRCG 16448 (0, 16, 178)
Search found 15 matches
- Mon Aug 03, 2020 6:46 am
- Forum: GPU Projects and FahCores
- Topic: Core won't start, no error displayed
- Replies: 22
- Views: 14744
- Sun Jul 26, 2020 6:19 pm
- Forum: GPU Projects and FahCores
- Topic: Core won't start, no error displayed
- Replies: 22
- Views: 14744
Re: Core won't start, no error displayed
Edited a few PRGCs to the message above
- Sun Jul 19, 2020 3:46 pm
- Forum: GPU Projects and FahCores
- Topic: Core won't start, no error displayed
- Replies: 22
- Views: 14744
Re: Core won't start, no error displayed
Here’s a few latest ones: PRCG 17200 (682, 3, 63) -- (inactive, but 17204 is starting early testing) PRCG 11761 (0, 10454, 140) -- 128.252.203.10 PRCG 11759 (0, 12396, 99) -- 128.252.203.10 EDIT July 22nd, Today I got: PRCG 11760 (0, 743, 110) EDIT July 25th: PRCG 11760 (0, 13115, 32) EDIT July 26th...
- Tue Jul 14, 2020 7:55 am
- Forum: GPU Projects and FahCores
- Topic: Core won't start, no error displayed
- Replies: 22
- Views: 14744
Re: Core won't start, no error displayed
Resurrecting this thread from couple of weeks back to give a status update: Out of the 6 clients I have folding, this ”stuck at 0,00%” still comes up maybe once every two days, so the problem is clearly still there. Haven’t really had time to browse/collect any logs. I did browse once just enough to...
- Thu Jul 02, 2020 7:22 am
- Forum: GPU Projects and FahCores
- Topic: Core won't start, no error displayed
- Replies: 22
- Views: 14744
Re: Core won't start, no error displayed
In addition to the log from a Z2 machine above, found the setPosition-error from the recent logs of three pretty much identical HP Z240 workstations (i7-7700K & Quadro P4000). Seems to be mostly happening with 144XX units. You consider the setPosition error in one WU would be causing a following...
- Wed Jul 01, 2020 7:43 pm
- Forum: GPU Projects and FahCores
- Topic: Core won't start, no error displayed
- Replies: 22
- Views: 14744
Re: Core won't start, no error displayed
Unfortunately just had the ”stuck at 0,00%” happen on the HP Z2 (i9 & RTX 4000) client with core version 0.0.11 as well, again at ”state.xml”, log below. If it might have something to do with the problem, this PC has been running headless with RDP used to log a user in. However, before core vers...
- Tue Jun 30, 2020 10:32 am
- Forum: GPU Projects and FahCores
- Topic: Core won't start, no error displayed
- Replies: 22
- Views: 14744
Re: Core won't start, no error displayed
Great, thanks for the info bruce. Looking forward to getting the 0.0.11 at some point then! Yes, thought so too that the i7 computers (with P4000) do not have an iGPU, but the i9-9900Ks on the other computers (with RTX 4000) do. Someone just speculated that an iGPU might have something to do with th...
- Mon Jun 29, 2020 9:33 pm
- Forum: GPU Projects and FahCores
- Topic: Core won't start, no error displayed
- Replies: 22
- Views: 14744
Re: Core won't start, no error displayed
Today this issue came up with one of the HP Z240 / Q P4000 PCs. These machines don't have any integrated GPUs as far as I can tell. Here's the log for this case: *********************** Log Started 2020-06-27T12:28:28Z *********************** 12:28:28:************************* Folding@home Client **...
- Sun Jun 28, 2020 7:16 pm
- Forum: GPU Projects and FahCores
- Topic: Core won't start, no error displayed
- Replies: 22
- Views: 14744
Re: Core won't start, no error displayed
I can confirm this same issue on HP Z240 and Z2 workstations that have Quadro P4000 and Quadro RTX 4000 GPUs respectively. I’ve noticed this now on four different PCs on maybe 5-6 occasions. It started sometime within a week or so, until then no hiccups whatsoever. In my case the cure has been: Pres...
- Tue Apr 28, 2020 12:35 pm
- Forum: Issues with a specific server
- Topic: 13.82.98.119 not taking my Wu
- Replies: 77
- Views: 24623
Re: Failed to connect: 3.133.76.19 and 3.21.157.11
My logs on several clients are getting a bit full of this: 12:10:13:WU02:FS00:Sending unit results: id:02 state:SEND error:NO_ERROR project:16435 run:277 clone:0 gen:7 core:0x22 unit:0x0000000903854c135e9a4efb5a1a5bea 12:10:13:WU02:FS00:Uploading 141.54MiB to 3.133.76.19 12:10:13:WU02:FS00:Connectin...
- Sun Apr 26, 2020 7:12 am
- Forum: Issues with a specific server
- Topic: 13.82.98.119 not taking my Wu
- Replies: 77
- Views: 24623
Re: Failed to connect: 3.133.76.19 and 3.21.157.11
Confirming sending errors here as well. Some half a dozen finished WUs on different clients retrying and failing to connect or failing at early percentage when started to upload.
- Tue Apr 07, 2020 4:43 pm
- Forum: Issues with a specific server
- Topic: Can't upload to 140.163.4.241
- Replies: 10
- Views: 6368
Re: Can't upload to 140.163.4.241
Over 40 tries in the retry counter so far, still getting the PLEASE_WAIT error
- Mon Apr 06, 2020 5:35 am
- Forum: Issues with a specific server
- Topic: Can't upload to 140.163.4.241
- Replies: 10
- Views: 6368
Re: Can't upload to 140.163.4.241
PLEASE_WAIT (464) still happening here. I guess they are still out of disk space as it shows only 571.69MiB in serverstats.
- Sun Apr 05, 2020 10:56 am
- Forum: Issues with a specific server
- Topic: Can't upload to 140.163.4.241
- Replies: 10
- Views: 6368
Re: Can't upload to 140.163.4.241
I have been getting by log full of PLEASE_WAIT (464): 10:39:54:WU02:FS00:Sending unit results: id:02 state:SEND error:NO_ERROR project:11745 run:0 clone:9705 gen:31 core:0x22 unit:0x0000002f8ca304f15e6bc3742045b884 10:39:54:WU02:FS00:Uploading 14.66MiB to 140.163.4.241 10:39:54:WU02:FS00:Connecting ...
- Wed Mar 25, 2020 2:02 pm
- Forum: Issues with a specific server
- Topic: Send Errors - 155.247.164.213 & .214
- Replies: 178
- Views: 64808
Re: Send Errors - 155.247.164.213 & .214
Just came here to confirm some issues with these servers ongoing at the moment. They have persisted for at least 24 hours now: 13:53:30:WU00:FS00:Uploading 55.24MiB to 155.247.164.213 13:53:30:WU00:FS00:Connecting to 155.247.164.213:8080 13:53:51:WARNING:WU00:FS00:WorkServer connection failed on por...