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

[isuelt]

Has anyone gotten Minera to work with MiningRigRentals.com.  Everytime I put the pool info in it does weird things and never connects.  I've tried both the http:// version and stratum+tcp:// version of their configuration.

I've done this on two different Pi's.  Both Pi's are running mini Gridseed Dual miners.


From the Rig Information page. Does it matter that Minera uses CPUminer?




Miner Configuration Examples

cgminer --scrypt -o http://us-west01.miningrigrentals.com:3333 -u isuelt.xxxx -p x
sgminer --scrypt -o http://us-west01.miningrigrentals.com:3333 -u isuelt.xxxx -p x
cudaminer --algo scrypt --url http://us-west01.miningrigrentals.com:3333 -u isuelt.xxxx -p x
bfgminer.exe --scrypt -o stratum+tcp://us-west01.miningrigrentals.com:3333 -u isuelt.xxxx -p x --no-gbt --no-getwork

Note: cudaminer users may need to use stratum+tcp://

Please allow up to 2 minutes for your miner to establish its connection

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.

+1 on this.  I'd like to get Minera to work with MiningRigRentals.com

[chadwickx16]

Hey michelem I'm brand new to Minera and am in the process of reading through all 45 pages right now. Want to say thanks and what a wonderful find this is for me. Two questions, I know e-mail notifications are in the works, how is that coming? And Is there an option for farm management that I may have yet to come up on or that is in the works.

[chadwickx16]

Has anyone gotten Minera to work with MiningRigRentals.com.  Everytime I put the pool info in it does weird things and never connects.  I've tried both the http:// version and stratum+tcp:// version of their configuration.

I've done this on two different Pi's.  Both Pi's are running mini Gridseed Dual miners.


From the Rig Information page. Does it matter that Minera uses CPUminer?




Miner Configuration Examples

cgminer --scrypt -o http://us-west01.miningrigrentals.com:3333 -u isuelt.xxxx -p x
sgminer --scrypt -o http://us-west01.miningrigrentals.com:3333 -u isuelt.xxxx -p x
cudaminer --algo scrypt --url http://us-west01.miningrigrentals.com:3333 -u isuelt.xxxx -p x
bfgminer.exe --scrypt -o stratum+tcp://us-west01.miningrigrentals.com:3333 -u isuelt.xxxx -p x --no-gbt --no-getwork

Note: cudaminer users may need to use stratum+tcp://

Please allow up to 2 minutes for your miner to establish its connection

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.

+1 on this.  I'd like to get Minera to work with MiningRigRentals.com

Glad you were able to get it to work. Thanks to Merx at MRR for the help!

[michelem]

Hey michelem I'm brand new to Minera and am in the process of reading through all 45 pages right now. Want to say thanks and what a wonderful find this is for me. Two questions, I know e-mail notifications are in the works, how is that coming? And Is there an option for farm management that I may have yet to come up on or that is in the works.

I don't think you need to read all the 45 pages, just read carefully the README and you should be ready to start mining happily with Minera
For email notifications, that will be added in the next big release along with CG/BFGminer support, I planned this for August 2014 if everything goes well.
Instead, farm management is not planned yet 'cause it could be another big code rewrite and I wanna be focused on the other features before putting hands on this.
So stay tuned for next updates and thank you very much for your appreciation!

[SilentH]

Michelem,

Just wanted to say thanks again for your continued support of this project and looking forward to  future changes that include BFGminer/CGminer. Sadly Gridseed doesn't seem to be keeping up and right now Zeus has hit the sweet spot. As I sit here contemplating additional hardware purchases, im always falling back to "how will I run my miners?" Nothing else out there provides me the confidence I want that Minera brings.

[pcjunkie86]

Just a quick update. I was able to get Minera to use my pools by manually editing the miner_conf.json file in order to remove the donation pool. Everything is working flawlessly now. I look forward to future improvements!

[MScFW]

Hi michelem,
hi all,
first I want to say that Minera is so far the most reliable/stable miner solution I've tried for my small Gridseed farm - great job, thanks michelem!

At the moment I'm using 2 Raspberry PIs, one managing 10 Gridseed Minis, the other one supporting 5 Gridseed Blades.

Even a good solution can be improved, that's the reason why I would like to share some of my findings and ideas.

1. Stability

• With some hardware revisions and kernel version there is a reported issue with freezing systems. As already mentioned in most of the topics covering various Raspberry PI mining solutions, there is an easy workaround by adding an addional parameter to the "/boot/cmdline.txt" file:

Code:

dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait slub_debug=FP

The "slub_debug=FP" will do the trick.

=> perhaps an option for the next release?

• If this is not enough, or you are looking for an additional safety-line, unsing the build-in harware watchdog is an option. Unfortunately most available sources do not cover a small issue with defaults in the actual version 5.12 of the watchdog daemon. The watchdog in the BMC2708 is limited to ~16s timeout, but the default of the watchdog daemon seem to be 60s. If you want to give it a try, the following steps will do it, incl. a workaround for the timeout issue:

Code:

$ sudo modprobe bcm2708_wdog
$ echo "bcm2708_wdog" | sudo tee -a /etc/modules

$ sudo apt-get update
$ sudo apt-get install watchdog
$ sudo chkconfig --add watchdog
$ sudo chkconfig watchdog on

• The configuration in "/etc/watchdog.conf" should look like this:

Code:

max-load-1              = 24
min-memory              = 1
watchdog-device = /dev/watchdog
realtime                = yes
priority                = 1
watchdog-timeout   = 10

The additional parameter "watchdog-timeout = 10" solved the problem on my systems.

• The last step is starting/restarting the daemon:

Code:

$ sudo /etc/init.d/watchdog restart

=> could be added to the master image in one for the next releases?!?

• Last bit is an automatic reboot every 12 hours, for that I added a line to "/etc/crontab":

Code:

...
5 */12 * * *    root    /bin/sync && /sbin/reboot
...

This will sync the SD card and rebbot the PI at 0:05 and 12:05 every day.

=> configuration through the web ui would be nice!

2. Pool Selection / NiceHash / Donation Pool

My two systems do NOT behave the same.

• the Minis have not yet reached the "race condition" to end up with the last pool in the list
• for my Blades this happened already several times - was Ok as donation for michelem, but should not be the default behaviour in the future.

Based on what I could track on my system, it's not just NiceHash, but NiceHash with the "p=x.y" option as password will more or less force the failure when the pools are changed too often. It also happend to me with ltcrabbits and a very low diff when switching to this pool, but only with the blades, not with the Minis!
The "cpuminer.log" shows the following:

Code:

[2014-06-26 23:21:17] stratum_recv_line failed
[2014-06-26 23:21:17] Stratum connection interrupted
[2014-06-26 23:21:17] Starting Stratum on stratum+tcp://eu.ltcrabbit.com:3333
[2014-06-26 23:21:17] stratum_recv_line failed
[2014-06-26 23:21:17] ...retry after 5 seconds
[2014-06-26 23:21:22] submit_upstream_work stratum_send_line failed
[2014-06-26 23:21:22] ...retry after 5 seconds
[2014-06-26 23:21:23] New Job_id: 2f41 Diff: 32 Work_id: 8ed3f9d6
[2014-06-26 23:21:25] New Job_id: 2f42 Diff: 32 Work_id: 8ed3f9d6
[2014-06-26 23:21:27] submit_upstream_work stratum_send_line failed
[2014-06-26 23:21:27] ...retry after 5 seconds
[2014-06-26 23:21:27] Rejected 600a447b GSD 7@15
[2014-06-26 23:21:27] DEBUG: reject reason: job not found
...
[2014-06-26 23:21:27] DEBUG: reject reason: job not found
[2014-06-26 23:21:32] submit_upstream_work stratum_send_line failed
[2014-06-26 23:21:32] ...retry after 5 seconds
[2014-06-26 23:21:32] Rejected a6714685 GSD 0@26
[2014-06-26 23:21:32] DEBUG: reject reason: job not found
[2014-06-26 23:21:32] stratum_recv_line failed
[2014-06-26 23:21:32] Stratum connection interrupted
...
[2014-06-26 23:21:47] Rejected ecdabe3d GSD 3@37
[2014-06-26 23:21:47] DEBUG: reject reason: low difficulty share of 0.000028805203748063583
[2014-06-26 23:21:47] Starting Stratum on stratum+tcp://eu.ltcrabbit.com:3333
[2014-06-26 23:21:48] stratum_recv_line failed
[2014-06-26 23:21:48] ...retry after 5 seconds
[2014-06-26 23:21:52] submit_upstream_work stratum_send_line failed
[2014-06-26 23:21:52] ...retry after 5 seconds
[2014-06-26 23:21:53] New Job_id: 2f93 Diff: 32 Work_id: 8ef195ed
[2014-06-26 23:21:57] submit_upstream_work stratum_send_line failed
[2014-06-26 23:21:57] ...retry after 5 seconds
[2014-06-26 23:21:58] Rejected 8674e16b GSD 4@21
[2014-06-26 23:21:58] DEBUG: reject reason: low difficulty share of 0.00002044789273909275
...
[2014-06-26 23:21:58] Rejected f34240a1 GSD 0@38
[2014-06-26 23:21:58] DEBUG: reject reason: low difficulty share of 0.0008953760268679294
[2014-06-26 23:22:00] Checking main pool: stratum+tcp://stratum.nicehash.com:3333
[2014-06-26 23:22:00] Stratum authentication failed
[2014-06-26 23:22:03] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:03] Rejected 6cdbeab1 GSD 7@17
[2014-06-26 23:22:03] DEBUG: reject reason: low difficulty share of 0.00002086725782000612
[2014-06-26 23:22:03] ...retry after 5 seconds
[2014-06-26 23:22:03] Rejected 600f3044 GSD 6@15
[2014-06-26 23:22:03] DEBUG: reject reason: low difficulty share of 0.000026977634249723677
...
[2014-06-26 23:22:03] Rejected b9a9127e GSD 2@29
[2014-06-26 23:22:03] DEBUG: reject reason: low difficulty share of 0.000020940332663484334
[2014-06-26 23:22:03] stratum_recv_line failed
[2014-06-26 23:22:03] Stratum connection interrupted
[2014-06-26 23:22:03] Starting Stratum on stratum+tcp://eu.ltcrabbit.com:3333
[2014-06-26 23:22:03] New Job_id: 2f42 Diff: 32 Work_id: 8efb367d
[2014-06-26 23:22:08] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:08] ...retry after 5 seconds
[2014-06-26 23:22:08] Rejected e678590b GSD 1@36
[2014-06-26 23:22:08] DEBUG: reject reason: job not found
...
[2014-06-26 23:22:08] Rejected 93459d49 GSD 5@23
[2014-06-26 23:22:08] DEBUG: reject reason: job not found
[2014-06-26 23:22:13] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:13] ...retry after 5 seconds
[2014-06-26 23:22:13] Rejected 8678f100 GSD 6@21
[2014-06-26 23:22:13] DEBUG: reject reason: job not found
[2014-06-26 23:22:13] stratum_recv_line failed
[2014-06-26 23:22:13] Stratum connection interrupted
[2014-06-26 23:22:13] Starting Stratum on stratum+tcp://eu.ltcrabbit.com:3333
[2014-06-26 23:22:13] stratum_recv_line failed
[2014-06-26 23:22:13] ...retry after 5 seconds
[2014-06-26 23:22:18] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:18] ...retry after 5 seconds
[2014-06-26 23:22:18] New Job_id: 2f94 Diff: 32 Work_id: 8f0a8598
[2014-06-26 23:22:23] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:23] ...retry after 5 seconds
[2014-06-26 23:22:23] Rejected 59afe1e6 GSD 7@14
[2014-06-26 23:22:23] DEBUG: reject reason: low difficulty share of 0.000038679563917316584
...
[2014-06-26 23:22:23] Rejected 59b0570a GSD 4@14
[2014-06-26 23:22:23] DEBUG: reject reason: low difficulty share of 0.000015259335727904784
[2014-06-26 23:22:28] Stratum detected new block
[2014-06-26 23:22:28] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:28] New Job_id: 2f95 Diff: 32 Work_id: 8f1429f3
[2014-06-26 23:22:28] ...retry after 5 seconds
[2014-06-26 23:22:28] Rejected 867d2d1d GSD 0@21
[2014-06-26 23:22:28] DEBUG: reject reason: job not found
...
[2014-06-26 23:22:28] Rejected b3366217 GSD 8@28
[2014-06-26 23:22:28] DEBUG: reject reason: job not found
[2014-06-26 23:22:33] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:33] Rejected b99a43d0 GSD 1@29
[2014-06-26 23:22:33] ...retry after 5 seconds
[2014-06-26 23:22:33] DEBUG: reject reason: job not found
[2014-06-26 23:22:33] Rejected c667315c GSD 9@31
...
[2014-06-26 23:22:33] Rejected c0006c5f GSD 4@30
[2014-06-26 23:22:33] DEBUG: reject reason: job not found
[2014-06-26 23:22:33] stratum_recv_line failed
[2014-06-26 23:22:33] Stratum connection interrupted
[2014-06-26 23:22:33] Starting Stratum on stratum+tcp://eu.ltcrabbit.com:3333
[2014-06-26 23:22:33] stratum_recv_line failed
[2014-06-26 23:22:33] ...retry after 5 seconds
[2014-06-26 23:22:38] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:38] ...retry after 5 seconds
[2014-06-26 23:22:38] stratum_recv_line failed
[2014-06-26 23:22:38] ...retry after 5 seconds

If have also seen crap strings as pool names in the screen session during this race, but could not capture this.
Remarks:

• Gridseed Blades don't like very small diffs, like 32, best results for me in a range from 256 to 1024 for my setup.
• Girdseed Minis will work with a diff of 32 already, better results within a range from 128 to 512, again in my setup
• For me it seems to be a problem of the cpuminer, not linked to the Minera UI and/or the donation pool idea

It looks like the miners are not set to a default state during a pool switch, so the results may not fit to new jobs and will produce a high number of rejects.
If I understood right, cpuminer is using an array to store some additional data for each pool during runtime, based on the crap strings I have seen, I would not be surprised if there is a "buffer overflow", "pointer error" or a kind of type mismatch in this lately added part. If it comes to a pool switch followed by a larger number of rejects things will/may go wrong.
>> All mentioned as a person who can't really read and understand code, so maybe I'm totally wrong here. <<

Based on this problem I'm not using NiceHash with the "p=x.y" option, witch means I have to monitor manually or use only pools where I can define the minimum diff for each worker - not good.

Regards

MScFW

[michelem]

Hi michelem,
hi all,
first I want to say that Minera is so far the most reliable/stable miner solution I've tried for my small Gridseed farm - great job, thanks michelem!

At the moment I'm using 2 Raspberry PIs, one managing 10 Gridseed Minis, the other one supporting 5 Gridseed Blades.

Even a good solution can be improved, that's the reason why I would like to share some of my findings and ideas.

1. Stability

• With some hardware revisions and kernel version there is a reported issue with freezing systems. As already mentioned in most of the topics covering various Raspberry PI mining solutions, there is an easy workaround by adding an addional parameter to the "/boot/cmdline.txt" file:

Code:

dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait slub_debug=FP

The "slub_debug=FP" will do the trick.

=> perhaps an option for the next release?

• If this is not enough, or you are looking for an additional safety-line, unsing the build-in harware watchdog is an option. Unfortunately most available sources do not cover a small issue with defaults in the actual version 5.12 of the watchdog daemon. The watchdog in the BMC2708 is limited to ~16s timeout, but the default of the watchdog daemon seem to be 60s. If you want to give it a try, the following steps will do it, incl. a workaround for the timeout issue:

Code:

$ sudo modprobe bcm2708_wdog
$ echo "bcm2708_wdog" | sudo tee -a /etc/modules

$ sudo apt-get update
$ sudo apt-get install watchdog
$ sudo chkconfig --add watchdog
$ sudo chkconfig watchdog on

• The configuration in "/etc/watchdog.conf" should look like this:

Code:

max-load-1              = 24
min-memory              = 1
watchdog-device = /dev/watchdog
realtime                = yes
priority                = 1
watchdog-timeout   = 10

The additional parameter "watchdog-timeout = 10" solved the problem on my systems.

• The last step is starting/restarting the daemon:

Code:

$ sudo /etc/init.d/watchdog restart

=> could be added to the master image in one for the next releases?!?

• Last bit is an automatic reboot every 12 hours, for that I added a line to "/etc/crontab":

Code:

...
5 */12 * * *    root    /bin/sync && /sbin/reboot
...

This will sync the SD card and rebbot the PI at 0:05 and 12:05 every day.

=> configuration through the web ui would be nice!

2. Pool Selection / NiceHash / Donation Pool

My two systems do NOT behave the same.

• the Minis have not yet reached the "race condition" to end up with the last pool in the list
• for my Blades this happened already several times - was Ok as donation for michelem, but should not be the default behaviour in the future.

Based on what I could track on my system, it's not just NiceHash, but NiceHash with the "p=x.y" option as password will more or less force the failure when the pools are changed too often. It also happend to me with ltcrabbits and a very low diff when switching to this pool, but only with the blades, not with the Minis!
The "cpuminer.log" shows the following:

Code:

[2014-06-26 23:21:17] stratum_recv_line failed
[2014-06-26 23:21:17] Stratum connection interrupted
[2014-06-26 23:21:17] Starting Stratum on stratum+tcp://eu.ltcrabbit.com:3333
[2014-06-26 23:21:17] stratum_recv_line failed
[2014-06-26 23:21:17] ...retry after 5 seconds
[2014-06-26 23:21:22] submit_upstream_work stratum_send_line failed
[2014-06-26 23:21:22] ...retry after 5 seconds
[2014-06-26 23:21:23] New Job_id: 2f41 Diff: 32 Work_id: 8ed3f9d6
[2014-06-26 23:21:25] New Job_id: 2f42 Diff: 32 Work_id: 8ed3f9d6
[2014-06-26 23:21:27] submit_upstream_work stratum_send_line failed
[2014-06-26 23:21:27] ...retry after 5 seconds
[2014-06-26 23:21:27] Rejected 600a447b GSD 7@15
[2014-06-26 23:21:27] DEBUG: reject reason: job not found
...
[2014-06-26 23:21:27] DEBUG: reject reason: job not found
[2014-06-26 23:21:32] submit_upstream_work stratum_send_line failed
[2014-06-26 23:21:32] ...retry after 5 seconds
[2014-06-26 23:21:32] Rejected a6714685 GSD 0@26
[2014-06-26 23:21:32] DEBUG: reject reason: job not found
[2014-06-26 23:21:32] stratum_recv_line failed
[2014-06-26 23:21:32] Stratum connection interrupted
...
[2014-06-26 23:21:47] Rejected ecdabe3d GSD 3@37
[2014-06-26 23:21:47] DEBUG: reject reason: low difficulty share of 0.000028805203748063583
[2014-06-26 23:21:47] Starting Stratum on stratum+tcp://eu.ltcrabbit.com:3333
[2014-06-26 23:21:48] stratum_recv_line failed
[2014-06-26 23:21:48] ...retry after 5 seconds
[2014-06-26 23:21:52] submit_upstream_work stratum_send_line failed
[2014-06-26 23:21:52] ...retry after 5 seconds
[2014-06-26 23:21:53] New Job_id: 2f93 Diff: 32 Work_id: 8ef195ed
[2014-06-26 23:21:57] submit_upstream_work stratum_send_line failed
[2014-06-26 23:21:57] ...retry after 5 seconds
[2014-06-26 23:21:58] Rejected 8674e16b GSD 4@21
[2014-06-26 23:21:58] DEBUG: reject reason: low difficulty share of 0.00002044789273909275
...
[2014-06-26 23:21:58] Rejected f34240a1 GSD 0@38
[2014-06-26 23:21:58] DEBUG: reject reason: low difficulty share of 0.0008953760268679294
[2014-06-26 23:22:00] Checking main pool: stratum+tcp://stratum.nicehash.com:3333
[2014-06-26 23:22:00] Stratum authentication failed
[2014-06-26 23:22:03] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:03] Rejected 6cdbeab1 GSD 7@17
[2014-06-26 23:22:03] DEBUG: reject reason: low difficulty share of 0.00002086725782000612
[2014-06-26 23:22:03] ...retry after 5 seconds
[2014-06-26 23:22:03] Rejected 600f3044 GSD 6@15
[2014-06-26 23:22:03] DEBUG: reject reason: low difficulty share of 0.000026977634249723677
...
[2014-06-26 23:22:03] Rejected b9a9127e GSD 2@29
[2014-06-26 23:22:03] DEBUG: reject reason: low difficulty share of 0.000020940332663484334
[2014-06-26 23:22:03] stratum_recv_line failed
[2014-06-26 23:22:03] Stratum connection interrupted
[2014-06-26 23:22:03] Starting Stratum on stratum+tcp://eu.ltcrabbit.com:3333
[2014-06-26 23:22:03] New Job_id: 2f42 Diff: 32 Work_id: 8efb367d
[2014-06-26 23:22:08] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:08] ...retry after 5 seconds
[2014-06-26 23:22:08] Rejected e678590b GSD 1@36
[2014-06-26 23:22:08] DEBUG: reject reason: job not found
...
[2014-06-26 23:22:08] Rejected 93459d49 GSD 5@23
[2014-06-26 23:22:08] DEBUG: reject reason: job not found
[2014-06-26 23:22:13] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:13] ...retry after 5 seconds
[2014-06-26 23:22:13] Rejected 8678f100 GSD 6@21
[2014-06-26 23:22:13] DEBUG: reject reason: job not found
[2014-06-26 23:22:13] stratum_recv_line failed
[2014-06-26 23:22:13] Stratum connection interrupted
[2014-06-26 23:22:13] Starting Stratum on stratum+tcp://eu.ltcrabbit.com:3333
[2014-06-26 23:22:13] stratum_recv_line failed
[2014-06-26 23:22:13] ...retry after 5 seconds
[2014-06-26 23:22:18] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:18] ...retry after 5 seconds
[2014-06-26 23:22:18] New Job_id: 2f94 Diff: 32 Work_id: 8f0a8598
[2014-06-26 23:22:23] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:23] ...retry after 5 seconds
[2014-06-26 23:22:23] Rejected 59afe1e6 GSD 7@14
[2014-06-26 23:22:23] DEBUG: reject reason: low difficulty share of 0.000038679563917316584
...
[2014-06-26 23:22:23] Rejected 59b0570a GSD 4@14
[2014-06-26 23:22:23] DEBUG: reject reason: low difficulty share of 0.000015259335727904784
[2014-06-26 23:22:28] Stratum detected new block
[2014-06-26 23:22:28] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:28] New Job_id: 2f95 Diff: 32 Work_id: 8f1429f3
[2014-06-26 23:22:28] ...retry after 5 seconds
[2014-06-26 23:22:28] Rejected 867d2d1d GSD 0@21
[2014-06-26 23:22:28] DEBUG: reject reason: job not found
...
[2014-06-26 23:22:28] Rejected b3366217 GSD 8@28
[2014-06-26 23:22:28] DEBUG: reject reason: job not found
[2014-06-26 23:22:33] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:33] Rejected b99a43d0 GSD 1@29
[2014-06-26 23:22:33] ...retry after 5 seconds
[2014-06-26 23:22:33] DEBUG: reject reason: job not found
[2014-06-26 23:22:33] Rejected c667315c GSD 9@31
...
[2014-06-26 23:22:33] Rejected c0006c5f GSD 4@30
[2014-06-26 23:22:33] DEBUG: reject reason: job not found
[2014-06-26 23:22:33] stratum_recv_line failed
[2014-06-26 23:22:33] Stratum connection interrupted
[2014-06-26 23:22:33] Starting Stratum on stratum+tcp://eu.ltcrabbit.com:3333
[2014-06-26 23:22:33] stratum_recv_line failed
[2014-06-26 23:22:33] ...retry after 5 seconds
[2014-06-26 23:22:38] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:38] ...retry after 5 seconds
[2014-06-26 23:22:38] stratum_recv_line failed
[2014-06-26 23:22:38] ...retry after 5 seconds

If have also seen crap strings as pool names in the screen session during this race, but could not capture this.
Remarks:

• Gridseed Blades don't like very small diffs, like 32, best results for me in a range from 256 to 1024 for my setup.
• Girdseed Minis will work with a diff of 32 already, better results within a range from 128 to 512, again in my setup
• For me it seems to be a problem of the cpuminer, not linked to the Minera UI and/or the donation pool idea

It looks like the miners are not set to a default state during a pool switch, so the results may not fit to new jobs and will produce a high number of rejects.
If I understood right, cpuminer is using an array to store some additional data for each pool during runtime, based on the crap strings I have seen, I would not be surprised if there is a "buffer overflow", "pointer error" or a kind of type mismatch in this lately added part. If it comes to a pool switch followed by a larger number of rejects things will/may go wrong.
>> All mentioned as a person who can't really read and understand code, so maybe I'm totally wrong here. <<

Based on this problem I'm not using NiceHash with the "p=x.y" option, witch means I have to monitor manually or use only pools where I can define the minimum diff for each worker - not good.

Regards

MScFW

Thank you very much for your feedback and appreciation! As you said, the problem with the random pool switch is only related to GBlades and some weird things they do with this cpuminer version and I'm sorry but I can't do anything but remove the donation pool.
So, as I just said before, I did a new release that will be the 0.2.3 with the ability to remove the donation pool (because I wanna you are happy with Minera and you use it) and some other small fixes/features like the timezone setting.

I hope the introduction of BFGminer/CGminer could help for this problem but that feature is not ready yet and it takes several weeks to be completed.

For the freezing issue that's not a problem to add that line as boot command but I should test it and this is the same for the watchdog, I will ask you more when I could put my hands on those.

Unfortunately (for me but not for you) tomorrow will be my last vacation day and on Sunday I will be at home ready and excited to re-start taking care of Minera. I have everything ready to be pushed as new release but here I have a really poor connection and so I decided it's better wait few days instead releasing it from here.

So guys, as usual, have a great weekend and stay tuned for next release!

[Ghostdoge]

Does minera not work with blizzard / furys?

I've got it set up and its found the asic however it runs at 0kh's, any idea what i'm doing wrong here?

[Lucax]

Hi
I me asked a question, Can i run my g-blade with minera ?

[chadwickx16]

Hi
I me asked a question, Can i run my g-blade with minera ?

Yes I currently have 15 running on 2 pis.

[crackfoo]

Does minera not work with blizzard / furys?

I've got it set up and its found the asic however it runs at 0kh's, any idea what i'm doing wrong here?

I'm curious as well. The ZenOs they offer is crap.

[MScFW]

Hi michelem,
switching to CGminer or BFGminer instead of the CPUminer would turn Minera into "just another Raspery PI solution". I tried a lot of images based on several versions of these miners, not finding a better working setup. For me CPUminer has some nice features:

• autotuning for the Minis - haven't tried it my blades so far
• beside the switching issue it's way more stable than any of the other miners I've tested
• in combination with your ui and your monitoring option it's "just working"
• most important: it's clean and light - not overloading the PI like some other solutions

From my point of view it would make sense to fix the CPUminer and improve the ui step by step - just my opinion.

Looking for some unique features for the next releases:

• common dashboard for multiple Minera instances with control and not only status
• extending the summary for pool hashrate and last share information to show min/max/avg
• adding something to switch pools on profit
• ...

bye

MScFW

[SilentH]

and now there is a fork of cgminer that supports both Gridseeds and Zeus miners.
https://github.com/dmaxl/cgminer/

[wolf_miner]

Hi, minera is available only as RasPI image or is available also a WiiBox / 703N firmware image?

Thanks in advance W_M

[michelem]

@MScFW Thanks for feedbacks, but I never said Minera will switch to CG/BFGMiner, instead Minera will support ALSO those miners giving to the users the ability to choose their preferred miner for the hardware that system has. Of course I will encourage to use CPUMiner for Gridseed devices but the user could choose any supported miner there will be.

@wolf_miner Minera runs in any Debian based system, but there isn't a port to Wiibox, I know there were some guys working on that but I think they gave up cause lack of needed libraries.

[phiber]

Anyone knows if it's possible for me to connect both Gridseed dual-miners (Those flower looking thingys) and gridseed blades to the same minera controller?
Will it be able to differentiate and control all properly?

Looking at connecting 6 x gridseeds and 2 x blades...

[Trimegistus]

Anyone knows if it's possible for me to connect both Gridseed dual-miners (Those flower looking thingys) and gridseed blades to the same minera controller?
Will it be able to differentiate and control all properly?

Looking at connecting 6 x gridseeds and 2 x blades...

I haven't done it myself but I believe someone else has. The cpuminer option to "auto detect" will handle both miners with 5 or 40 chips.

Try to browse this thread from the first pages and you will find info on that subject.

Good luck 

[michelem]

Hi, michelem.

My dashboard was stuck. I tried reboot, poweroff. Nothing works. I cannot get into the dashboard. Now after 20 minutes it finally worked. I had 7 days uptime on my RPI.

That was caused by Cryptsy API was down. I just put a fix there if the Cryptsy API will be down again.

[gigica viteazu`]

Anyone knows if it's possible for me to connect both Gridseed dual-miners (Those flower looking thingys) and gridseed blades to the same minera controller?
Will it be able to differentiate and control all properly?

Looking at connecting 6 x gridseeds and 2 x blades...

it works as a charm