-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSON decode failed: "The document root must not be followed by other values." #123
Comments
@xmrig |
Can you recompile miner with one small change? Uncomment this line https://github.com/xmrig/xmrig/blob/master/CMakeLists.txt#L154 |
@xmrig for another question I want to ask is from what Iunderstand when I use proxy, the hash rate will be not accurate, but in a long time, it is the same...So I just need set the difficulty in the proxy like xxxx.xxxx.xxxx.xxxx:port(the port i use is high difficulty to make sure the share is sent beyond 30 seconds to pool), then let all the miner connect to it and that's all... However, I noticed that "rejected (222/16) diff 14178 "Low difficulty share" (26 ms)", what could be the issue for this? |
Hi again, two errors: [2018-03-05 07:32:13] new job from orayddns.iok.la:12145 diff 165483 [2018-03-05 07:35:16] [MY PROXY IPADDRESS: MY PROXY OUTSITE PORT] received (64 bytes): "{"id":11,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}" |
I observer my windows PC, and I see two more error: JSON decode failed: "Miss exponent in number." hmmm, will it affect the mining work? looks like it is something like config file need to be more accurate or clean? |
About JSON errors, something wrong, you received only partial data, for TCP it's one packet can split to multiple parts or multiple packets glue together, but parser should make whole packet anyway and I was test any possible combination. I point one miner to your proxy and see same errors, need check it closer. What is internet connection on your proxy? |
I confirm it's a bug (regression) on miner side. Working on fix now. |
Fixed, all versions since 2.4.0 was affected, usually responses from pool/proxy fit to one TCP packet and this issue not appear. |
@xmrig How can I fix it? maybe I need rebuild it from the fixed source? By the way, how can I solve the "Low difficulty share is generic pool error message, means something wrong with share."? |
You need rebuild miners, I pushed changes to each repo also it affect proxy too, but I update only dev branch.
Can be many reasons, something wrong with share, with pool or pool not accept expired shares (most of pool accept it). |
@xmrig by the way, will it affect the mining ? if so, it's better to patch it I think.. |
@xmrig |
what?! |
I try to use proxy now...
I monitor the miner,it from time to time to show something like below:
[MY PROXY IPADDRESS: MY PROXY OUTSITE PORT] JSON decode failed: "The document root must not be followed by other values."
and other miner give:
[MY PROXY IPADDRESS: MY PROXY OUTSITE PORT] JSON decode failed: "Invalid value."
what does this mean?
config is:
{
"algo": "cryptonight",
"background": false,
"colors": true,
"retries": 5,
"retry-pause": 5,
"donate-level": 1,
"syslog": false,
"log-file": null,
"print-time": 60,
"av": 0,
"safe": false,
"max-cpu-usage": 100,
"cpu-priority": 5,
"threads": null,
"threads": 12,
"pools": [
{
"url": "MY PROXY IPADDRESS: MY PROXY OUTSITE PORT",
"user": "HELLO MONEY",
"pass": "MONEY",
"keepalive": true,
"nicehash": false
}
],
"api": {
"port": 0,
"access-token": null,
"worker-id": null
}
}
The text was updated successfully, but these errors were encountered: