SOCKET ERROR - CALL error

Chakthi commented 6 years ago

Every time I start the program, I get this error until a "Result accepted by the pool" message (eventually) pops up. I have tried everything I can think of. I've changed the timeout to 15 seconds up to 6 minutes without it making any difference at all. I've shut down all anti-virus and firewall software, and tried it on multiple machines, even downloaded previous versions of the software to see if I can pinpoint the problem, but all to no avail. Once I get the message that a result was accepted, it runs flawlessly forever after, until the next time I start the software, and then I start the agonizing process over again. Does anyone have any suggestions for how to fix this problem? Has anyone else had this problem, or is it just me? I've searched on Reddit, Google, and Github, but can't even find a mention of it... :(

CONNECTION REPORT Pool address : xmr.pool.minergate.com:45560 Connected since : 2017-11-13 12:57:31 Pool ping time : 137 ms

Network error log: | Date | Error text | | 2017-11-13 12:48:32 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:49:01 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:49:22 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:49:41 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:50:14 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:51:07 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:51:36 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:52:16 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:52:37 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:53:04 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:54:23 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:54:59 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:55:20 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:55:45 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:56:15 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:56:40 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:57:00 | CALL error: Timeout while waiting for a reply | | 2017-11-13 12:57:28 | CALL error: Timeout while waiting for a reply |

psychocrypt commented 6 years ago

We released a new version of the miner: https://github.com/fireice-uk/xmr-stak Please check if the issue still exists with the new version. If the problem is not fixed so far please open a new issue in the issue section of the new reposetory

marcopineschi commented 6 years ago

Same problem here:

"pool_address" : "xmr.pool.minergate.com:45560",

LOG:
ubuntu@min-az-2:~/xmr-stak-cpu/bin$ ./xmr-stak-cpu
[2017-11-19 23:35:33] : MEMORY ALLOC FAILED: mlock failed
[2017-11-19 23:35:33] : MEMORY ALLOC FAILED: mlock failed
-------------------------------------------------------------------
xmr-stak-cpu 1.3.0-1.5.0 mining software, CPU Version.
Based on CPU mining code by wolf9466 (heavily optimized by fireice_uk).
Brought to you by fireice_uk and psychocrypt under GPLv3.

Configurable dev donation level is set to 2.0 %

You can use following keys to display reports:
'h' - hashrate
'r' - results
'c' - connection
-------------------------------------------------------------------
[2017-11-19 23:35:33] : Starting double thread, affinity: 0.
[2017-11-19 23:35:33] : Starting double thread, affinity: 1.
[2017-11-19 23:35:33] : Starting double thread, affinity: 2.
[2017-11-19 23:35:33] : Starting double thread, affinity: 3.
[2017-11-19 23:35:33] : Connecting to pool xmr.pool.minergate.com:45560 ...
[2017-11-19 23:35:33] : hwloc: memory pinned
[2017-11-19 23:35:33] : hwloc: memory pinned
[2017-11-19 23:35:33] : hwloc: memory pinned
[2017-11-19 23:35:33] : MEMORY ALLOC FAILED: mlock failed
[2017-11-19 23:35:33] : MEMORY ALLOC FAILED: mlock failed
[2017-11-19 23:35:33] : MEMORY ALLOC FAILED: mlock failed
[2017-11-19 23:35:33] : MEMORY ALLOC FAILED: mlock failed
[2017-11-19 23:35:33] : MEMORY ALLOC FAILED: mlock failed
[2017-11-19 23:35:33] : hwloc: memory pinned
[2017-11-19 23:35:33] : MEMORY ALLOC FAILED: mlock failed
[2017-11-19 23:35:33] : MEMORY ALLOC FAILED: mlock failed
[2017-11-19 23:35:33] : MEMORY ALLOC FAILED: mlock failed
[2017-11-19 23:35:34] : Connected. Logging in...
[2017-11-19 23:35:34] : Difficulty changed. Now: 1063.
[2017-11-19 23:35:34] : New block detected.
[2017-11-19 23:35:46] : SOCKET ERROR - CALL error: Timeout while waiting for a reply
[2017-11-19 23:35:46] : Pool connection lost. Waiting 10 s before retry (attempt 1).
[2017-11-19 23:35:55] : Connecting to pool xmr.pool.minergate.com:45560 ...
[2017-11-19 23:35:56] : Connected. Logging in...

psychocrypt commented 6 years ago

https://github.com/fireice-uk/xmr-stak

ghost commented 6 years ago

The problem still happen with the last version:

xmr-stak 2.0.0 79154f7

Brought to you by fireice_uk and psychocrypt under GPLv3.
Based on CPU mining code by wolf9466 (heavily optimized by fireice_uk).
Based on NVIDIA mining code by KlausT and psychocrypt.
Based on OpenCL mining code by wolf9466.

Configurable dev donation level is set to 2.0%

You can use following keys to display reports:
'h' - hashrate
'r' - results
'c' - connection
-------------------------------------------------------------------
[2017-11-22 19:48:46] : Start mining: MONERO
[2017-11-22 19:48:46] : Starting NVIDIA GPU thread 0, no affinity.
[2017-11-22 19:48:46] : Starting single thread, affinity: 0.
[2017-11-22 19:48:46] : hwloc: memory pinned
[2017-11-22 19:48:46] : Starting single thread, affinity: 2.
[2017-11-22 19:48:46] : hwloc: memory pinned
[2017-11-22 19:48:46] : Starting single thread, affinity: 4.
[2017-11-22 19:48:46] : hwloc: memory pinned
[2017-11-22 19:48:46] : Starting single thread, affinity: 1.
[2017-11-22 19:48:46] : hwloc: memory pinned
[2017-11-22 19:48:46] : Starting single thread, affinity: 6.
[2017-11-22 19:48:46] : hwloc: memory pinned
[2017-11-22 19:48:46] : Starting single thread, affinity: 8.
[2017-11-22 19:48:46] : hwloc: memory pinned
[2017-11-22 19:48:46] : Starting single thread, affinity: 10.
[2017-11-22 19:48:46] : hwloc: memory pinned
[2017-11-22 19:48:46] : Starting single thread, affinity: 7.
[2017-11-22 19:48:46] : hwloc: memory pinned
[2017-11-22 19:48:46] : Fast-connecting to stratum+tcp://xdn-xmr.pool.minergate.com:45790 pool ...
[2017-11-22 19:48:46] : Pool stratum+tcp://xdn-xmr.pool.minergate.com:45790 connected. Logging in...
[2017-11-22 19:48:46] : Difficulty changed. Now: 1063.
[2017-11-22 19:48:46] : Pool logged in.
[2017-11-22 19:49:02] : All pools are dead. Idling...
[2017-11-22 19:49:03] : Difficulty changed. Now: 1111.
[2017-11-22 19:49:03] : Pool logged in.
[2017-11-22 19:49:03] : All pools are dead. Idling...
[2017-11-22 19:49:03] : SOCKET ERROR - [stratum+tcp://xdn-xmr.pool.minergate.com:45790] CALL error: Timeout while waiting for a reply

Chakthi commented 6 years ago

For me, the problem is fixed. Sorry to hear you are still having trouble though...

Sent from eM Client | www.emclient.com http://www.emclient.com/get

------ Original Message ------ From: "paulotwo" notifications@github.com To: "fireice-uk/xmr-stak-cpu" xmr-stak-cpu@noreply.github.com Cc: "Chakthi" armistead.1863@gmail.com; "Author" author@noreply.github.com Sent: 11/22/2017 4:53:55 PM Subject: Re: [fireice-uk/xmr-stak-cpu] SOCKET ERROR - CALL error (#413)

The problem still happen with the last version:

xmr-stak 2.0.0 79154f7

Brought to you by fireice_uk and psychocrypt under GPLv3. Based on CPU mining code by wolf9466 (heavily optimized by fireice_uk). Based on NVIDIA mining code by KlausT and psychocrypt. Based on OpenCL mining code by wolf9466.

Configurable dev donation level is set to 0.0%

You can use following keys to display reports: 'h' - hashrate 'r' - results 'c' - connection

[2017-11-22 19:48:46] : Start mining: MONERO [2017-11-22 19:48:46] : Starting NVIDIA GPU thread 0, no affinity. [2017-11-22 19:48:46] : Starting single thread, affinity: 0. [2017-11-22 19:48:46] : hwloc: memory pinned [2017-11-22 19:48:46] : Starting single thread, affinity: 2. [2017-11-22 19:48:46] : hwloc: memory pinned [2017-11-22 19:48:46] : Starting single thread, affinity: 4. [2017-11-22 19:48:46] : hwloc: memory pinned [2017-11-22 19:48:46] : Starting single thread, affinity: 1. [2017-11-22 19:48:46] : hwloc: memory pinned [2017-11-22 19:48:46] : Starting single thread, affinity: 6. [2017-11-22 19:48:46] : hwloc: memory pinned [2017-11-22 19:48:46] : Starting single thread, affinity: 8. [2017-11-22 19:48:46] : hwloc: memory pinned [2017-11-22 19:48:46] : Starting single thread, affinity: 10. [2017-11-22 19:48:46] : hwloc: memory pinned [2017-11-22 19:48:46] : Starting single thread, affinity: 7. [2017-11-22 19:48:46] : hwloc: memory pinned [2017-11-22 19:48:46] : Fast-connecting to stratum+tcp://xdn-xmr.pool.minergate.com:45790 pool ... [2017-11-22 19:48:46] : Pool stratum+tcp://xdn-xmr.pool.minergate.com:45790 connected. Logging in... [2017-11-22 19:48:46] : Difficulty changed. Now: 1063. [2017-11-22 19:48:46] : Pool logged in. [2017-11-22 19:49:02] : All pools are dead. Idling... [2017-11-22 19:49:03] : Difficulty changed. Now: 1111. [2017-11-22 19:49:03] : Pool logged in. [2017-11-22 19:49:03] : All pools are dead. Idling... [2017-11-22 19:49:03] : SOCKET ERROR - [stratum+tcp://xdn-xmr.pool.minergate.com:45790] CALL error: Timeout while waiting for a reply

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/fireice-uk/xmr-stak-cpu/issues/413#issuecomment-346483231, or mute the thread https://github.com/notifications/unsubscribe-auth/AgDuZN3GvPZjEZLBgPh86GuPsnWEXOGPks5s5JfzgaJpZM4QcMHk.

This email has been checked for viruses by AVG. http://www.avg.com

ghost commented 6 years ago

Only happens with this address:"stratum+tcp://xdn-xmr.pool.minergate.com:45790" The address "stratum+tcp://xmr.pool.minergate.com:45560" works fine.

A more detail log:

-------------------------------------------------------------------
xmr-stak 2.0.0 79154f7

Brought to you by fireice_uk and psychocrypt under GPLv3.
Based on CPU mining code by wolf9466 (heavily optimized by fireice_uk).
Based on NVIDIA mining code by KlausT and psychocrypt.
Based on OpenCL mining code by wolf9466.

Configurable dev donation level is set to 2.0%

You can use following keys to display reports:
'h' - hashrate
'r' - results
'c' - connection
-------------------------------------------------------------------
[2017-11-23 14:44:03] : Start mining: MONERO
[2017-11-23 14:44:03] : Starting single thread, affinity: 0.
[2017-11-23 14:44:03] : hwloc: memory pinned
[2017-11-23 14:44:03] : Starting single thread, affinity: 2.
[2017-11-23 14:44:03] : hwloc: memory pinned
[2017-11-23 14:44:03] : Starting single thread, affinity: 4.
[2017-11-23 14:44:03] : hwloc: memory pinned
[2017-11-23 14:44:03] : Starting single thread, affinity: 1.
[2017-11-23 14:44:03] : hwloc: memory pinned
[2017-11-23 14:44:03] : Starting single thread, affinity: 6.
[2017-11-23 14:44:03] : hwloc: memory pinned
[2017-11-23 14:44:03] : Starting single thread, affinity: 8.
[2017-11-23 14:44:03] : hwloc: memory pinned
[2017-11-23 14:44:03] : Starting single thread, affinity: 10.
[2017-11-23 14:44:03] : hwloc: memory pinned
[2017-11-23 14:44:03] : Starting single thread, affinity: 7.
[2017-11-23 14:44:03] : hwloc: memory pinned
[2017-11-23 14:44:03] : Fast-connecting to stratum+tcp://xdn-xmr.pool.minergate.com:45790 pool ...
[2017-11-23 14:44:03] : Pool stratum+tcp://xdn-xmr.pool.minergate.com:45790 connected. Logging in...
SEND: {"method":"login","params":{"login":"XXX","pass":"x","agent":"xmr-stak/2.0.0/79154f7/unknown/win/nvidia-amd-cpu/aeon-monero/0"},"id":1}

[2017-11-23 14:44:03] : Difficulty changed. Now: 1063.
[2017-11-23 14:44:03] : Pool logged in.
SEND: {"method":"submit","params":{"id":"8a920379-be83-4d8f-a787-a5b1280d437c","job_id":"994132e9-4985-455e-84ba-2d033e3c199e","nonce":"1c100000","result":"e89f4b60d8e8840da24e93d1ed7fb074259b88d1fea0e2b4e129f60dd5be2200"},"id":1}

[2017-11-23 14:44:24] : All pools are dead. Idling...
[2017-11-23 14:44:24] : SOCKET ERROR - [stratum+tcp://xdn-xmr.pool.minergate.com:45790] CALL error: Timeout while waiting for a reply
[2017-11-23 14:44:33] : Fast-connecting to stratum+tcp://xdn-xmr.pool.minergate.com:45790 pool ...
[2017-11-23 14:44:33] : Pool stratum+tcp://xdn-xmr.pool.minergate.com:45790 connected. Logging in...
SEND: {"method":"login","params":{"login":"XXX","pass":"x","agent":"xmr-stak/2.0.0/79154f7/unknown/win/nvidia-amd-cpu/aeon-monero/0"},"id":1}

[2017-11-23 14:44:35] : Difficulty changed. Now: 1063.
[2017-11-23 14:44:35] : Pool logged in.
SEND: {"method":"submit","params":{"id":"9c842c57-cbd0-47ef-9d9b-bed9cbe5a681","job_id":"a1f3ff38-1c7d-4e60-9f2d-27451db3cbcb","nonce":"05510000","result":"2494dbf787d673fb074a700056cf58c7ac5f85fae707607724fb1b84ac863a00"},"id":1}

psychocrypt commented 6 years ago

use only xdn-xmr.pool.minergate.com:45790

ghost commented 6 years ago

I am already using only one pool. The "xdn.pool.minergate.com:45620" only works at the first execute, on the second execution I get the same error. One time the "xdn-xmr.pool.minergate.com:45790" works after a reboot on PC, but now do not works anymore. I made some test with anothers URLs (xdn, bcn) and all give the same comportament, they works on the first execution, but if I close the app and start again they stop works. The error is always the same, xmr-stak connect, logon and give me a timeout when "submit" command is sended.

ghost commented 6 years ago

I've found the problem, sometimes, usually starting from the second connection, the minergate simply does not respond to the "submit" command. I make a small proxy program and compared xmr-stak's communication with another miner.

This is xmr-stak:

Client: {"method":"login","params":{"login":"XXX","pass":"x","agent":"xmr-stak/2.0.0/79154f7/unknown/win/nvidia-amd-cpu/aeon-monero/0"},"id":1}
Server: {"jsonrpc":"2.0","result":{"job":{"blob":"0606d584e2d005b9d9d6c590bb174dd5c2f0b67c2d005575de8292569732b9a536816ef7e2122200000000f71b3b9929ff6db13cbd506e0cda9a6e7c610010efd9d526fceb1d722ec20b920b","target":"e4a63d00","job_id":"21530fca-b0e2-44ca-a1de-1648e79837e9","time_to_live":5},"status":"OK","id":"f772f37c-ef4e-4600-815e-e20178849726"},"id":1,"error":null}
Server: {"jsonrpc":"2.0","method":"job","params":{"blob":"0606d584e2d005b9d9d6c590bb174dd5c2f0b67c2d005575de8292569732b9a536816ef7e21222000000001c04425c450011482b130b6302b284364f1e9af22517382e151cd6d2e35f7d7a0b","target":"e4a63d00","job_id":"947a9a5d-336d-4b73-880e-434908f596eb","time_to_live":5},"error":null}
Server: {"jsonrpc":"2.0","method":"job","params":{"blob":"0606d584e2d005b9d9d6c590bb174dd5c2f0b67c2d005575de8292569732b9a536816ef7e2122200000000face70577ffafe6afa187555bb2757f884b38e451aaac43c90f8e8dc61447c600b","target":"e4a63d00","job_id":"cc08852d-67e8-4df2-aa1e-42e03773a608","time_to_live":5},"error":null}
Client: {"method":"submit","params":{"id":"f772f37c-ef4e-4600-815e-e20178849726","job_id":"cc08852d-67e8-4df2-aa1e-42e03773a608","nonce":"6a010000","result":"74bd3d6ddfc1a23622c10a50e3395344f334b45c19e1f58b9a4fa277d0f72f00"},"id":1}
java.net.SocketException: Connection reset by peer: socket write error

And this is another miner:

Client: {"method": "login", "params": {"login": "XXX", "pass": "x", "agent": "xmr/1.0"}, "id": 1}
Server: {"jsonrpc":"2.0","result":{"job":{"blob":"0606b2ffe1d0052e86b30c3736d4e39613a88d8d2172670d383adcae294c09be52e41b6bbd4fbb00000000983fa1aeb4ba43dcf2f0c093b0184bd3aa09ad0958418beac157a1675e60fac302","target":"e4a63d00","job_id":"ece02418-a301-4957-92bd-58d79133522d","time_to_live":5},"status":"OK","id":"007a5656-4edd-4564-8859-65dc44823ea2"},"id":1,"error":null}
Server: {"jsonrpc":"2.0","method":"job","params":{"blob":"0606b2ffe1d0052e86b30c3736d4e39613a88d8d2172670d383adcae294c09be52e41b6bbd4fbb00000000f17234679655a5f7c5810f7879dcc83249ad24440d7ddbf02ae836332b67154102","target":"e4a63d00","job_id":"3c9c2a1c-99f6-4b3d-b185-8db5e4f95b9f","time_to_live":5},"error":null}
Client: {"method": "submit", "params": {"id": "007a5656-4edd-4564-8859-65dc44823ea2", "job_id": "3c9c2a1c-99f6-4b3d-b185-8db5e4f95b9f", "nonce": "f2010000", "result": "b7bbc7b99a8fb76f31365c7104caf03fa38bbf501a55bb998b1477da70973800"}, "id":4}
Client: {"method": "submit", "params": {"id": "007a5656-4edd-4564-8859-65dc44823ea2", "job_id": "3c9c2a1c-99f6-4b3d-b185-8db5e4f95b9f", "nonce": "14040000", "result": "9095c3d290464328c846dc91921445e20ff6162856402720c2bc19401d8c1d00"}, "id":4}
Server: {"jsonrpc":"2.0","result":{"status":"OK"},"id":4,"error":null}
Client: {"method": "submit", "params": {"id": "007a5656-4edd-4564-8859-65dc44823ea2", "job_id": "3c9c2a1c-99f6-4b3d-b185-8db5e4f95b9f", "nonce": "f8040000", "result": "c198009ed65aabfeb529b31b8e34885858cb24f304684a8a91874bb9fb003600"}, "id":4}
Server: {"jsonrpc":"2.0","result":{"status":"OK"},"id":4,"error":null}

As you can see, the second miner ignores the server's lack of response and continues to communicate, being able to receive a response to the next commands.

I make this change in jpsock.cpp

bool jpsock::cmd_ret_wait(const char* sPacket, opq_json_val& poResult)
{
    return cmd_ret_wait(sPacket, poResult, 1);
}

bool jpsock::cmd_ret_wait(const char* sPacket, opq_json_val& poResult, int attempt)
{
    //printf("SEND: %s\n", sPacket);

    /*Set up the call rsp for the call reply*/
    prv->oCallValue.SetNull();
    prv->callAllocator.Clear();

    std::unique_lock<std::mutex> mlock(call_mutex);
    prv->oCallRsp = call_rsp(&prv->oCallValue);
    mlock.unlock();

    if(!sck->send(sPacket))
    {
        disconnect(); //This will join the other thread;
        return false;
    }

    //Success is true if the server approves, result is true if there was no socket error
    bool bSuccess;
    mlock.lock();
    bool bResult = call_cond.wait_for(mlock, std::chrono::seconds(jconf::inst()->GetCallTimeout()),
        [&]() { return prv->oCallRsp.bHaveResponse; });

    bSuccess = prv->oCallRsp.pCallData != nullptr;
    prv->oCallRsp.pCallData = nullptr;
    mlock.unlock();

    if(bHaveSocketError)
        return false;

    //This means that there was no socket error, but the server is not taking to us
    if(!bResult)
    {
        if (attempt > 1)
        {
            set_socket_error("CALL error: Timeout while waiting for a reply");
            disconnect();
            return false;
        } else {
            //TODO log a warning
            return cmd_ret_wait(sPacket, poResult, attempt++);
        }
    }

    if(bSuccess)
        poResult.val = &prv->oCallValue;

    return bSuccess;
}

What I did was try to send the command a second time if the first attempt fails. So the result was this:

Client: {"method":"login","params":{"login":"XXX","pass":"x","agent":"xmr-stak/2.0.0/79154f7/unknown/win/nvidia-amd-cpu/aeon-monero/0"},"id":1}
Server: {"jsonrpc":"2.0","result":{"job":{"blob":"0606a896e2d00551f783c2db5579a6542128c0a12d0555b80680326dff8876bb8076c24a2dfff7000000008077090ea4d412fa9786167c5c03e8c2573699fe697417b1453ec96e35c9558804","target":"e4a63d00","job_id":"20a7c337-0454-4911-bab6-e3c2b19a3013","time_to_live":5},"status":"OK","id":"94c6d5de-19aa-49cb-8f64-7b64c44f2664"},"id":1,"error":null}
Client: {"method":"submit","params":{"id":"94c6d5de-19aa-49cb-8f64-7b64c44f2664","job_id":"20a7c337-0454-4911-bab6-e3c2b19a3013","nonce":"10000000","result":"4edce47189e78470015227fd2a5759e9abd4b30d8ea310d681188912c43d2a00"},"id":1}
Client: {"method":"submit","params":{"id":"94c6d5de-19aa-49cb-8f64-7b64c44f2664","job_id":"20a7c337-0454-4911-bab6-e3c2b19a3013","nonce":"10000000","result":"4edce47189e78470015227fd2a5759e9abd4b30d8ea310d681188912c43d2a00"},"id":1}
Server: {"jsonrpc":"2.0","error":{"code":-22,"message":"Duplicate share."},"id":1,"result":null}
Client: {"method":"submit","params":{"id":"94c6d5de-19aa-49cb-8f64-7b64c44f2664","job_id":"20a7c337-0454-4911-bab6-e3c2b19a3013","nonce":"3f070000","result":"8b1205f01807129977bbc51e43d91ad7e8c0e48fd1a68c74d50a069fdf0a2a00"},"id":1}
Server: {"jsonrpc":"2.0","result":{"status":"OK"},"id":1,"error":null}
Client: {"method":"submit","params":{"id":"94c6d5de-19aa-49cb-8f64-7b64c44f2664","job_id":"20a7c337-0454-4911-bab6-e3c2b19a3013","nonce":"d70f0000","result":"2fe03f02dd09b6a09d2c65911573951d12720bdfc40753f14ea50474ad012600"},"id":1}
Server: {"jsonrpc":"2.0","result":{"status":"OK"},"id":1,"error":null}

As you can see, on the second attempt the server responds that the share is duplicated, which means that the server received and processed the first command, just did not send the response it should. At log xmr-stak says the first share was rejected, but at least after that it works and the next shares are accepted successfully. I would like you to add this fix to github sources, or provide a more elegant solution to this problem.

psychocrypt commented 6 years ago

Thank you for checking where the problem is comming from. The problem is that we can not fix it. It is an bug on the pool side.Your workaround is working but the statistiks will be wrong and a sideeffect is that othe well communicating pools will be handed wrong.

Never the less I cc-ing @fireice_uk