Re: M's Miner (S1/S2/S3/C1) Monitor v3.9: alerts,auto/mass/scheduled reboot/fast
Just found and installed this nice little app but not yet read the 48 pages in this thread so apologies if the following issues are duplicates of earlier threads.
First issue is that I have 2 virtually identical AntMiner S3's on sequential IP addresses (101 and 102). All settings passwords etc. are the same and I can connect via http to both units but the App only shows 101 in the Ant Output section. The settings in the App are identical save for the IP address, Name and of course ID#. The log shows the following error message...
ERROR when querying S3:0.102 (step 1): Object reference not set to an instance of an object.
08/12/2014 17:28:22: Attempting to reboot S3:0.102 via the web because the API query errored out.
08/12/2014 17:28:22: REBOOTING S3:0.102 via SSH
08/12/2014 17:28:44: Reboot of S3:0.102 FAILED: Permission denied (password).
This leads on to my second issue - why is reboot on error enabled by default? Surely anything like this should by default be disabled, so that the user must choose to enable if required? This reason I am annoyed about this point is that the above log is taken from my second attempt to get 102 working. On my first attempt, I set the correct SSH password and the app rebooted my AntMiner - Ahhhhhh I was in the middle of a longevity test so not a happy bunny
Happy to provide any screenshots or info if you require on the first point.
Many thanks in advance
Cheers n beers
HPmuirt
First issue is that I have 2 virtually identical AntMiner S3's on sequential IP addresses (101 and 102). All settings passwords etc. are the same and I can connect via http to both units but the App only shows 101 in the Ant Output section. The settings in the App are identical save for the IP address, Name and of course ID#. The log shows the following error message...
ERROR when querying S3:0.102 (step 1): Object reference not set to an instance of an object.
08/12/2014 17:28:22: Attempting to reboot S3:0.102 via the web because the API query errored out.
08/12/2014 17:28:22: REBOOTING S3:0.102 via SSH
08/12/2014 17:28:44: Reboot of S3:0.102 FAILED: Permission denied (password).
This leads on to my second issue - why is reboot on error enabled by default? Surely anything like this should by default be disabled, so that the user must choose to enable if required? This reason I am annoyed about this point is that the above log is taken from my second attempt to get 102 working. On my first attempt, I set the correct SSH password and the app rebooted my AntMiner - Ahhhhhh I was in the middle of a longevity test so not a happy bunny
Happy to provide any screenshots or info if you require on the first point.
Many thanks in advance
Cheers n beers
HPmuirt
Hello. That "reboot on failure" option is NOT supposed to be on by default. Apparently there's a problem somewhere that causes that to turn on of its own accord.
I apologize for that.As for why one works and one doesn't ... are they using the same firmware?
M