Unable to get mining info from wallet & tried to fix Jminer
-
@ Luxe hello sorry to bother you with this. A few days ago I started getting the error message: b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet, repeatedly. The same version of Jminer 0.4.10 had previously worked fine.
I am using a GeForce GTX 660 Ti & Open CL is fine, reward recipient is set correctly (Blago miner is working).
I have read the other threads here on this problem and tried all suggested solutions, including: removing the port number from my pool server, removing the wallet server and trying other wallet servers, increasing the connection timeout - individually and altogether - all failed to remove the error. Have checked with pool owner that all OK his end. Here's my config file details at present:plotPaths=B/:Burst/Plots,C:/Burst/Plots,D:/Burst/Plots,F:/Burst/Plots,I:/Burst/Plots,J:/Burst/Plots,K:/Burst/Plots,L:/Burst/Plots
scanPathsEveryRound=
listPlotFiles=
poolMining=
numericAccountId=14242249402239300721
poolServer=http://burstneon.ddns.net:8124
walletServer=http://burstcoin.cc:8889
winnerRetriesOnAsync=
winnerRetryIntervalInMs=
soloServer=
passPhrase=
targetDeadline=
triggerServer=
recommitDeadlines=
platformId=
deviceId=
refreshInterval=
connectionTimeout=
debug=
writeLogFile=
logFilePath=
readProgressPerRound=
byteUnitDecimal=
showDriveInfo=
showSkippedDeadlines=
chunkPartNonces=Thanks for your help,
ATB, AtP
-
@ArthurThePug Try setting the connectionTimeout = 240000
-
This will probably not fix your problem, but the colon and your forward slash are reversed for your B:/ drive.
Also, poolMining should be "poolMining=true"
This also helped, for some reason:
optDevPool=false
Try:
refreshInterval=2000
connectionTimeout=75000This works for me. Keep increasing the connectionTimeout in 15000 increments. I know you've probably tried this, so if you have, please disregard.
Wait for the big dogs if this doesn't help. I'm still a noob.
Good luck!!
-
@vmantilla said in Unable to get mining info from wallet & tried to fix Jminer:
75000
Well I'll be damned that worked like a treat! I had already tried the refresh interval & connection timeout, so I'm assuming adding optDevPool=false was the trick.
Where did you find that golden nugget & any idea what it does?!
Many thanks,
ATB ATP
-
One of the mining gurus suggested it to me about 10 days ago. I now increase my connection timeout every time I see the error. In fact, I just increased it to 90000.
I'm glad you are up and running.
Cheers and make a lot of Burst!!
-
@vmantilla and well spotted on the B drive, just plotted that one
