Topic: [ANN] New Primecoin Pool + GPU Miner - page 6. (Read 19667 times)
Are those coin that have been mined already still eventually reach my wallet?
MadMax, please add timestamps to miner output (may be in the next version)...
I know this up and down again sucks, but in software development stuff never works on first try, it's always a process.
If you don't want to be part of the process then just wait a few days
GPU activity:
...
[GPU 3] A=64% 7950
CPU load 25-30%
AMD Athlon X2 2 core
It`s not good values ?
Some 7950s have issues with powertune which will make the A=% reading meaningless. Your CPU load seems fine, you can also try cpuload="0" in config.txt for lower cpu load. ...
[GPU 3] A=64% 7950
CPU load 25-30%
AMD Athlon X2 2 core
It`s not good values ?
GPU activity:
[GPU 0] A=98% 7970
[GPU 1] A=98% 7970
[GPU 2] A=98% 7970
[GPU 3] A=64% 7950
CPU load 25-30%
AMD Athlon X2 2 core
It`s not good values ?
[GPU 0] A=98% 7970
[GPU 1] A=98% 7970
[GPU 2] A=98% 7970
[GPU 3] A=64% 7950
CPU load 25-30%
AMD Athlon X2 2 core
It`s not good values ?
madMAx510510 tell me please what is mean the following values
T - ?
A- ?
E - ?
primes - ?
fermat- ?
[GPU 0] T=61C A=99% E=0 primes=0.102144 fermat=391718/sec cpd=4.18/day
[GPU 1] T=60C A=99% E=0 primes=0.102022 fermat=390992/sec cpd=4.13/day
[GPU 2] T=62C A=99% E=0 primes=0.102153 fermat=391804/sec cpd=4.19/day
[GPU 3] T=61C A=99% E=0 primes=0.102158 fermat=343804/sec cpd=3.68/day
T - ?
A- ?
E - ?
primes - ?
fermat- ?
[GPU 0] T=61C A=99% E=0 primes=0.102144 fermat=391718/sec cpd=4.18/day
[GPU 1] T=60C A=99% E=0 primes=0.102022 fermat=390992/sec cpd=4.13/day
[GPU 2] T=62C A=99% E=0 primes=0.102153 fermat=391804/sec cpd=4.19/day
[GPU 3] T=61C A=99% E=0 primes=0.102158 fermat=343804/sec cpd=3.68/day
T = Temp
A = GPU activity (ie. load)
E = error count
primes = average prime probablility
fermat = number of fermats tests per second
move service to cloudflare! perfect ddos protection guaranteed! fee would be enough to pay for it. in other case ddos will be permanent.
Once i fix these invalid data issues the server should be ok with these small scale attacks. 
madMAx510510 tell me please what is mean the following values
T - ?
A- ?
E - ?
primes - ?
fermat- ?
[GPU 0] T=61C A=99% E=0 primes=0.102144 fermat=391718/sec cpd=4.18/day
[GPU 1] T=60C A=99% E=0 primes=0.102022 fermat=390992/sec cpd=4.13/day
[GPU 2] T=62C A=99% E=0 primes=0.102153 fermat=391804/sec cpd=4.19/day
[GPU 3] T=61C A=99% E=0 primes=0.102158 fermat=343804/sec cpd=3.68/day
T - ?
A- ?
E - ?
primes - ?
fermat- ?
[GPU 0] T=61C A=99% E=0 primes=0.102144 fermat=391718/sec cpd=4.18/day
[GPU 1] T=60C A=99% E=0 primes=0.102022 fermat=390992/sec cpd=4.13/day
[GPU 2] T=62C A=99% E=0 primes=0.102153 fermat=391804/sec cpd=4.19/day
[GPU 3] T=61C A=99% E=0 primes=0.102158 fermat=343804/sec cpd=3.68/day
T - temp GPU
A- Acept
E - Error
Alright guys, pool works again, this time properly fixed.
All the issues were cause by the ancient ulimit -n of 1024. Basically the server ran out of file descriptors and this caused the blockchain to go corrupt.
This is also why the DOS was so effective and why it crashed again once we hit >100 workers.
I set the ulimit -n now to 102400, more than enough
UPDATE: DOS hit again! Had to shut down the server to prevent any further damage!
All the issues were cause by the ancient ulimit -n of 1024. Basically the server ran out of file descriptors and this caused the blockchain to go corrupt.
This is also why the DOS was so effective and why it crashed again once we hit >100 workers.
I set the ulimit -n now to 102400, more than enough
UPDATE: DOS hit again! Had to shut down the server to prevent any further damage!
move service to cloudflare! perfect ddos protection guaranteed! fee would be enough to pay for it. in other case ddos will be permanent.
madMAx510510 tell me please what is mean the following values
T - ?
A- ?
E - ?
primes - ?
fermat- ?
[GPU 0] T=61C A=99% E=0 primes=0.102144 fermat=391718/sec cpd=4.18/day
[GPU 1] T=60C A=99% E=0 primes=0.102022 fermat=390992/sec cpd=4.13/day
[GPU 2] T=62C A=99% E=0 primes=0.102153 fermat=391804/sec cpd=4.19/day
[GPU 3] T=61C A=99% E=0 primes=0.102158 fermat=343804/sec cpd=3.68/day
T - ?
A- ?
E - ?
primes - ?
fermat- ?
[GPU 0] T=61C A=99% E=0 primes=0.102144 fermat=391718/sec cpd=4.18/day
[GPU 1] T=60C A=99% E=0 primes=0.102022 fermat=390992/sec cpd=4.13/day
[GPU 2] T=62C A=99% E=0 primes=0.102153 fermat=391804/sec cpd=4.19/day
[GPU 3] T=61C A=99% E=0 primes=0.102158 fermat=343804/sec cpd=3.68/day
There is an issue where invalid strings from DOS attacks are accepted. I will need to make a complete DOS proof check of the server code.
This will take at least 1h guys. The server will be offline until then.
This will take at least 1h guys. The server will be offline until then.
Alright guys, pool works again, this time properly fixed.
All the issues were cause by the ancient ulimit -n of 1024. Basically the server ran out of file descriptors and this caused the blockchain to go corrupt.
This is also why the DOS was so effective and why it crashed again once we hit >100 workers.
I set the ulimit -n now to 102400, more than enough
UPDATE: DOS hit again! Had to shut down the server to prevent any further damage!
pool down All the issues were cause by the ancient ulimit -n of 1024. Basically the server ran out of file descriptors and this caused the blockchain to go corrupt.
This is also why the DOS was so effective and why it crashed again once we hit >100 workers.
I set the ulimit -n now to 102400, more than enough
UPDATE: DOS hit again! Had to shut down the server to prevent any further damage!
, again
Pool worked a couple of minutes, now rests a couple of hours?
Alright guys, pool works again, this time properly fixed.
All the issues were cause by the ancient ulimit -n of 1024. Basically the server ran out of file descriptors and this caused the blockchain to go corrupt.
This is also why the DOS was so effective and why it crashed again once we hit >100 workers.
I set the ulimit -n now to 102400, more than enough
All the issues were cause by the ancient ulimit -n of 1024. Basically the server ran out of file descriptors and this caused the blockchain to go corrupt.
This is also why the DOS was so effective and why it crashed again once we hit >100 workers.
I set the ulimit -n now to 102400, more than enough
It's down again.
Alright guys, pool works again, this time properly fixed.
All the issues were cause by the ancient ulimit -n of 1024. Basically the server ran out of file descriptors and this caused the blockchain to go corrupt.
This is also why the DOS was so effective and why it crashed again once we hit >100 workers.
I set the ulimit -n now to 102400, more than enough
UPDATE: DOS hit again! Had to shut down the server to prevent any further damage!
All the issues were cause by the ancient ulimit -n of 1024. Basically the server ran out of file descriptors and this caused the blockchain to go corrupt.
This is also why the DOS was so effective and why it crashed again once we hit >100 workers.
I set the ulimit -n now to 102400, more than enough
UPDATE: DOS hit again! Had to shut down the server to prevent any further damage!
pool working - please upload new vorking version
Mad i recommend to make the miner multipool with 10% fee. Or add suport for ypool.
NA screw ypool MORE COINS FOR ZNA
Mad i recommend to make the miner multipool with 10% fee. Or add suport for ypool.
+1
Mad i recommend to make the miner multipool with 10% fee. Or add suport for ypool.
Seems like the Intel Core cpu's have a GMP issue.
I'm having no issues like that with AMD or Core2 Quad cpu's.
I'm having no issues like that with AMD or Core2 Quad cpu's.
similar problem
Pentium g2030
win8.1 x64
catalist 13.12
x6 asus r9 280x
https://bitcointalksearch.org/topic/m.6597096
It works!
slacker still sleeping(
Jump to: