ChasingTheDream
|
|
May 15, 2014, 04:13:47 AM |
|
I've been running into a lot of hung work units. The work unit will hit the end and just sit there forever at 99.99% with 3 seconds remaining. I've done a bit of looking around and from what I've seen so far they say look for connection errors in the logs. So far I haven't seen any but I have these hung work units on several computers. I'm not sure how to resolve them but they certainly are hurting my production.
About the only thing I've been able to do so far is restart the computer without stopping the work unit first. That seems to knock it back to a previous checkpoint and then it will process about 50% of the time after it redoes the work again which can take hours.
If I stop the work unit prior to rebooting it just sits are 99.99% again. There must be an easier way to get around these. Has anyone else been experiencing this?
|
|
|
|
cameronpalte
|
|
May 15, 2014, 04:17:06 AM |
|
I've been running into a lot of hung work units. The work unit will hit the end and just sit there forever at 99.99% with 3 seconds remaining. I've done a bit of looking around and from what I've seen so far they say look for connection errors in the logs. So far I haven't seen any but I have these hung work units on several computers. I'm not sure how to resolve them but they certainly are hurting my production.
About the only thing I've been able to do so far is restart the computer without stopping the work unit first. That seems to knock it back to a previous checkpoint and then it will process about 50% of the time after it redoes the work again which can take hours.
If I stop the work unit prior to rebooting it just sits are 99.99% again. There must be an easier way to get around these. Has anyone else been experiencing this?
I too encountered the problem: here is the article i read that helped https://foldingforum.org/viewtopic.php?f=74&t=25341
|
|
|
|
FifthGhostbuster
|
|
May 15, 2014, 04:19:08 AM |
|
I've been running into a lot of hung work units. The work unit will hit the end and just sit there forever at 99.99% with 3 seconds remaining. I've done a bit of looking around and from what I've seen so far they say look for connection errors in the logs. So far I haven't seen any but I have these hung work units on several computers. I'm not sure how to resolve them but they certainly are hurting my production.
About the only thing I've been able to do so far is restart the computer without stopping the work unit first. That seems to knock it back to a previous checkpoint and then it will process about 50% of the time after it redoes the work again which can take hours.
If I stop the work unit prior to rebooting it just sits are 99.99% again. There must be an easier way to get around these. Has anyone else been experiencing this?
are you running multiple cards? I literally just ran into the same issue... still only solution i can find is restarting without stopping. still trying to find another sorry.
|
Go CureCoin!
|
|
|
ChasingTheDream
|
|
May 15, 2014, 04:21:09 AM |
|
I've been running into a lot of hung work units. The work unit will hit the end and just sit there forever at 99.99% with 3 seconds remaining. I've done a bit of looking around and from what I've seen so far they say look for connection errors in the logs. So far I haven't seen any but I have these hung work units on several computers. I'm not sure how to resolve them but they certainly are hurting my production.
About the only thing I've been able to do so far is restart the computer without stopping the work unit first. That seems to knock it back to a previous checkpoint and then it will process about 50% of the time after it redoes the work again which can take hours.
If I stop the work unit prior to rebooting it just sits are 99.99% again. There must be an easier way to get around these. Has anyone else been experiencing this?
I too encountered the problem: here is the article i read that helped https://foldingforum.org/viewtopic.php?f=74&t=25341Thanks for this and I also saw a reference to a similar problem on the previous page after I posted. My GPU's are factory overclocked so I suspect the OC'ing is the issue. I'll look into it!
|
|
|
|
ChasingTheDream
|
|
May 15, 2014, 04:22:39 AM |
|
I've been running into a lot of hung work units. The work unit will hit the end and just sit there forever at 99.99% with 3 seconds remaining. I've done a bit of looking around and from what I've seen so far they say look for connection errors in the logs. So far I haven't seen any but I have these hung work units on several computers. I'm not sure how to resolve them but they certainly are hurting my production.
About the only thing I've been able to do so far is restart the computer without stopping the work unit first. That seems to knock it back to a previous checkpoint and then it will process about 50% of the time after it redoes the work again which can take hours.
If I stop the work unit prior to rebooting it just sits are 99.99% again. There must be an easier way to get around these. Has anyone else been experiencing this?
are you running multiple cards? I literally just ran into the same issue... still only solution i can find is restarting without stopping. still trying to find another sorry. Yes each machine has two R9 290X TRI-X's in them and I am running into this on nearly every machine and I've got them in 7 machines so it seems to be consistent and I am running catalyst 14.4. I suspect it is an overclock issue and my cards are factory overclocked. I can tone them down and see what happens.
|
|
|
|
bardacuda
|
|
May 15, 2014, 04:25:19 AM Last edit: May 15, 2014, 05:40:59 AM by bardacuda |
|
I've been running into a lot of hung work units. The work unit will hit the end and just sit there forever at 99.99% with 3 seconds remaining. I've done a bit of looking around and from what I've seen so far they say look for connection errors in the logs. So far I haven't seen any but I have these hung work units on several computers. I'm not sure how to resolve them but they certainly are hurting my production.
About the only thing I've been able to do so far is restart the computer without stopping the work unit first. That seems to knock it back to a previous checkpoint and then it will process about 50% of the time after it redoes the work again which can take hours.
If I stop the work unit prior to rebooting it just sits are 99.99% again. There must be an easier way to get around these. Has anyone else been experiencing this?
After you complete a work unit you should see something like this in the log: 23:58:06:WU00:FS01:0x17:Completed 5000000 out of 5000000 steps (100%)
23:58:08:WU03:FS01:Connecting to 171.67.108.201:80 23:58:08:WU03:FS01:Assigned to work server 140.163.4.231 23:58:08:WU03:FS01:Requesting new work unit for slot 01: RUNNING gpu:0:Pitcairn [] from 140.163.4.231 23:58:08:WU03:FS01:Connecting to 140.163.4.231:8080 23:58:09:WU03:FS01:Downloading 4.84MiB 23:58:11:WU03:FS01:Download complete 23:58:11:WU03:FS01:Received Unit: id:03 state:DOWNLOAD error:NO_ERROR project:13001 run:534 clone:7 gen:14 core:0x17 unit:0x0000001d538b3db7532c93b7e185f3f6
23:58:26:WU00:FS01:0x17:Saving result file logfile_01.txt 23:58:27:WU00:FS01:0x17:Saving result file checkpointState.xml 23:58:29:WU00:FS01:0x17:Saving result file checkpt.crc 23:58:29:WU00:FS01:0x17:Saving result file log.txt 23:58:29:WU00:FS01:0x17:Saving result file positions.xtc 23:58:31:WU00:FS01:0x17:Folding@home Core Shutdown: FINISHED_UNIT 23:58:31:WU00:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64) 23:58:31:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:13001 run:162 clone:2 gen:11 core:0x17 unit:0x00000021538b3db753287d9b0d4519a3 23:58:31:WU00:FS01:Uploading 12.86MiB to 140.163.4.231 23:58:31:WU00:FS01:Connecting to 140.163.4.231:8080
23:58:31:WU03:FS01:Starting 23:58:31:WU03:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/admin/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/ATI/R600/Core_17.fah/FahCore_17.exe -dir 03 -suffix 01 -version 704 -lifeline 4596 -checkpoint 15 -gpu 0 -gpu-vendor ati 23:58:32:WU03:FS01:Started FahCore on PID 848 23:58:32:WU03:FS01:Core PID:2244 23:58:32:WU03:FS01:FahCore 0x17 started 23:58:32:WU03:FS01:0x17:*********************** Log Started 2014-05-14T23:58:32Z *********************** 23:58:32:WU03:FS01:0x17:Project: 13001 (Run 534, Clone 7, Gen 14) 23:58:32:WU03:FS01:0x17:Unit: 0x0000001d538b3db7532c93b7e185f3f6 23:58:32:WU03:FS01:0x17:CPU: 0x00000000000000000000000000000000 23:58:32:WU03:FS01:0x17:Machine: 1 23:58:32:WU03:FS01:0x17:Reading tar file state.xml 23:58:33:WU03:FS01:0x17:Reading tar file system.xml 23:58:33:WU03:FS01:0x17:Reading tar file integrator.xml 23:58:33:WU03:FS01:0x17:Reading tar file core.xml 23:58:33:WU03:FS01:0x17:Digital signatures verified 23:58:33:WU03:FS01:0x17:Folding@home GPU core17 23:58:33:WU03:FS01:0x17:Version 0.0.52
23:58:37:WU00:FS01:Upload 7.78% 23:58:43:WU00:FS01:Upload 17.01% 23:58:49:WU00:FS01:Upload 25.76% 23:58:55:WU00:FS01:Upload 34.51% 23:59:01:WU00:FS01:Upload 43.75% 23:59:07:WU00:FS01:Upload 52.49% 23:59:13:WU00:FS01:Upload 61.24% 23:59:19:WU00:FS01:Upload 69.99% 23:59:25:WU00:FS01:Upload 78.74% 23:59:31:WU00:FS01:Upload 87.49% 23:59:37:WU00:FS01:Upload 96.24% 23:59:39:WU00:FS01:Upload complete 23:59:40:WU00:FS01:Server responded WORK_ACK (400) 23:59:40:WU00:FS01:Final credit estimate, 63963.00 points 23:59:40:WU00:FS01:Cleaning up
00:02:17:WU03:FS01:0x17:Completed 0 out of 5000000 steps (0%) What does your log look like for these hung units? EDIT: Also does anyone know how to do a spoiler in this forum? I'm new here so sorry for taking up all the space with the log. Put it in a quote to make it a little smaller anyway lol EDIT2: Thanks meelvanchris that's better.
|
The future will rely on AI. SingularityNET lets anyone create, monetize, and use AI at scale. From the creators of Sophia the Robot.
|
|
|
mycryptocoin
Full Member
Offline
Activity: 380
Merit: 100
Community Manager - Blockchain analyst
|
|
May 15, 2014, 04:31:56 AM |
|
Hey there! We like CureCoin a lot and set up a new pool to spread the hashrate. Who helps finding the first block? - No registration required: Mine anonymously.
- 1% mining fee
How to mine CureCoin with usStep 1: Generate your CureCoin wallet address Step 2: Point your miner to stratum+tcp://pool.mycryptoco.in:50080 Step 3: Username = Your wallet address, Password doesn't matter (e.g. x) Step 4: As soon as the CureCoin Client allows us to send mined coins you'll get your CURE immediately
|
|
|
|
kqpahv
|
|
May 15, 2014, 04:35:25 AM |
|
I've been running into a lot of hung work units. The work unit will hit the end and just sit there forever at 99.99% with 3 seconds remaining. I've done a bit of looking around and from what I've seen so far they say look for connection errors in the logs. So far I haven't seen any but I have these hung work units on several computers. I'm not sure how to resolve them but they certainly are hurting my production.
About the only thing I've been able to do so far is restart the computer without stopping the work unit first. That seems to knock it back to a previous checkpoint and then it will process about 50% of the time after it redoes the work again which can take hours.
If I stop the work unit prior to rebooting it just sits are 99.99% again. There must be an easier way to get around these. Has anyone else been experiencing this?
I can confirm that this is a overclocking issue ! You can read about my experience on the few last pages. My Gpu's have always been rock solid with every coin but I had to down clock them to avoid the 99.99% problem. Here's what I found from the folding forum: The usual reason for this occurring is a GPU reset, check the Windows logs for this happening around the time the WU stopped progressing in the folding log. The cause can be an overclocked GPU that is not stable for folding or a driver crash.
Another action that will do this is sleeping or hibernating the system with a GPU WU active. The OS will reload regular RAM from where it is saved on disc for processes running on the CPU, but does not do that for GPU processing. A newer version of the GPU folding core is under test that is intended to detect that change in state and restart at the previous checkpoint, but has not yet been released to general use.
FYI the 99% thing is purely a cosmetic symptom while the client starts up, or shuts down. Sometimes it takes a little bit for the GUI to sync with the work unit. This is especially true with the above mentioned circumstances.
|
|
|
|
ChasingTheDream
|
|
May 15, 2014, 04:51:04 AM |
|
I've been running into a lot of hung work units. The work unit will hit the end and just sit there forever at 99.99% with 3 seconds remaining. I've done a bit of looking around and from what I've seen so far they say look for connection errors in the logs. So far I haven't seen any but I have these hung work units on several computers. I'm not sure how to resolve them but they certainly are hurting my production.
About the only thing I've been able to do so far is restart the computer without stopping the work unit first. That seems to knock it back to a previous checkpoint and then it will process about 50% of the time after it redoes the work again which can take hours.
If I stop the work unit prior to rebooting it just sits are 99.99% again. There must be an easier way to get around these. Has anyone else been experiencing this?
After you complete a work unit you should see something like this in the log: 23:58:06:WU00:FS01:0x17:Completed 5000000 out of 5000000 steps (100%)
23:58:08:WU03:FS01:Connecting to 171.67.108.201:80 23:58:08:WU03:FS01:Assigned to work server 140.163.4.231 23:58:08:WU03:FS01:Requesting new work unit for slot 01: RUNNING gpu:0:Pitcairn [] from 140.163.4.231 23:58:08:WU03:FS01:Connecting to 140.163.4.231:8080 23:58:09:WU03:FS01:Downloading 4.84MiB 23:58:11:WU03:FS01:Download complete 23:58:11:WU03:FS01:Received Unit: id:03 state:DOWNLOAD error:NO_ERROR project:13001 run:534 clone:7 gen:14 core:0x17 unit:0x0000001d538b3db7532c93b7e185f3f6
23:58:26:WU00:FS01:0x17:Saving result file logfile_01.txt 23:58:27:WU00:FS01:0x17:Saving result file checkpointState.xml 23:58:29:WU00:FS01:0x17:Saving result file checkpt.crc 23:58:29:WU00:FS01:0x17:Saving result file log.txt 23:58:29:WU00:FS01:0x17:Saving result file positions.xtc 23:58:31:WU00:FS01:0x17:Folding@home Core Shutdown: FINISHED_UNIT 23:58:31:WU00:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64) 23:58:31:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:13001 run:162 clone:2 gen:11 core:0x17 unit:0x00000021538b3db753287d9b0d4519a3 23:58:31:WU00:FS01:Uploading 12.86MiB to 140.163.4.231 23:58:31:WU00:FS01:Connecting to 140.163.4.231:8080
23:58:31:WU03:FS01:Starting 23:58:31:WU03:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/admin/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/ATI/R600/Core_17.fah/FahCore_17.exe -dir 03 -suffix 01 -version 704 -lifeline 4596 -checkpoint 15 -gpu 0 -gpu-vendor ati 23:58:32:WU03:FS01:Started FahCore on PID 848 23:58:32:WU03:FS01:Core PID:2244 23:58:32:WU03:FS01:FahCore 0x17 started 23:58:32:WU03:FS01:0x17:*********************** Log Started 2014-05-14T23:58:32Z *********************** 23:58:32:WU03:FS01:0x17:Project: 13001 (Run 534, Clone 7, Gen 14) 23:58:32:WU03:FS01:0x17:Unit: 0x0000001d538b3db7532c93b7e185f3f6 23:58:32:WU03:FS01:0x17:CPU: 0x00000000000000000000000000000000 23:58:32:WU03:FS01:0x17:Machine: 1 23:58:32:WU03:FS01:0x17:Reading tar file state.xml 23:58:33:WU03:FS01:0x17:Reading tar file system.xml 23:58:33:WU03:FS01:0x17:Reading tar file integrator.xml 23:58:33:WU03:FS01:0x17:Reading tar file core.xml 23:58:33:WU03:FS01:0x17:Digital signatures verified 23:58:33:WU03:FS01:0x17:Folding@home GPU core17 23:58:33:WU03:FS01:0x17:Version 0.0.52
23:58:37:WU00:FS01:Upload 7.78% 23:58:43:WU00:FS01:Upload 17.01% 23:58:49:WU00:FS01:Upload 25.76% 23:58:55:WU00:FS01:Upload 34.51% 23:59:01:WU00:FS01:Upload 43.75% 23:59:07:WU00:FS01:Upload 52.49% 23:59:13:WU00:FS01:Upload 61.24% 23:59:19:WU00:FS01:Upload 69.99% 23:59:25:WU00:FS01:Upload 78.74% 23:59:31:WU00:FS01:Upload 87.49% 23:59:37:WU00:FS01:Upload 96.24% 23:59:39:WU00:FS01:Upload complete 23:59:40:WU00:FS01:Server responded WORK_ACK (400) 23:59:40:WU00:FS01:Final credit estimate, 63963.00 points 23:59:40:WU00:FS01:Cleaning up
00:02:17:WU03:FS01:0x17:Completed 0 out of 5000000 steps (0%)
What does your log look like for these hung units? EDIT: Also does anyone know how to do a spoiler in this forum? I'm new here so sorry for taking up all the space with the log. Put it in a quote to make it a little smaller anyway lol My logs shows the updates stopped long before 99.99%. The 99.99% is not valid. It actually stopped at 29% for the log I was looking at. No errors in the F@H log but the updates stopped. I'm sure the GPU driver crashed. I need to look at the event log but I'm in the middle of another system rebuild at the moment. lol Got to love the late night (for me) computer battles. Thanks for the info!
|
|
|
|
ChasingTheDream
|
|
May 15, 2014, 04:53:44 AM |
|
I've been running into a lot of hung work units. The work unit will hit the end and just sit there forever at 99.99% with 3 seconds remaining. I've done a bit of looking around and from what I've seen so far they say look for connection errors in the logs. So far I haven't seen any but I have these hung work units on several computers. I'm not sure how to resolve them but they certainly are hurting my production.
About the only thing I've been able to do so far is restart the computer without stopping the work unit first. That seems to knock it back to a previous checkpoint and then it will process about 50% of the time after it redoes the work again which can take hours.
If I stop the work unit prior to rebooting it just sits are 99.99% again. There must be an easier way to get around these. Has anyone else been experiencing this?
I can confirm that this is a overclocking issue ! You can read about my experience on the few last pages. My Gpu's have always been rock solid with every coin but I had to down clock them to avoid the 99.99% problem. Here's what I found from the folding forum: The usual reason for this occurring is a GPU reset, check the Windows logs for this happening around the time the WU stopped progressing in the folding log. The cause can be an overclocked GPU that is not stable for folding or a driver crash.
Another action that will do this is sleeping or hibernating the system with a GPU WU active. The OS will reload regular RAM from where it is saved on disc for processes running on the CPU, but does not do that for GPU processing. A newer version of the GPU folding core is under test that is intended to detect that change in state and restart at the previous checkpoint, but has not yet been released to general use.
FYI the 99% thing is purely a cosmetic symptom while the client starts up, or shuts down. Sometimes it takes a little bit for the GUI to sync with the work unit. This is especially true with the above mentioned circumstances.Thanks for the info! I also saw your situation where you have two computers with identical hardware and one is running at essentially half the speed of the other. I've got the same situation and I'm rebuilding that machine right now. I suspect it also has to do with GPU's in that machine. But it has been hard reset many times while mining so I thought I would start fresh. I suspect the cards in that machine will actually need to be toned down a bit more than the others.
|
|
|
|
compumine
|
|
May 15, 2014, 04:57:45 AM |
|
Directed my bitcoin miner to this coin...
Is this coin sha and scrypt friendly? I read that it's good for asic and gpu mining?
|
*Image Removed*
|
|
|
bardacuda
|
|
May 15, 2014, 05:01:19 AM |
|
Directed my bitcoin miner to this coin...
Is this coin sha and scrypt friendly? I read that it's good for asic and gpu mining?
Mining is done with SHA algo...can use either ASIC or GPU for that. However, you get much higher returns using GPUs for folding rather than mining (and you help the scientific research...which is the point really). The scrypt algo is unrelated.
|
The future will rely on AI. SingularityNET lets anyone create, monetize, and use AI at scale. From the creators of Sophia the Robot.
|
|
|
kqpahv
|
|
May 15, 2014, 05:08:42 AM |
|
I've been running into a lot of hung work units. The work unit will hit the end and just sit there forever at 99.99% with 3 seconds remaining. I've done a bit of looking around and from what I've seen so far they say look for connection errors in the logs. So far I haven't seen any but I have these hung work units on several computers. I'm not sure how to resolve them but they certainly are hurting my production.
About the only thing I've been able to do so far is restart the computer without stopping the work unit first. That seems to knock it back to a previous checkpoint and then it will process about 50% of the time after it redoes the work again which can take hours.
If I stop the work unit prior to rebooting it just sits are 99.99% again. There must be an easier way to get around these. Has anyone else been experiencing this?
I can confirm that this is a overclocking issue ! You can read about my experience on the few last pages. My Gpu's have always been rock solid with every coin but I had to down clock them to avoid the 99.99% problem. Here's what I found from the folding forum: The usual reason for this occurring is a GPU reset, check the Windows logs for this happening around the time the WU stopped progressing in the folding log. The cause can be an overclocked GPU that is not stable for folding or a driver crash.
Another action that will do this is sleeping or hibernating the system with a GPU WU active. The OS will reload regular RAM from where it is saved on disc for processes running on the CPU, but does not do that for GPU processing. A newer version of the GPU folding core is under test that is intended to detect that change in state and restart at the previous checkpoint, but has not yet been released to general use.
FYI the 99% thing is purely a cosmetic symptom while the client starts up, or shuts down. Sometimes it takes a little bit for the GUI to sync with the work unit. This is especially true with the above mentioned circumstances.Thanks for the info! I also saw your situation where you have two computers with identical hardware and one is running at essentially half the speed of the other. I've got the same situation and I'm rebuilding that machine right now. I suspect it also has to do with GPU's in that machine. But it has been hard reset many times while mining so I thought I would start fresh. I suspect the cards in that machine will actually need to be toned down a bit more than the others. Yeah, I am still combating with the only 50% of PPD shown symptom. Checking the logs I found out that the PPD figure shown in the client is actually inaccurate ! I was getting twice as many points for my WU's than the GUI estimated. Looking at how much time the WU took and how many points it gave me I did the math and my actual PPD for each card was ~120K as it should be despite the client showing 55K So it's only a cosmetical thing but I would like to get it fixed for a better overview
|
|
|
|
atom1cdonkey
Member
Offline
Activity: 112
Merit: 10
|
|
May 15, 2014, 05:18:33 AM |
|
This looks very interesting. I have a pretty powerful gaming PC that I will use for folding. I've tested it for about 5 minutes, it showed me a rough 100k points per day. How much coins would this roughly equal?
Before I start using it 24/7 I will need to put some new cooling paste on the CPU, it is hitting 90c+ degrees...lol.
Thanks
|
BTC: 18ose7BN8xPkaHsT1XTetCBhoB4drDqLSP
|
|
|
bardacuda
|
|
May 15, 2014, 05:21:19 AM |
|
This looks very interesting. I have a pretty powerful gaming PC that I will use for folding. I've tested it for about 5 minutes, it showed me a rough 100k points per day. How much coins would this roughly equal?
Before I start using it 24/7 I will need to put some new cooling paste on the CPU, it is hitting 90c+ degrees...lol.
Thanks
See here: https://bitcointalk.org/index.php?topic=603757.msg6722773#msg6722773EDIT: What do you have for hardware? Not sure what you consider pretty powerful but a system with a single 7870/7950/270/280 should get 100k PPD. You should be able to get a lot more than that if you have something like crossfire 290Xs or whatever.
|
The future will rely on AI. SingularityNET lets anyone create, monetize, and use AI at scale. From the creators of Sophia the Robot.
|
|
|
atom1cdonkey
Member
Offline
Activity: 112
Merit: 10
|
|
May 15, 2014, 05:22:34 AM |
|
This looks very interesting. I have a pretty powerful gaming PC that I will use for folding. I've tested it for about 5 minutes, it showed me a rough 100k points per day. How much coins would this roughly equal?
Before I start using it 24/7 I will need to put some new cooling paste on the CPU, it is hitting 90c+ degrees...lol.
Thanks
See here: https://bitcointalk.org/index.php?topic=603757.msg6722773#msg6722773Thanks for the help. As soon as I can put a good week of folding in and I have some results, I will post them.
|
BTC: 18ose7BN8xPkaHsT1XTetCBhoB4drDqLSP
|
|
|
meelvanchris
|
|
May 15, 2014, 05:34:28 AM |
|
After you complete a work unit you should see something like this in the log: 23:58:06:WU00:FS01:0x17:Completed 5000000 out of 5000000 steps (100%)
23:58:08:WU03:FS01:Connecting to 171.67.108.201:80 23:58:08:WU03:FS01:Assigned to work server 140.163.4.231 23:58:08:WU03:FS01:Requesting new work unit for slot 01: RUNNING gpu:0:Pitcairn [] from 140.163.4.231 23:58:08:WU03:FS01:Connecting to 140.163.4.231:8080 23:58:09:WU03:FS01:Downloading 4.84MiB 23:58:11:WU03:FS01:Download complete 23:58:11:WU03:FS01:Received Unit: id:03 state:DOWNLOAD error:NO_ERROR project:13001 run:534 clone:7 gen:14 core:0x17 unit:0x0000001d538b3db7532c93b7e185f3f6
23:58:26:WU00:FS01:0x17:Saving result file logfile_01.txt 23:58:27:WU00:FS01:0x17:Saving result file checkpointState.xml 23:58:29:WU00:FS01:0x17:Saving result file checkpt.crc 23:58:29:WU00:FS01:0x17:Saving result file log.txt 23:58:29:WU00:FS01:0x17:Saving result file positions.xtc 23:58:31:WU00:FS01:0x17:Folding@home Core Shutdown: FINISHED_UNIT 23:58:31:WU00:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64) 23:58:31:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:13001 run:162 clone:2 gen:11 core:0x17 unit:0x00000021538b3db753287d9b0d4519a3 23:58:31:WU00:FS01:Uploading 12.86MiB to 140.163.4.231 23:58:31:WU00:FS01:Connecting to 140.163.4.231:8080
23:58:31:WU03:FS01:Starting 23:58:31:WU03:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/admin/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/ATI/R600/Core_17.fah/FahCore_17.exe -dir 03 -suffix 01 -version 704 -lifeline 4596 -checkpoint 15 -gpu 0 -gpu-vendor ati 23:58:32:WU03:FS01:Started FahCore on PID 848 23:58:32:WU03:FS01:Core PID:2244 23:58:32:WU03:FS01:FahCore 0x17 started 23:58:32:WU03:FS01:0x17:*********************** Log Started 2014-05-14T23:58:32Z *********************** 23:58:32:WU03:FS01:0x17:Project: 13001 (Run 534, Clone 7, Gen 14) 23:58:32:WU03:FS01:0x17:Unit: 0x0000001d538b3db7532c93b7e185f3f6 23:58:32:WU03:FS01:0x17:CPU: 0x00000000000000000000000000000000 23:58:32:WU03:FS01:0x17:Machine: 1 23:58:32:WU03:FS01:0x17:Reading tar file state.xml 23:58:33:WU03:FS01:0x17:Reading tar file system.xml 23:58:33:WU03:FS01:0x17:Reading tar file integrator.xml 23:58:33:WU03:FS01:0x17:Reading tar file core.xml 23:58:33:WU03:FS01:0x17:Digital signatures verified 23:58:33:WU03:FS01:0x17:Folding@home GPU core17 23:58:33:WU03:FS01:0x17:Version 0.0.52
23:58:37:WU00:FS01:Upload 7.78% 23:58:43:WU00:FS01:Upload 17.01% 23:58:49:WU00:FS01:Upload 25.76% 23:58:55:WU00:FS01:Upload 34.51% 23:59:01:WU00:FS01:Upload 43.75% 23:59:07:WU00:FS01:Upload 52.49% 23:59:13:WU00:FS01:Upload 61.24% 23:59:19:WU00:FS01:Upload 69.99% 23:59:25:WU00:FS01:Upload 78.74% 23:59:31:WU00:FS01:Upload 87.49% 23:59:37:WU00:FS01:Upload 96.24% 23:59:39:WU00:FS01:Upload complete 23:59:40:WU00:FS01:Server responded WORK_ACK (400) 23:59:40:WU00:FS01:Final credit estimate, 63963.00 points 23:59:40:WU00:FS01:Cleaning up
00:02:17:WU03:FS01:0x17:Completed 0 out of 5000000 steps (0%)
What does your log look like for these hung units? EDIT: Also does anyone know how to do a spoiler in this forum? I'm new here so sorry for taking up all the space with the log. Put it in a quote to make it a little smaller anyway lol By spoiler did you mean like so..? if yes, then it's the hastag # next to quote...
|
|
|
|
bardacuda
|
|
May 15, 2014, 05:46:37 AM |
|
By spoiler did you mean like so..? if yes, then it's the hastag # next to quote...
Ahh thanks...that's not exactly what I was trying to do but close enough...by spoiler I mean where you see a single line such as this: and you can toggle showing/hiding the full content by clicking it.
|
The future will rely on AI. SingularityNET lets anyone create, monetize, and use AI at scale. From the creators of Sophia the Robot.
|
|
|
sumgye
|
|
May 15, 2014, 05:47:07 AM |
|
I was wondering if anyone's considered hitting this thing from the third angle. We've got GPU's hitting the folding pretty hard. We've got SHA256 ASIC's hitting the mining end pretty hard. What about a multipool so the SCRYPT ASIC's can hit the value end of things? Then all mining hardware could be used to develop and support CureCoin. Just a thought.
|
|
|
|
cameronpalte
|
|
May 15, 2014, 05:47:37 AM |
|
This looks very interesting. I have a pretty powerful gaming PC that I will use for folding. I've tested it for about 5 minutes, it showed me a rough 100k points per day. How much coins would this roughly equal?
Before I start using it 24/7 I will need to put some new cooling paste on the CPU, it is hitting 90c+ degrees...lol.
Thanks
100,000 / 120,000,000 points * 7488 = 6.24 coins/day Price = 0.005 BTC/day = 0.0312 BTC / day $13.80 / day
|
|
|
|
|