 Show Posts
|
|
Pages: [1] 2 3 »
|
|
Wow,
seems to be a good game/idea.
If anyone wants to play: I'm hanging out in the IRC.
|
|
|
|
|
Wow,
seems to be a good game/idea.
If anyone wants to play: I'm hanging out in the IRC.
|
|
|
|
|
mhm.
could be factor used to even to this out?
i know how does slush it does, but i don't like it.
|
|
|
|
|
Hi,
I've done some reading on various possibilities in order to prevent pool-hopping.
At some point I had my own idea and I'd like some feedback, may be I'm
missing something.
userScore = t //seconds since round start for the submitted share
after the round is finished all scores of the user and the totalScore
will be summed up, resulting in:
reward = userScore/totalScore*50
Any ideas about what I'm missing?
Eliel_ in the irc already pointed out that may be miners
don't want to mine at the start of a round.
But sadly I have not enough data, to do some simulations.
|
|
|
|
|
After some testing, with the help from denisx in the irc, we figured out that this issue seems to
bo related to pushpool, phoenix and perhaps nvidia, all combined.
He runs a pool too and when I've pointed my phoenixminer at his pool, the same results.
Now, when I do the same thing with poclbm against my and his pool I have no unknown-work, in fact ~0 stales.
Tested with different versions of phoenix and pushpool.
diablo-miner and poclbm are working great.
additionally denisx reported that some members of his pool with nvidia cards have problems too.
|
|
|
|
|
the problem is still present.
i pledge 50$ for a solution. I'd pay via paypal since I have not much BTC.
|
|
|
|
|
I've tried increasing the askrate and it helps a litte bit.
their are still 50% unknown-works, how can i check that pushpool logs everything right?
|
|
|
|
Is this the "auth.cred_cache.expire" : 75, option?
No. And if not how do I get pushpool do keep it longer, or is the problem
somewhere else on the host?
The problem is with miners submitting old work. They should not submit work older than 60 seconds, much less 120 seconds. increasing the askrate of the miner would help against this? but why do I have no troubles on other pools? |
|
|
|
|
you're right.
but the problem is very strange.
i figured out it has to be something wrong with the log.
i've received work and submitted within 120seconds.
where does pushpool log this, in memcached?
|
|
|
|
|
Is this the "auth.cred_cache.expire" : 75, option?
And if not how do I get pushpool do keep it longer, or is the problem
somewhere else on the host?
|
|
|
|
here is the config: {
"listen" : [
{ "port" : 8342 },
{ "port" : 8332, "protocol" : "http-json" },
{ "port" : 8335, "protocol" : "http-json",
"proxy" : "XXX.XXX.XXX.XXX" },
{ "host" : "127.0.0.1", "port" : 8338, "protocol" : "binary" }
],
"database" : {
"engine" : "mysql",
"host" : "localhost",
"port" : 3306,
"name" : "XXXXXXXX",
"username" : "XXXXXXXXXXXXXX",
"password" : "XXXXXXXXXXXXXXXXXXXx",
"sharelog" : true,
"stmt.pwdb":"SELECT password FROM pool_worker WHERE username = ?",
"stmt.sharelog":"INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES (?, ?, ?, ?, ?, ?)"
},
"memcached" : {
"servers" : [
{ "host" : "127.0.0.1", "port" : 11211 }
]
},
"pid" : "/home/XXXXXX/bitcoin/pushpool.pid",
"forcehost" : "localhost.localdomain",
"log.requests" : "/home/XXXXXX/bitcoin/request.log",
"log.shares" : "/home/XXXXXX/bitcoin/shares.log",
"longpoll.disable" : false,
"auth.cred_cache.expire" : 75,
"rpc.url" : "http://127.0.0.1:10000/",
"rpc.user" : "XXXXXXXXXXXXXXXXXXXX",
"rpc.pass" : "XXXXXXXXXXXXXX",
"rpc.target.rewrite" : true,
"roll.ntime.disable" : true
}
and thx for your help |
|
|
|
|
yes I did, this is frustrating. I have no clue where this comes from.
|
|
|
|
Thanks for the hint  . I'm now testing, with and without the patch suggested by redditorrex. so far it's not looking that good :/. edit: it got a little bit better. |
|
|
|
|
Hello,
i've played a bit aroung with pushpoold and everything worked just fine.
But when I asked a friend for a little test something strange happened.
I have about 100MH/s my friend has 1500MH/s.
As soon as my friend joined for testing i got a lot of stales,
I looked it up in the datase and the reason is "unknown-work".
Where does this come from?
Help with this would be really nice.
regards, redshark1802
ps: things I've tried so far with help from the irc-channnel
-checking that the blockchain is complete
-checking if the time is correct
-decreased the speed from my friend to 300MH/s
-my friend has no problems at all
-unknown is like 90% of the work sent
|
|
|
|
|
Hello,
i've played a bit aroung with pushpoold and everything worked just fine.
But when I asked a friend for a little test something strange happened.
I have about 100MH/s my friend has 1500MH/s.
As soon as my friend joined for testing i got a lot of stales,
I looked it up in the datase and the reason is "unknown-work".
Where does this come from?
Help with this would be really nice.
regards, redshark1802
|
|
|
|
use ./pushpoold -E -c server.json  regards, redshark1802 |
|
|
|
try apt-get install memcached regards, redshark1802 |
|
|
|
|
