burstcoin-jminer v0.4.10 - GPU assisted PoC-Miner (All Platforms)
-
@GabryRox Not sure why you're getting the message - if you look just before it occurred you had a DL confirmed, so you're communicating with the pool normally.
-
@haitch oh yeah wow! i didnt even see that before you mentioned it. Seems very strange as it should be all or nothing right? Wierd that it would read and connect and get a dl but then right away start that error message. Really wish i could get this working since it looks like it was reading about 6-7x faster than my Blago CPU AVX2.
-
@GabryRox Watch your miner and the pool, if your miner starts mining at the same time the pool rolls onto a new block, and you get confirmed DL's, then it's working properly.
-
@haitch yeah, no matter what i do i can only get it to run for a few blocks max... maybe has 1-2 confirmed dl max but then starts up with just repeating that error and won't continue to mine.
I even tried launching Jminer through the AIO interface since i know that works from CPU mining through there... but even that gets the same error after a 1 or very few blocks.
I will try setting this up on my other PC and see what happens as this is really baffling me.
-
well, it didnt work on my other PC either, so I dont know what the issue is but i am pretty much done with this for today :(
I thought i was onto something when I saw in the readme that the walletServer should actually be 'wallet.burst-team.us:8125', not the 'pool.burst-team.us:8124' that i had been using, but alas, that didn't work either.
So, is it correct that the pool server should be port 8124 and wallet server 8125? or does it matter? I think I have tried most combinations for both of these fields but nothing seems to work.
If I thought that changing my pool back to burst-team.us would help, i would try it but that doesn't seem like it would affect the problem I am having.
Anyway, if anyone can think of something to try please let me know.
-
@GabryRox no, for the pool, URL http://pool.burst-team.us port 8124
-
@luxe could you add a "recommitDeadlines" option for pool mining as well? With its own timeout setting perhaps? I believe Blago's miner has something like that as well.
I'm new to Burst and I started mining on Lexitoshi's pool this weekend and I get lots of timeouts (while set to 30 secs) on that pool when submitting deadlines (and even successful confirmations take 15-20 secs). I haven't seen anything like it on the other 2 pools that I tried so far so I hope they'll get it together but recommitting DL's could always be useful I think.
So instead of waiting 30 secs for a timeout I would rather see jminer try committing again after 5 seconds or something (when no confirmation was received), especially with low deadlines.
-
@haitch said in burstcoin-jminer v0.4.10 - GPU assisted PoC-Miner (All Platforms):
@GabryRox no, for the pool, URL http://pool.burst-team.us port 8124
@haitch but I am using burstcoin.biz as my pool, so shouldn't their address be linked in my poolserver spot? man, this stuff is so much more confusing than GPU mining lol
-
@GabryRox In your earlier post you referenced pool.burst-team.us: "I thought i was onto something when I saw in the readme that the walletServer should actually be 'wallet.burst-team.us:8125', not the 'pool.burst-team.us:8124' that i had been using, but alas, that didn't work either."
If you're using pool.burstcoin.biz instead, just use pool.burstcoin.biz:8124
-
@jant90 For solo mining the idea of a recommit was to ensure a result gets propagated, in case of a pool, the pool has the responsibility for that. However, you are right ... miner should ensure a deadline reaches the pool. I will keep that in mind and maybe add a solution in a future version.
-
@GabryRox You should not use https for walletServer, seams to make problems ... the best would be using local wallet for it like:
walletServer=http://localhost:8125If that is not possible whyever, find a non https wallet on burstcoin.cc that you could use. e.g.
walletServer=http://wallet2.burstcoin.sk:8126
-
I've done some quick modification in order to resubmit deadlines. So i have to say, on lex pool it is worth it.
This is from my DailyJMinerDigestMail:Today we found 2872 DLs
Today we commited 1956 DLs
Today we successfully resubmitted 977 DLs
Today we lost 916 DLs on connections faults
-
@Zaziki You should share your miner improvements, maybe you find time to publish it or make merge request on github :-)
In your stats you should only count lowest deadlines maybe ... a high deadline that does not get commited is not relevant, if a lower gets committed after it.
-
@Zaziki Yeah I've seen many (for me) great deadlines that never got confirmed, really frustrating! Could you please share your jminer improvements? Even if it's just the resubmit part (as apparently you also wrote a mailer function).
How do I read those stats btw? Because thanks to your resubmission function you didn't loose all those 916 DL's I assume?
And do you also take into account never to resubmit a higher deadline? I believe there's a penalty on that in Lex's pool.
-
@luxe i only count commitable deadlines, not queued ones. It was more a network quality information as a performance value since i use a broadband connection.
@jant90 i did not loose that 916, thats right. It was never that bad before, this night i only recovered 14. So it is not a substainable value. I only resubmit deadlines which are better than the best confirmed one.
I will publish my modifications when, for now not sure how.
-
Couple of questions since I'm new to jminer...
- In some of the screenshots above, I see it listed out read speeds per drive letter. Whereas my jminer just shows a % of the total drives/plots and the current amount of TB that it's read. Is there something in the config that has to be changed to show read speeds per drive, instead of per % of total drives?
EDIT: I just answered this one for myself... totally overlooked the "showDriveInfo" property multiple times
-
Is there a way to make the miner not output the info in the 2nd column? This info seems like it's more for Dev stuff, as it doesn't have any useful information (at least for me):
-
Can the miner list out what drive/plot found a deadline?
-
When a deadline is found, the miner just lists out the total seconds for the deadline until the pool replies back with a confirmation, then it converts it to days/minutes/seconds. Is there any way to configure it so that it shows the days/minutes/seconds by default?
-
Is there a way to remotely monitor the miner? So, that if the miner stops mining for some reason or another, that it can be automatically restarted or for grabbing external mining stats?
Thanks in advance!
