[Minera v0.9.1] Your next mining dashboard - Antminer/CPUminer/CGminer/BFGminer

[Flep182]

Hi,

I can't choose my own pool. When I set it, it seems to work for a few seconds and then defaults back to the developer's donation pool. Also, one of my miners is not reporting a hash rate. Any help would be greatly appreciated.

Have you tried setting up multiple pools?

[1714078172]

1714078172

[1714078172]

1714078172

[1714078172]

1714078172

[1714078172]

1714078172

[Ajeto]

This is just annoying. Woke up just to find 6 out of 8 Rpis switched again to 6th pool (Donation). Michelem could you please fix this

[pcjunkie86]

Hi,

I can't choose my own pool. When I set it, it seems to work for a few seconds and then defaults back to the developer's donation pool. Also, one of my miners is not reporting a hash rate. Any help would be greatly appreciated.

Have you tried setting up multiple pools?

I just added some more. It's still defaulting back to the donation pool after what seems like a few seconds, or whenever you refresh the dashboard next.

[madmartyk]

Hi,

I can't choose my own pool. When I set it, it seems to work for a few seconds and then defaults back to the developer's donation pool. Also, one of my miners is not reporting a hash rate. Any help would be greatly appreciated.

Have you tried setting up multiple pools?

I just added some more. It's still defaulting back to the donation pool after what seems like a few seconds, or whenever you refresh the dashboard next.

That's not a bug, it's an undocumented feature!    (Just Kidding)
BTW, I do not have that issue at all.

[michelem]

@ajeto I'm afraid it's a personal behavior that, it's really weird, one question if you remove the donation pool by hand you still have this happen? I mean the pools were switched also without the donation pool?

Did you enable time donation? Can you try to disable and save? (But I really don't think it's that the problem)
Also, can you look at the cpuminer log? I believe there is a problem at cpuminer level and I can't do much more cause it's not my software.

Of course this is a problem but trust me I'm not absolutely responsible (intentionally) of that.
I'm also sorry because I'm currently on my summer vacation and I cannot do much from here.

Hope you can solve the issue, please keep me updated.
Thanks

[Ajeto]

@ajeto I'm afraid it's a personal behavior that, it's really weird, one question if you remove the donation pool by hand you still have this happen? I mean the pools were switched also without the donation pool?

Wasn't aware i can remove it in the first place I will test with out it although I'm quite sure that is not the reason.

Did you enable time donation? Can you try to disable and save? (But I really don't think it's that the problem)

No it is disabled. I also don't think that's a problem. The problem is that (for unknown reason so far) i get a bunch of rejects which moves me down the pool list (and never returns me back up to poll 0 for example).

Of course this is a problem but trust me I'm not absolutely responsible (intentionally) of that.
I'm also sorry because I'm currently on my summer vacation and I cannot do much from here.

Yes I'm quite sure you are not responsible for that. I just suggested you check this pool swapping (fail-over) AND/OR add miner autoreset every xx hours. Enjoy your vacation

[michelem]

Yes I'm quite sure you are not responsible for that. I just suggested you check this pool swapping (fail-over) AND/OR add miner autoreset every xx hours. Enjoy your vacation

Restarting devices after X time is planned and if I find a good connection I could add it from here too or that's will be of course on next release.

I had an idea, do you use the "--retries" option as extra option for you config? I don't want the absence of that option could cause the weird behaviour you have.

Please can you try setting up this option within your cpuminer starting command line:

Code:

--retries=0

You can place it as extra options in the settings. This tells cpuminer to not retry a down pool, just pass to the next failover or come back to the main one until you find a good pool.

Of course I'm not the cpuminer's author but I gave a look at the code and probably the absence of that option could impact it in this case.

Please let me know.

EDIT: and please @Ajeto if that happens again send me the entire cpuminer.log that could be really useful for me (still better if it has debug active). Please don't paste it here, just save it in a cloud drive and give me the url. Thanks!

[michelem]

Is there a way or command that I can use to check if all the chips on a G-Blade are working in the logger?  I have two G-Blades and one seems to be under performing and i'm getting way to many HW errors:



I think two or more chips are not working  :-|

I think you can look at http://<ip>/minera/index.php/app/stats URL, that should give you each chip stat.

[gigica viteazu`]

small bug/things to fix:

- one problem that need fixing ASAP is the fact that after the donation period the miner doesn`t revert to the pool he was mining on prior to that, it start on the first pool in the list.

- device list and pool changing widgets are missing on mobile devices, only in portrait mode

- donation log should be sorted by date rather that day name

[gigica viteazu`]

@gigica is that records per page default 10?

yes

[Ajeto]

I had an idea, do you use the "--retries" option as extra option for you config? I don't want the absence of that option could cause the weird behaviour you have.

yes, these are my extra options:
--gc3355-timeout=500 --retries=1 --gc3355-freq=48FB50683831:838:0,48FB50683831:838:1,....

Please can you try setting up this option within your cpuminer starting command line:

Code:

--retries=0

Sure I' will try with retries=0 and let you know.

EDIT: and please @Ajeto if that happens again send me the entire cpuminer.log that could be really useful for me (still better if it has debug active). Please don't paste it here, just save it in a cloud drive and give me the url. Thanks!

I'll send you some logs today

[Trimegistus]

Hi,

I can't choose my own pool. When I set it, it seems to work for a few seconds and then defaults back to the developer's donation pool. Also, one of my miners is not reporting a hash rate. Any help would be greatly appreciated.

I had this problem myself once or twice. In order to overcome this difficulty and improve on a few other situations, I’ve been trying to attain three basic goals:
 
1-Rotate my pools
2-Change my blades’ frequency during the hot hours of the day
3-Remove the donation pool to prevent accidental prolonged donation
 
And I believe I've found a way to achieve all of this.

Basic steps:
 
Inside /var/www/minera/conf:

Create two files: miner_conf.json1 and miner_conf.json2 with different sets of pools (remove the donation pool if you wish)

You can do this either by hand or via the GUI and then copy via SSH. Your choice...

Inside /etc

Create two files rc.local1 and rc.local2
Add the appropriate command lines:

Code:

/usr/bin/screen -dmS cpuminer /var/www/minera/minera-bin/minerd --gc3355-detect --gc3355-timeout=180 --freq=820 --retries=2 -c /var/www/minera/conf/miner_conf.json

and

Code:

/usr/bin/screen -dmS cpuminer /var/www/minera/minera-bin/minerd --gc3355-detect --gc3355-timeout=180 --freq=840 --retries=2 -c /var/www/minera/conf/miner_conf.json

inside /bin

Create two scripts OC-morning and OC-afternoon

Code:

vi OC-morning

(add lines below)

Code:

sudo cp /var/www/minera/conf/miner_conf.json1 /var/www/minera/conf/miner_conf.json
sudo chmod 777 /var/www/minera/conf/miner_conf.json
sudo cp /etc/rc.local1 /etc/rc.local
sudo chmod 777 /etc/rc.local
sudo kill $(pidof minerd)
sudo /usr/bin/screen -dmS cpuminer /var/www/minera/minera-bin/minerd --gc3355-detect --gc3355-timeout=180 --freq=820 --retries=2 -c /var/www/minera/conf/miner_conf.json

(exit and save file)

Code:

sudo chmod 777 OC-morning

Code:

vi OC-afternoon

(add lines below)

Code:

sudo cp /var/www/minera/conf/miner_conf.json2 /var/www/minera/conf/miner_conf.json
sudo chmod 777 /var/www/minera/conf/miner_conf.json
sudo cp /etc/rc.local2 /etc/rc.local
sudo chmod 777 /etc/rc.local
sudo kill $(pidof minerd)
sudo /usr/bin/screen -dmS cpuminer /var/www/minera/minera-bin/minerd --gc3355-detect --gc3355-timeout=180 --freq=840 --retries=2 -c /var/www/minera/conf/miner_conf.json

(exit and save file)

Code:

sudo chmod 777 OC-afternoon

Create a cron task

Code:

crontab -e

(add lines below)

Code:

0 10 * * * /bin/OC-morning
0 18 * * * /bin/OC-afternoon

(exit and save file)

It appears to be working like a charm, rotating my pools once a day, cooling down my blades during the hottest hours of day while reducing the HWE and preventing any accidental donation.

@michelem: Sorry for this litle hack. I just want to push the system a little further. Hope you don't mind  

[emanzer0]

I really like how nice the os is but the biggest turnoff is not being able to mine a wallet and no new commits have been done with cpuminer since 5/21. Dead project?  No plans to implement getwork in cpuminer?

Is there a proxy or workaround that can turn getwork to stratum? I've seen the ones that turn stratum to getwork.

[Ibisy]

I think you can look at http://<ip>/minera/index.php/app/stats URL, that should give you each chip stat.

Thanks for your help  The only thing i get is this per blade:

Code:

{"ttyACM3":{"frequency":800,"accepted":2489,"rejected":2,"hw_errors":1,"shares":3611400,"hashrate":2701197,"last_share":1403308505,"serial":"48FC66603135"}

I think is just the total 

[suzukii]

Hi,

I can't choose my own pool. When I set it, it seems to work for a few seconds and then defaults back to the developer's donation pool. Also, one of my miners is not reporting a hash rate. Any help would be greatly appreciated.

Ditto on one of my two stock g-blades no matter what freq I put them at.  They seem to alternate.

[Trimegistus]

Hi,

I can't choose my own pool. When I set it, it seems to work for a few seconds and then defaults back to the developer's donation pool. Also, one of my miners is not reporting a hash rate. Any help would be greatly appreciated.

Ditto on one of my two stock g-blades no matter what freq I put them at.  They seem to alternate.

I provided a solution for this. Read my previous post:

https://bitcointalk.org/index.php?topic=596620.msg7424487#msg7424487

Hope it helps. It worked for me!

[Flep182]

I removed the donation pool but it just returned again (I think after rebooting the miner). Very annoying.

[Trimegistus]

I removed the donation pool but it just returned again (I think after rebooting the miner). Very annoying.

If you follow my procedure, the donation pool will appear in the settings GUI but not on the dashboard list of pools because it is not included in the json file.

If you save any of your settings while the donation pool is listed under the settings list, it will be included again in the json file.

My procedure overrides this 

[Trimegistus]

I removed the donation pool but it just returned again (I think after rebooting the miner). Very annoying.

If you follow my procedure, the donation pool will appear in the settings GUI but not on the dashboard list of pools because it is not included in the json file.

If you save any of your settings while the donation pool is listed under the settings list, it will be included again in the json file.

My procedure overrides this  

Which procedure? sudo nano miner_conf.json ? Remove donation pool, ctrl x save and exit?

Your step seems to have mixed steps, blades and remove donation. Make a one clear step to remove donation to be permanent.

You are right, my steps involve a lot more than just removing the donation pool.

In order to do just that you can edit the miner_conf.json file, remove the donation pool, save the file, restart the miner.

Something like this:

Go to /var/www/minera/conf

Code:

sudo nano miner_conf.json

(remove donation pool, add other pools, etc)
(ctrl x save and exit)

(Change the file's permissions)

Code:

sudo chmod 777 miner_conf.json

(restart miner - use your own parameters)

Code:

sudo kill $(pidof minerd)
sudo /usr/bin/screen -dmS cpuminer /var/www/minera/minera-bin/minerd --gc3355-detect --gc3355-timeout=180 --freq=838 --retries=2 -c /var/www/minera/conf/miner_conf.json

The donation pool will always show up in Minera settings but won't be used unless you save your settings via the GUI because that will overrride the json file, adding the donation pool again.

Got it?

[Ajeto]

Does Minera (cpuminer) support extranonce subscriptions?

https://bitcointalk.org/index.php?topic=562238.msg7439217#msg7439217