Topic: [Minera v0.9.0] Your next mining dashboard - S9/L3+/D3/CPUminer/CGminer/BFGminer - page 145. (Read 850463 times)

Not sure if you found a fix for this, but if you haven't put http://[MRRStuff] as your pool. Start minera, view the logs for "something like 'stratum at ___- requested reconnect to ____:5####" and switch the 3333 with the 5 number you just found.

Thank you michelem.

Also sending you screenshot so you can see how the Blades are moving through the whole list .. Will also send you log from this Rasp to your mail address.

Love the program for pool mining, but because it inserts http: in front of the pool name you can't use it for solo mining.  Stuck hooking up the laptop and using cgminer.  Other thing, using cgminer I get a lot less HW errors then with Minera.

Still love the program though...

Thank you all for your feedbacks. Well, I think the better solution is adding the ability to remove the donation pool, at least until I can find what causes this problem.

But I have to add the ability to re-add it too or at least to add it if you select the time donation, I'll update you soon about this.

I Agree Ajeto.

We all know that your Minera software right now, stands above everyone else, but because of this your are forcing a donation pool on a lot of people and if it continues, you will lose the support of those people that ARE donating to you cause they are getting pissed off about this. ( just look at Ginero who is now only known as a scammer and a douchebag ) but LSB and RRTFON are known as gods.

just put a check box of on or off for the donation pool, this way people who want to donate will and those who don't will still praise your Frontend and keep spreading the good word to other miners and i'm shure you will come on top this way, like many others i donated at the beginning to you and sandors and right now i'm not interered in donating more at the moment, but with this donation pool "problem" i'm very close to pluggin that cable to my windows PC.

just my to cents worth but i think a lot of people are thinking the same thing.

Minera Rocks BTW THAT there is no denying it

I am afraid that is not such a good idea. For example I have 6 pools listed and when i see a better profitability on pool3 I switch all RPis to it. If those pools will automatically switch back to pool0 that is not ok.

I also think that having Nicehash in pool list is not the reason why these changes happen.

I still think that donaton pool, that can be removed by those, who have problems with it, is the best fast solution. 

That has to be the default behavior, not the other way around. Minera has to mine in our chosen pools and not in any system enforced pool.


Nicehash’s price variation is indeed a reason for multiple disconnects but I accidentally mined to the donation pool for several hours without having Nicehash in my selection at the moment. Therefore, Nicehash is not the one to blame. In reality, all pools experience some kind of failure, network instability, hash rate fluctuations, rejection peaks, etc. The goal of having multiple pools is exactly to have a contingency plan in the event of any failure in the main pool.

But the key fact remains: Donation has to be voluntary, by definition! If a donation is somehow enforced or mandatory, then it becomes a fee. It the donation happens by accident, then we have to call it something else, but not donation!

I donate when I feel like, not when the system fails!

Michelem made a sweet job, I love it and I have donated more than once. But now I stay away from my rig for 24 ou 48 hours and cannot stand the idea of accidentally mining as a donation against my will. Donation by accident is not donation!

I truly believe in the generosity of michelem’s intentions, proven by his dedication to the development of this system as a hobby. But still, I removed the donation pool and will keep things as they are until I voluntarily decide it’s time to donate again.

By my choice, and not by some random event…

mmm and what do you think about adding an option to automatically switch to the main pool every X minutes? I mean, Minera could check every X minutes if it's hashing on the main pool and if doesn't it tries to switch to it.

EDIT: BTW I think the problem is related to Nicehash pool only, I'm almost convinced of this. I know it's not a good workaround but if you with this kind of problem could try to remove the Nicehash pool completely (no main no failover) that could be a nice try.

Moving donation pool to second to the last does not really help here. It still wil uncontrollably miner on that pool if you don't check your miners all the time..

Suggestion: how about adding donation pool in a way that can be removed? This will still leave an option to donate for everyone and to remove it for those with multiple Blades, since all of them most likely removed it manually. Just until you find a better solution..

Can we have the textbox added back for this?

I know this isn't THE solution but I think moving the donation pool as the second to the last pool could do the trick. So if this really weird behaviour happens it selects a pool of yours instead the donation one.

This can help while I'm finding the real solution.

Maybe you're right. I just shared my recent experience but I must admit my results can be pure coincidence

Not really sure if it does make sense lately to set diff on nicehash, because they implemented vardiff which ignores settings. I could be wrong though.

Before vardiff i think diff=2048 worked best for 5 Blades on 1 RPi. Somehow diff=8192 (from their spreadsheet) just didn't work so well.

Exactly the same situation was happening with my miners... It simply moved down the list (5 or 6 major multipools, which could not be down all at once) and end up on donation pool. I also had to remove donation pools manually otherwise using Minera (donating 30% of the time) simply would't make sense.

I have no idea but I have been mining at Nicehash using Minera with very decent results. I believe the trick is to find the appropriate difficulty. Right now, I have one Blade (80 chips) pointed at Nicehash with diff=1024.

I'm getting a fairly stable hash rate with very few rejections.

My bad... chmod 777 changes the permissions of the file file to read, write, and execute for all. Thank you for correcting me  

PS: But it works!

I had about 30% of one of my two rigs on the donationpool the other day based on the amount of accepted shares. I don't think Clevermining, Ghash, Nicehash AND multipool were down but Ghash did work on the donation account. It seems it's not checking up in the list but with an error just going down. I've manually removed the donationpool from the json file but it's a pain to change the password for nicehash every time the rate of scrypt jumps or drops through WinSCP

Would it be possible to make the donation minutes an option starting with 1 minutes increments instead of 15 and higher and remove the donation pool for now? I've already donated around release 1.0 but wouldn't be against donating another 5 minutes a day on top of that.

damn this dashboard is one of the best I have seen so far.

I don't know but I remember there were some issues with CPUminer-gc3355 and Nicehash pool, but for this we should ask to Sandor.

Did the donation pool issue happen again?

For who is posting how to remove the donation pool, changing it directly in the json file and change permission on it could work but read-only permission aren't 777 but 444.

I want to be able to use... so that would pry need a different miner program instead of cpuminer....

voltage=1
--no-submit-stale