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

All, it really helps when you state your issues that you mention if you are using mini's or blades and how many of each. The fact that Blades do not use autotune, means they are almost 2 different products with regard to troubleshooting and configurations.


Just an FYI many, many people are running minera with absolutely no issues with both Blades and mini's. In fact of all the solutions I have used this is by far the most stable and easiest to use. Not to mention the fact the development cycle is crazy fast and responsive. Michelem and Sandor make quite the team

I never used the save frequency setting on Minera, I already knew what frequencies to use when I installed Minera. But yes, I do put specific frequencies on my settings, that's a problem?

This is just a test system, it's as simple as it gets. It only has one raspberry and one Gridseed 5 chip, unmodded, so no stress with usb hubs. Rebooting doesn't solve. And yes, this is a fresh install.

I've seen what's up with blades and Minera, so not using those with it, thanks for the heads up. I guess I'll switch back to SSH control for now.

the miner hanging when you set saved frequencies is a known problem

the other stuff seems to be a feature of cpuminer that or duff usb hubs (mine seem fine since I ditched the cheapo ones) a reboot is the best bet.

Oh and I have had little success with my 40 chip blades which seem to hang with minera if it's blades you are using use hashra or a as I have  low power netbook and bgminer

Minera is indeed very good, but it's still very unstable, and has been like so in the last versions. Things I've been noticing:

1. If I save new settings and restart, minerd hangs randomly, while setting chip frequencies
2. Also, when I save new settings and restart, it sometimes starts hashing but does not accept any shares
(to solve all of the above I have to restart several times till it works)
3. when I add 3 or more pools, it gives errors similar to 1 and 2, and the only workaround is to remove those pools from the config
4. Pool switcher rarely works

Anyone experiencing the same? Any workarounds?

How often do your Blades drop/freeze? With latest update it's easier to spot those (in previous version you could only see only Last share 20000 secs ago, but individual hashrate was still showing sth like 2.7 Mh/s)



Afaik, a miner restart in Minera menu solves this problem?

michelem, great job with the latest update and your code also solved my Dashboard problem with 5Blades/RPi

Yes, that's the first thing I did.  When that didn't work, then I cloned the cpuminer-gc3355 and built it, then copied that over the minera-bin/minerd with the same results. 

I did try running minerd manually and specifying the --log=./log.txt as well as --log=log.txt and both cause minerd to just freeze.
I'll mess with it later this weekend if I have time.  Right now minera works to display stats ONLY if I start minerd manually without the log function. 

It worked! 

Thank you!

All set michelem. Everything perfect....Thanks for the support
The update is fantastic! The color coding is excellent to monitor individual miners at a glance. Keep up the good work. I'll be sending you some more BTC as a thank you

First of all, did you overwrite the minera-bin/minerd file with that for Ubuntu 64bit? I don't think there is a binary for Ubuntu in cpuminer-gc3355 git page (that's for RPI a different architecture)

My bad, I should enforce the git pull to prevent this kind of problems, now with this you should have a clean upgraded environment:


NOTE: every time you update the system running git commands manually you have to run ./upgrade_minera.sh too, this resets the notification icon while it does every system upgrade needed.

Thanks for feedbacks guys

PS
autotune saved freq seems to be bugged need to investigate

General Question:

When I save my autotuned frequencies (which works great!), is there a way to keep my saved frequencies running on startup AND add NEW devices that will be autotuned.... I hate to have all my devices autotuned over again over 6+ hours just to add two more gridseeds. Thanks!

gfuzz

when you put the 1.12 update on the program still as the I symble showing and states that an update is available and you have 1.11 installed

This worked for me too. Tnx, fivejonnyfive

Since the update today, the Dashboard DB popups errors have gone away, I really like the new hashrate reporting too (side effect is it starts way high and comes down to level off, previous showed much lower hashrate and came up to level off).

Is there any way to get the default devices to be 25+?  Seems like it always defaults back to 5 devices shown on the Dashboard.

Cheers!

That is the error I got. For better or worse I just ran "sudo git stash" and then I was able to update manually.

I had just done a fresh install of Ubuntu and minera yesterday and all was working fine.  Unfortunately I was using a test machine with an old drive and we had a power flicker over night and the drive didn't work after that. 
I replaced the drive and just did a fresh install of Ubuntu this morning, followed all instructions to a T to install minera.  Did everything exactly the same as I did yesterday.  And minera doesn't work and neither does mining.

The gridseeds are fine, network is fine, it's something to do with minera as I pulled down the cpuminer-gc3355 from github, built it, and am able to run it manually and it works. 
After minera is installed fresh, I change the settings to reflect the pool I'm using, speeds, and other settings.  Save.  Start Miner.  Then I get the message it's unable to get stats.
It does this no matter what I do.  I even copied the minerd that was freshly built from the cpuminer-gc3355 git to the minera-bin/minerd and get the same results.

If I run minerd manually and specify the minera_conf.json I get a core dump message. 
If I edit the minera_conf.json and remove ONLY the logging line, then it seems to work ok - but only if I run minerd manually.  Removing the logging from within the minera interface doesn't seem to resolve anything. 

I haven't checked the application logs yet, just thought I'd throw my experience in here and see if anyone had any suggestions.

minera@raspberrypi /var/www/minera $ sudo ./upgrade_minera.sh
-----
START Minera Upgrade script
-----

-----
Install extra packages
-----

Reading package lists... Done
Building dependency tree       
Reading state information... Done
autoconf is already the newest version.
automake is already the newest version.
build-essential is already the newest version.
libcurl4-openssl-dev is already the newest version.
libjansson-dev is already the newest version.
libncurses5-dev is already the newest version.
libtool is already the newest version.
libudev-dev is already the newest version.
postfix is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 56 not upgraded.
Changing permissions on Minera dir
-----

Upgrading sudoers configuration for www-data and minera users
-----

Changing cron file
-----

Adding minera to www-data group
-----

Adding default settings
-----

OK
Update redis values
-----

(integer) 1
(integer) 1
DONE! Minera is ready!



......nothing changed.

michelem, after auto update i also tried manual update

minera@minera /var/www/minera $ sudo git pull
Updating 1f5814f..727d1fa
error: Your local changes to the following files would be overwritten by merge:
        conf/index.html
Please, commit your changes or stash them before you can merge.
Aborting

Please try:


And please look at the logs too (application/logs/)

When I punch in the update manually it throws an error saying I had locally modified /conf/index.html
(I hadn't)

Anyway, did a git stash and then a git pull and it seems to have gone through.

Worth noting the reboot page shows the following error: