ethpool.org - Predictable solo mining pool

1161719212226

Comments

  • BiodomBiodom Member Posts: 693 ✭✭✭
    edited March 2016
    @dr_pra
    I am wondering why stopping qtminer for a few seconds, then restarting it is causing the program to start rebuilding DAG from 0% again. I could not figure out what is triggering this. I know that a couple of seconds between stop and restart does not do it, but why is this happening for slightly longer times, like 30 sec. I did not get this with ethminer.
  • dlehenkydlehenky Member Posts: 2,249 ✭✭✭✭
    @Biodom I noticed that, too, when I tried out qtminer. However, if it's just rebuilding the *next* DAG, not the current one, you should be mining full tilt while the DAG action is occurring. Having said that, a very low end CPU may not be able to do that. I have 2-core 2-thread i3's. Anyway, next to no failover, that's the second reason I went with eth-proxy per rig.
  • BiodomBiodom Member Posts: 693 ✭✭✭
    @dlehenky thanks
    OK re "next" DAG. Powhash was showing mining numbers, but I never know if they are real or 'fake" until DAG is built. I might try eth-proxy tomorrow.
  • dlehenkydlehenky Member Posts: 2,249 ✭✭✭✭
    @Biodom They're real. They are mining off the current DAG, while the future DAG is being built. I would say the "gap" in time necessary to trigger the future DAG rebuild is based on whether a new block has come in while qtminer wasn't running.
  • dlehenkydlehenky Member Posts: 2,249 ✭✭✭✭
    Wow, ethpool hash rate just dropped 40 GH. Did the EU server go down or something?
  • o0ragman0oo0ragman0o Member, Moderator Posts: 1,291 mod
    Look like it's across the whole network. Not seen anyone report cards dropping off. Perhaps more daylight savings stats adjustments???

    Maybe just my imagination... Stats have been weird all day too. Diff's been trying to pull times up to 16 but they seem to be staying well below 15 yet global hash has hung low 1.2~1.3.
  • SIRacer09SIRacer09 Member Posts: 246 ✭✭
    Yeah.. My EthProxy disconnected... Closed and reconnected but not showing on dashboard yet.
  • o0ragman0oo0ragman0o Member, Moderator Posts: 1,291 mod
    Are yes... mine too at about 0:00UTC. had to reboot 2 of 3 rigs. (That was only 3 hours ago man I've got a crap memory) So I image many still down.
  • BiodomBiodom Member Posts: 693 ✭✭✭
    edited March 2016
    yes, weird stats, claims of invalid shares, disconnect, reconnect.
    is this still a consequence of time change?
    Boy, do i dislike this jumping time (twice a year).
    BTW, Russia gave it up recently after 3-4 decades or so, not that we have to follow.
    Nobody calculates how much time and money was spent reprogramming the stuff.
  • SIRacer09SIRacer09 Member Posts: 246 ✭✭
    Weird... Reported hashrate is 110 MHS, but Effective still really low from other miner... Hmmm
  • dlehenkydlehenky Member Posts: 2,249 ✭✭✭✭
    Strange, my stats didn't change at all, that's way I was thinking EU was down.
  • SIRacer09SIRacer09 Member Posts: 246 ✭✭
    edited March 2016
    Getting errors....

    2016-03-27 22:48:25,882 INFO proxy # MAIN eth_submitWork 0xbbe1b7a939e34df2 by
    2016-03-27 22:48:26,101 WARNING protocol # Failed message: local variable 'meta
    referenced before assignment from 104.236.133.86
    2016-03-27 22:48:26,117 INFO proxy # Disconnected from Stratum pool at us2.ethe
    mine.org:4444
    2016-03-27 22:48:26,117 INFO stats # 3 peers connected, state changed 1 times
    2016-03-27 22:48:29,019 INFO proxy # Hashrate for **** is 146.285714 MHs
    2016-03-27 22:48:29,283 INFO stats # 4 peers connected, state changed 1 times
    2016-03-27 22:48:29,283 INFO proxy # Connected to Stratum pool at us2.ethermine


    Says my effective rate is 10 MHs... not even close to 110. :)

    Oh, and it doesn't even show the miner as being active, but shows it's hashrate... something definitely messed up
  • dlehenkydlehenky Member Posts: 2,249 ✭✭✭✭
    @SIRacer09 That's not a big deal, if it's just for a few seconds. Any glitch anywhere in the network between us and the pool servers can cause short re-connects. It's when it goes on for a number of minutes that it's a concern. Just my take.
  • SIRacer09SIRacer09 Member Posts: 246 ✭✭
    Been going on for about an hour now.... :( Total pool hashrate dropped big time as well.
  • dlehenkydlehenky Member Posts: 2,249 ✭✭✭✭
    @SIRacer09 Some big hashers dropped off all at once, and are now coming back.
  • SIRacer09SIRacer09 Member Posts: 246 ✭✭
    I guess what I'm saying is I can't get my other rig to show up on the dashboard anymore... Just showing the 1 with 15 MHS, not my big one with 110 MHS
  • dlehenkydlehenky Member Posts: 2,249 ✭✭✭✭
    @SIRacer09 Are you sure you're not failing-over to dwarfpool or something? It's happened to me before, that's why I'm mentioning it. Of course, if you're not using eth-proxy, forget what I just said :)
  • SIRacer09SIRacer09 Member Posts: 246 ✭✭
    @dlehenky Haha! I just changed my pool to dwrfpool and got an error on the daahboard that said something about corrupted DAG. Redownloading now to see if that helps... 23% and counting.
  • workwork Member Posts: 2,084 ✭✭✭✭
    edited March 2016
    @dlehenky @o0ragman0o something wack with ethminer and ethpool recently. I've been reporting it about my rigs for a little while now. Stratum has been dropping connections, which isn't a big deal because usually the miner will reconnect after a brief period. However, sometimes when the connection is dropped and re-established, all submitted shares are not accepted, and then either the miner stop mining indefinitely, or it keeps mining on the same work indefinitely until restarted. I presume it's a bug in the common parts of ethminer/qtminer/genoil, triggered by the pool acting up. I have been getting dropped connections with ethpool very regularly in the past few days, but none at all with miningpoolhub.
  • SIRacer09SIRacer09 Member Posts: 246 ✭✭
    Finally got mine reconnected to Ethermine... Interesting though. It says I have 5/5 invalid shares... But I'm using ethproxy not QtMiner.... Hmmmm weird night tonight!
  • dlehenkydlehenky Member Posts: 2,249 ✭✭✭✭
    @work I didn't experience that at all. All 18 of my rigs just kept on mining. I've been getting my blocks right on cue all day. I don't know about the ethminer you are using, but both qtminer and Genoil's miner are based on ethminer code that's old, at this point. I built my own from the 1.0 release that came out in November, I believe. I don't think it's 'ethminer' per se, but some of the shared libs that have been updated along the way. I really have no idea if this has anything to do with anything, really, just putting it out there as another data point.
  • o0ragman0oo0ragman0o Member, Moderator Posts: 1,291 mod
    @work @dlehenky, my experience was that 2 of 3 ethproxies crashed. Restarting didn't help so I had to reboot. I didn't really take time to investigate.
  • workwork Member Posts: 2,084 ✭✭✭✭
    edited March 2016
    @dlehenky that leans towards the suspicion I had in my previous post - I presume it's a bug in the common parts of ethminer/qtminer/genoil, triggered by the pool acting up. Glad to hear that a compile from webthree-umbrella isn't crashing out.

    My 3 rigs pointed to ethpool just dropped stratum and reconnected again a few minutes ago btw; they came back up fine this time tho. It's always the same message before the connection drops: "Read response failed: End of file." And usually when that happens, there hasn't been a new job received for some time (so the mining effort for an unknown amount of time was lost/wasted).

    Edit: looking back over the logs of one rig, the stratum connection dropped twice in about 3 minutes, and no new jobs were received for about 5 minutes. Miner was still hashing away, but obviously on nothing useful.
  • dlehenkydlehenky Member Posts: 2,249 ✭✭✭✭
    @o0ragman0o I'm on eth-proxy v005, if that matters.
  • workwork Member Posts: 2,084 ✭✭✭✭
    edited March 2016
    and it happened again... bit different this time.
    [...] mining okay and then
    X 22:09:34| Read response failed: End of file
    i 22:09:34| Stopping farm
    i 22:09:34| Reconnecting in 3 seconds...
    i 22:09:37| Connecting to stratum server us2.ethpool.org:3333
    i 22:09:37| Connected to stratum server us2.ethpool.org : 3333
    i 22:09:37| Starting farm
    i 22:09:37| Subscribed to stratum server
    i 22:09:37| Authorized worker 0x3a55b016d8b23dd14a9902fdda1b91eab9860963.terminal
    miner 22:09:38|main Mining on PoWhash #5716f2e4 : 0 H/s = 0 hashes / 0.524 s
    miner 22:09:40|main Mining on PoWhash #5716f2e4 : 0 H/s = 0 hashes / 2.003 s
    miner 22:09:42|main Mining on PoWhash #5716f2e4 : 0 H/s = 0 hashes / 2.004 s
    miner 22:09:44|main Mining on PoWhash #5716f2e4 : 0 H/s = 0 hashes / 2.003 s
    miner 22:09:46|main Mining on PoWhash #5716f2e4 : 0 H/s = 0 hashes / 2.003 s
    miner 22:09:48|main Mining on PoWhash #5716f2e4 : 0 H/s = 0 hashes / 2.004 s
    miner 22:09:50|main Mining on PoWhash #5716f2e4 : 0 H/s = 0 hashes / 2.004 s
    miner 22:09:52|main Mining on PoWhash #5716f2e4 : 0 H/s = 0 hashes / 2.003 s
    miner 22:09:54|main Mining on PoWhash #5716f2e4 : 0 H/s = 0 hashes / 2.004 s
    miner 22:09:56|main Mining on PoWhash #5716f2e4 : 0 H/s = 0 hashes / 2.003 s
    X 22:09:57| Discarding incomplete response
    X 22:09:57| Discarding incomplete response
    X 22:09:57| Discarding incomplete response
    miner 22:09:58|main Mining on PoWhash #5716f2e4 : 0 H/s = 0 hashes / 2.004 s
    miner 22:10:00|main Mining on PoWhash #5716f2e4 : 0 H/s = 0 hashes / 2.003 s
    miner 22:10:02|main Mining on PoWhash #5716f2e4 : 0 H/s = 0 hashes / 2.004 s
    X 22:10:02| Parse response failed: * Line 1, Column 42
    Missing ',' or '}' in object declaration

    Then it reconnected and init'd mining again.

    ---
    Definitely looks like ethpool is messing up stratum messages.

    Edit: this is on us2, although I observed the same thing on us1 earlier.
  • dr_pradr_pra Member Posts: 445 ✭✭✭
    We had to perform an emergency upgrade to our stratum backend as geth became more and more unstable.

    As a side effect we are now able to offer poll-free mining, meaning our pool process does not continuously poll geth for new work (getwork like). Instead we patched geth to notify our pool service if new work is now available. This ensures a minimal delay between the time a new block arrives and the pool starts to work on the next block. Our tests showed that the transport time from geth to the pool process is now way below 1ms. In theory this should decrease the uncle rate of the pool even further and at the same time also decrease the load we put on our geth instances.
  • MrYukonCMrYukonC Member Posts: 627 ✭✭✭
    @dr_pra Nice! Thanks for all the hard work.

    On another note -- I switched my entire farm back to QtMiner last night after using eth-proxy for the past week. So far, my average hashrate is about 5+ Mh/s higher (709 vs 704).

    It could just be coincidence or maybe push vs poll is just that much more efficient. I'll watch it for the next few days to see how it holds up.
  • dr_pradr_pra Member Posts: 445 ✭✭✭
    No, that is pure luck, the pool will not discard shares till a certain age as they can still be turned into uncles. Unlike bitcoin where a pool discards old work immediately.
  • SIRacer09SIRacer09 Member Posts: 246 ✭✭
    @MrYukonC Nice! I tried QtMiner a while back, but could never get the farm recheck switch to work. Maybe its not compatible, I don't know. Do you use that with QtMiner?
  • MrYukonCMrYukonC Member Posts: 627 ✭✭✭
    SIRacer09 said:

    @MrYukonC Nice! I tried QtMiner a while back, but could never get the farm recheck switch to work. Maybe its not compatible, I don't know. Do you use that with QtMiner?

    @SIRacer09 --farm-recheck is not applicable to QtMiner due to the way it implements its stratum connection.

    @dr_pra I figured it was probably just luck. ;)
Sign In or Register to comment.