I only tried a mining pool for a few hours before giving up on it. When I was getting those messages, it was because the pool network was hosed. I also saw extremely long deadlines when I tried to telnet to the mining pool ports directly.
The "no deadline" messages look perfectly normal to me for a 4TB drive. I just pulled the latest log for one of mine, and out of 276 blocks, no deadline was reported before the next block started 74 times. In your first "no deadline" message, the block was found before you had finished scanning your HD. In the second, it had only just started scanning the drive.
Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 760. (Read 2171056 times)
September 19, 2014, 07:54:05 PM
September 19, 2014, 07:50:32 PM
Code:
Could not get mining info from Node. Will retry..
Code:
Walet reported no deadline.
Why do I keep getting this?
The same.
September 19, 2014, 07:45:34 PM
Code:
Could not get mining info from Node. Will retry..
Code:
Walet reported no deadline.
Why do I keep getting this?
September 19, 2014, 07:44:05 PM
On dcct's new miner I keep getting this:
Is this normal? If not, how do I fix it? Please help!
Code:
Could not get mining info from Node. Will retry..
917 MB read/3671 GB total/deadline 1426805s (1426631s left)
New block 14088, basetarget 2407011
21 MB read/85 GB total/deadline 711256s (711246s left)
Walet reported no deadline.
917 MB read/3671 GB total/deadline 117016s (116939s left)
New block 14089, basetarget 2360711
317 MB read/1271 GB total/deadline 73700s (73684s left)
Walet reported no deadline.
917 MB read/3671 GB total/deadline 73700s (73307s left)
New block 14090, basetarget 2395043
0 MB read/0 GB total/no deadline
Walet reported no deadline.
917 MB read/3671 GB total/deadline 1426805s (1426631s left)
New block 14088, basetarget 2407011
21 MB read/85 GB total/deadline 711256s (711246s left)
Walet reported no deadline.
917 MB read/3671 GB total/deadline 117016s (116939s left)
New block 14089, basetarget 2360711
317 MB read/1271 GB total/deadline 73700s (73684s left)
Walet reported no deadline.
917 MB read/3671 GB total/deadline 73700s (73307s left)
New block 14090, basetarget 2395043
0 MB read/0 GB total/no deadline
Walet reported no deadline.
Is this normal? If not, how do I fix it? Please help!
Can someone familiar with dcct's new miner please answer this for me?
Its not normal, pool or solo mining?
New block 14094, basetarget 2446962
1360 MB read/5440 GB total/deadline 178039s (177773s left)
New block 14095, basetarget 2505140
1360 MB read/5440 GB total/deadline 5074s (4930s left)
New block 14096, basetarget 2554054
1360 MB read/5440 GB total/deadline 520849s (520485s left)
New block 14097, basetarget 2671767
1360 MB read/5440 GB total/deadline 381845s (381787s left)
New block 14098, basetarget 2492339
1360 MB read/5440 GB total/deadline 1075203s (10748s left)
New block 14099, basetarget 2550128
1360 MB read/5440 GB total/deadline 3395s (3175s left)
New block 14100, basetarget 2586473
I'm mining at a pool but it's not uray's, it's another pool based on uray's.
Anyone using dcct's miner care to help me out?
September 19, 2014, 07:39:14 PM
I'm running 4TB on a quad-core with 4GB RAM (Win7).
Both the "burst-pool-miner" and the new "burst-miner" miners absolutely thrashes whatever drive I have the pagefile setup on (causing the system to be pretty much unusable).
I have already disabled prefetch/superfetch like several have suggested and the pagefile usage is a lot better, but still gets hit up really hard.
I've tested this same system running Ubuntu instead of Windows 7... and it works perfectly fine... same hardware, different OS.
On the other hand, I have another system with a 4TB, 4GB RAM, but running Windows Server 2012... and has 0 issues with resources like Win7.
What is going on with the Memory/Pagefile usage in Windows 7 when mining? and does anyone know of a solution?
Both the "burst-pool-miner" and the new "burst-miner" miners absolutely thrashes whatever drive I have the pagefile setup on (causing the system to be pretty much unusable).
I have already disabled prefetch/superfetch like several have suggested and the pagefile usage is a lot better, but still gets hit up really hard.
I've tested this same system running Ubuntu instead of Windows 7... and it works perfectly fine... same hardware, different OS.
On the other hand, I have another system with a 4TB, 4GB RAM, but running Windows Server 2012... and has 0 issues with resources like Win7.
What is going on with the Memory/Pagefile usage in Windows 7 when mining? and does anyone know of a solution?
September 19, 2014, 07:16:46 PM
can you elaborate on how the payments work on these pools?
On uray based pools, the pool takes the one best deadline you find each block and runs it through a formula to give you a score. When the pool finds a block, it splits it up based on the scores users have.
On my v2 pool, the pool has a set deadline target, and amount of shares to keep. The miner submits each share that results in a deadline under the target. The pool always maintains a fixed amount of shares, so when a new one is submitted, the oldest one is discarded. When a block is found, it splits the block up based on the number of shares each user has in that fixed size buffer.
Will you make the source code available for the v2 pool?
September 19, 2014, 06:58:45 PM
can you elaborate on how the payments work on these pools?
On uray based pools, the pool takes the one best deadline you find each block and runs it through a formula to give you a score. When the pool finds a block, it splits it up based on the scores users have.
On my v2 pool, the pool has a set deadline target, and amount of shares to keep. The miner submits each share that results in a deadline under the target. The pool always maintains a fixed amount of shares, so when a new one is submitted, the oldest one is discarded. When a block is found, it splits the block up based on the number of shares each user has in that fixed size buffer.
Will you make the source code available for the v2 pool?
September 19, 2014, 06:42:59 PM
can you elaborate on how the payments work on these pools?
On uray based pools, the pool takes the one best deadline you find each block and runs it through a formula to give you a score. When the pool finds a block, it splits it up based on the scores users have.
On my v2 pool, the pool has a set deadline target, and amount of shares to keep. The miner submits each share that results in a deadline under the target. The pool always maintains a fixed amount of shares, so when a new one is submitted, the oldest one is discarded. When a block is found, it splits the block up based on the number of shares each user has in that fixed size buffer.
September 19, 2014, 06:33:12 PM
ok, well that's a start, haven't found anywhere where someone has specifically stated how it pays out. interesting..
Thanks!!
Thanks!!
Payments have been lowered to 100 on my pool. Given we find a block...
I also might get a friend to work, or at least try and make an Android wallet.
But for that we need coins. And to get coins I need miners on the pool
September 19, 2014, 06:31:39 PM
ok, well that's a start, haven't found anywhere where someone has specifically stated how it pays out. interesting..
Thanks!!
Thanks!!
September 19, 2014, 06:07:21 PM
can you elaborate on how the payments work on these pools?
No
EDIT: sorry, I don't know how it works....but I'll guess...it counts shares, when a block is found(say 3000 shares are submitted before a block is found, and you submitted 150) then you get 5% of 9500 coins, but then it waits till you have 500 balance, then pays out.
September 19, 2014, 06:03:36 PM
can you elaborate on how the payments work on these pools?
September 19, 2014, 06:03:25 PM
The new one stores a lot more in memory before it writes to disk. I'm guessing this helps cut down on the disk seeking a lot.
Oh thanks, I missed that because I had already set SSIZE by hand to max out the memory.
September 19, 2014, 06:03:02 PM
oh, sorry.. 
September 19, 2014, 06:01:20 PM
how are the payouts figured on this pool? I found a block with 763 deadline, but havent been awarded anything its been almost an hour. how many confirmations before it his my wallet?
Whats this about a 30% fee?? WTF!!
Whats this about a 30% fee?? WTF!!
1.5% fee, 30% of the 1.5% fee goes to the gui(so 0.45% to gui, 1.05% to maintenance and fanepatent)
EDIT: actually was changed to 1% fee, so 0.3% to gui, 0.7% to fane and maintanence
September 19, 2014, 06:00:19 PM
how are the payouts figured on this pool? I found a block with 763 deadline, but havent been awarded anything its been almost an hour. how many confirmations before it hits my wallet?
Whats this about a 30% fee?? WTF!!
Whats this about a 30% fee?? WTF!!
September 19, 2014, 05:55:23 PM
Join http://burstpool.ddns.net people
30% of the fee will go towards developers of the windows GUI AIO tool.
30% of the fee will go towards developers of the windows GUI AIO tool.
You just lost all your *nix miners.
lmfao, the thing is, 'nix users don't need a GUI. They usually prefer command line. lol
Also, a GUI for newbies will bring more people overall to burst, which is good for everyone!
September 19, 2014, 05:36:05 PM
On dcct's new miner I keep getting this:
Is this normal? If not, how do I fix it? Please help!
Code:
Could not get mining info from Node. Will retry..
917 MB read/3671 GB total/deadline 1426805s (1426631s left)
New block 14088, basetarget 2407011
21 MB read/85 GB total/deadline 711256s (711246s left)
Walet reported no deadline.
917 MB read/3671 GB total/deadline 117016s (116939s left)
New block 14089, basetarget 2360711
317 MB read/1271 GB total/deadline 73700s (73684s left)
Walet reported no deadline.
917 MB read/3671 GB total/deadline 73700s (73307s left)
New block 14090, basetarget 2395043
0 MB read/0 GB total/no deadline
Walet reported no deadline.
917 MB read/3671 GB total/deadline 1426805s (1426631s left)
New block 14088, basetarget 2407011
21 MB read/85 GB total/deadline 711256s (711246s left)
Walet reported no deadline.
917 MB read/3671 GB total/deadline 117016s (116939s left)
New block 14089, basetarget 2360711
317 MB read/1271 GB total/deadline 73700s (73684s left)
Walet reported no deadline.
917 MB read/3671 GB total/deadline 73700s (73307s left)
New block 14090, basetarget 2395043
0 MB read/0 GB total/no deadline
Walet reported no deadline.
Is this normal? If not, how do I fix it? Please help!
Can someone familiar with dcct's new miner please answer this for me?
Its not normal, pool or solo mining?
New block 14094, basetarget 2446962
1360 MB read/5440 GB total/deadline 178039s (177773s left)
New block 14095, basetarget 2505140
1360 MB read/5440 GB total/deadline 5074s (4930s left)
New block 14096, basetarget 2554054
1360 MB read/5440 GB total/deadline 520849s (520485s left)
New block 14097, basetarget 2671767
1360 MB read/5440 GB total/deadline 381845s (381787s left)
New block 14098, basetarget 2492339
1360 MB read/5440 GB total/deadline 1075203s (10748s left)
New block 14099, basetarget 2550128
1360 MB read/5440 GB total/deadline 3395s (3175s left)
New block 14100, basetarget 2586473
I'm mining at a pool but it's not uray's, it's another pool based on uray's.
September 19, 2014, 05:35:22 PM
Well this turned out to be my worst investment...wouldn't recommend clouding mining.
Will use what I made and set a buy order sub 20 sat...
this sounds like a plan.Will use what I made and set a buy order sub 20 sat...
i thought of doing a martingale trading strategy each time 1 btc doubles my balance
September 19, 2014, 05:31:03 PM
Join http://burstpool.ddns.net people
30% of the fee will go towards developers of the windows GUI AIO tool.
30% of the fee will go towards developers of the windows GUI AIO tool.
You just lost all your *nix miners.
Jump to: