The only way to use stratum/gbt is to connect through cgminer or similar correct? Can't use the bitminter GUI?
Yeah, BitMinter client uses getwork with rollntime. I will be adding Stratum and GBT later. |
|
|
|
EDIT: changed my miner version back to prior to stratum so I'm back to LP and it seems to work now so something is up with me and stratum at the moment... Can you clarify the port I'm supposed to use with bfgminer 2.9.4 or a specific cgminer version that might work better?
It's 3333 or 5050. So you can use --url stratum+tcp://mint.bitminter.com:3333 It looks like you have a gap where you were not mining from last night till this morning (euro time). Looks like you fell out around the time I did a pool server restart. I have heard of miners crashing when the pool disconnects them, although I think it's rare. It could also be that it stayed on a failover pool and didn't switch back? What exact problems or errors are you seeing when you use stratum? And was the miner crashed in this instance, or did you see anything else to explain why it wasn't mining? |
|
|
|
This information should be included on first post in topic, as you declare full support to Stratum and GBT - but nowhere we can find info how to connect to it, except single posts inside this huge topic.
You mean there are people who don't read every post in this thread? This is a bit of a shock.  Sorry, I forgot to add that - thanks  |
|
|
|
I am sitting here in NJ USA I have the same flu! Get well!
Thanks, you get well too. It's an annoying one. Anyone else having comm problems? Two of my miners keep crashing "pool 0 stratum submission failure".
M
I have been unable to log in. get transport error. when I use my open id. Since I use multiple pcs to run my video cards I happen to be logged into the site one 1 of the 9 pcs I have. all other pcs and a mac that is not a worker can't log in. It is fine for me in one sense since I can check my workers on the on pc. All 9 are running but if a work crashes I won't be able to sign it back in. I see in the website logs some communication errors with both Yahoo and Google spread out over a period of 1 hour. The last error was about 40 minutes ago, and both Yahoo and Google logins appear to be working now. Not sure what caused that - can't remember seeing any problems with Google or Yahoo before. About the Stratum errors, is that something that happens rarely? Every once in a while I see errors in the log about garbled data being submitted. Is there a more detailed error message? Are you saying the miner actually crashes when this happens and you have to restart it? |
|
|
|
Is there a way to force cgminer not to use var diff?
I prefer to mine at diff 1 as long as it possible....
You can use the --fix-protocol option to force getwork. It may be some more days before I turn on var diff for getwork. But in general, the diff is set by the server and the miner can't override it. I have found that during the recent pool outages that cgminer is not switching to backup pools. Bitminter is marked dead, then alive, but no work issued.
Any ideas before I raise this in the cgminer thread?
I guess this is because the pool wasn't down but horribly slow. Too slow should probably be considered down, for some definition of "too slow." I bet that will be a lot easier to fix after about another week passes. After all the 50 BTC per block rewards have scrolled off.
Then just set it to 25 BTC.
A lot of hassle not worth the effort, IMO, to have it deal with the 'switchover' event mid graph.
For the reward graph, I would like to add some buttons in the future to move forward and back in time, though. So I would like to have the 25/50 BTC change work in the graph. I tried to fix it but it's not quite working. A bit out of it with the flu at the moment, so not at regular programming speed. |
|
|
|
|
Thanks for testing. Must be something wrong there. Which operating system are you guys on?
|
|
|
|
Yeah, that one needs fixing. It's still using 50 BTC as expected income per block. |
|
|
|
Did you change the config? Wrong name/password maybe? NO Could you give it another try then? Mining is working. I just noticed someone is sending wrong credentials 10 times per second (standard with DiabloMiner). Remember after the user name to include an underscore and a worker name. |
|
|
|
Little Luke-Jr
This is how representatives of cgminer address other developers? No - as usual, you simply fall down to the level of name calling and show no intelligence at all.
I LOLed. |
|
|
|
Short question: is var diff enabled on default port, for GetWork miners?
Not yet. I'm waiting a bit with this so hashpower.com can get var diff support. We have a bunch of miners using their services and going var diff on getwork would break things as of now. Even though cgminer 2.9.7 indeed has very minimal rejects on BitMinter, should the vardiff code still be adjusted to avoid constantly changing difficulty? Have slightly different threshold levels for increasing/decreasing the difficulty, or use a longer time period for averaging shares per minute. I'm not sure if I correctly understood the information on cgminer's thread, but it seemed to indicate that changing difficulty has the potential for some lost work because of latency.
This was an issue with the way Stratum used to work. But changes were made and adjusting difficulty is no longer a problem. I see that my hashrate estimate has a lot more swings when mining on stratum. With higher difficulty shares, the averaging period should obviously be longer to get a meaningful estimate.
Yes, the higher difficulty makes the hashrate estimates less accurate. I'll have to look into that. Maybe a longer averaging period the higher your hashrate is. |
|
|
|
Did you change the config? Wrong name/password maybe? |
|
|
|
Pool having some issues. Working on it.
Everything up and running again. Sorry for the downtime.  namecoind crashed as usual, but something more went wrong causing very high cpu usage. I'm looking into it (logs, heap dump) to make sure it won't happen again. The high cpu usage was also the reason that the website was unstable. |
|
|
|
|
Pool having some issues. Working on it.
|
|
|
|
The Approximate Mint speed in btc/day is still wrong for me. Do I need to download a newer version?
The fix is only in a beta version so far. One user has reported a performance drop, so this hasn't been released as a stable version yet. There are some changes to reduce CPU usage for FPGA mining, so I want to be sure I didn't break something. Perhaps you can help test it: https://bitcointalk.org/index.php?topic=31163.msg1378210#msg1378210When do you anticipate being able to define other pools through the gui (as secondary or primary pools)?
When the different protocols (Stratum, GBT, etc) come online for prod, will you be able to choose in the gui as well as alter difficulty?
When do you anticipate these items being rolled out (if at all)?
Multi server and pool support will be coming. Most likely both GBT and Stratum too, which will be choosable in the GUI. I may make it possible to alter difficulty, perhaps setting it on the website. Haven't decided on this yet. I can't really say when things will be rolled out. As always, I will do my best to get the most important things out as quickly as possible. |
|
|
|
I seem to lose performance on my BFL Single with 1.3.1beta (around 70Mhps). Can't say about the CPU usage jumps to much to say (current version and beta)
Some other BFL users are getting the same speed with 1.3.1beta as they do with 1.3.0. Can you check this again? Is it constant at 70 Mhps lower than with v1.3.0? |
|
|
|
Actually, unless every pool that has been using LP since the beginning has been unable to support LP without sending out empty blocks, there is no excuse.
Faster long poll means less rejected work and fewer stale/orphan blocks, that's why. |
|
|
|
I was thinking, why aren't pool operators announcing LP is being retired and force ppl to upgrade? Even GBT is better than LP.
The protocol is getwork. Both GBT and getwork use long polling (LP) to detect block changes. With getwork the server has to generate work for the miners, while with GBT or Stratum the miners generate their own work. Long polling is much faster for getwork miners if you can generate the work beforehand, which is possible with empty blocks. With a few tricks like that, plus var diff and rollntime, getwork is still useable, even for ASICs. I'm not saying it's the best choice, though.  |
|
|
|
BitMinter client should run well on 7970 - give it a try bitminter.com |
|
|
|
Can you explain it, please? What is so wrong with old versions?
Old cgminer/bfgminer have a bug that suddenly make them request work from the server over and over as fast as they can. This amounts to a DDoS attack which can be quite heavy for the server. Giving those miners work that is as cheap as possible to produce is one of the many changes I made to keep things running smoothly even with those miners sometimes going nuts. That's mean dynasty have old, obsolete cgminer version and that's why we generated empty, useless block?
Maybe. Long poll is also feeding miners empty blocks, so that could also be the reason. But those are not allowed to rollntime, so we are talking a very small amount of work. The chance to produce a block from this is very low. Why use empty blocks for long poll? Because you can produce this work already before the block change. This way all miners are informed of the block change very quickly, which results in less rejected work. |
|
|
|
BitMinter client v1.3.1beta is ready for testing. Small update this time. Please let me know whether FPGA mining still runs well (BFL and Icarus). If you have the time it would also be interesting to hear if CPU usage is lower than with v1.3.0, especially with BFL FPGAs. New since 1.3.0: - Adjust 'BTC per day' display according to reward halving
- Reduced CPU usage for FPGA mining
- Recognize GTX 670 and 680 GPUs
Please check it out:  |
|
|
|
|
Show Posts
