M's Miner (Ant/SP) Monitor v5.2: alerts,auto/mass/scheduled reboot/mobile miner

[mdude77]

Negative - no joy - will not get any info.

I almost forgot.  My SP20 came with API access disabled.  I'm guessing the SP35s are the same.  From an earlier post of mine:


PLEASE NOTE!

My SP20 came with only local API access allowed.  That means this program won't be able to talk to it.  To enable it, you need to SSH into your miner (you may have to enable SSH) and edit /etc/cgminer.conf to allow network access.  If you don't know how to do this, try this at your own risk:

SSH to your miner
type "vi /etc/cgminer.conf"

On my SP20, I see one line of data that start with this:

{"api-listen":true,"api-allow":"W:127.0.0.1","pools":

press 'i' on your keyboard to allow editing

scroll to the end of the section that reads "W:127.0.0.1" and add ",your ip", like this where "your ip" is the IP address the monitoring app is running from.  It should look something like this:

{"api-listen":true,"api-allow":"W:127.0.0.1,192.168.0.194","pools":

press Esc, ':' then 'w' and then 'q' and press enter.

Restart cgminer from the miner console, and on the pools tab you should see the new API allow.

M

[1715423118]

1715423118

[1715423118]

1715423118

[1715423118]

1715423118

[1715423118]

1715423118

[1715423118]

1715423118

[smilingloki]

Negative - no joy - will not get any info.

I almost forgot.  My SP20 came with API access disabled.  I'm guessing the SP35s are the same.  From an earlier post of mine:


PLEASE NOTE!

My SP20 came with only local API access allowed.  That means this program won't be able to talk to it.  To enable it, you need to SSH into your miner (you may have to enable SSH) and edit /etc/cgminer.conf to allow network access.  If you don't know how to do this, try this at your own risk:

SSH to your miner
type "vi /etc/cgminer.conf"

On my SP20, I see one line of data that start with this:

{"api-listen":true,"api-allow":"W:127.0.0.1","pools":

press 'i' on your keyboard to allow editing

scroll to the end of the section that reads "W:127.0.0.1" and add ",your ip", like this where "your ip" is the IP address the monitoring app is running from.  It should look something like this:

{"api-listen":true,"api-allow":"W:127.0.0.1,192.168.0.194","pools":

press Esc, ':' then 'w' and then 'q' and press enter.

Restart cgminer from the miner console, and on the pools tab you should see the new API allow.

M

Did that,

Restarted miner -

in one of the screens it now has this - CGMiner Conf

    api-listen

    True
    api-allow

    W:127.0.0.1,192.168.1.101

im assuming thats a good sign. but on the mantmonitor log it reads -

22/12/2014 4:56:39 p.m.: ERROR when querying SP:1.101GALACTICA (step 1.0): Value cannot be null.
Parameter name: s
22/12/2014 4:57:11 p.m.: ERROR when accessing API on 192.168.1.101: Thread was being aborted.

[mdude77]

Did that,

Restarted miner -

in one of the screens it now has this - CGMiner Conf

    api-listen

    True
    api-allow

    W:127.0.0.1,192.168.1.101

im assuming thats a good sign. but on the mantmonitor log it reads -

22/12/2014 4:56:39 p.m.: ERROR when querying SP:1.101GALACTICA (step 1.0): Value cannot be null.
Parameter name: s
22/12/2014 4:57:11 p.m.: ERROR when accessing API on 192.168.1.101: Thread was being aborted.

That doesn't seem quite right.  Above you wrote:

Unable to get a responses from 192.168.1.101

Which tells me the SP35 IP is 192.168.1.101.  If that's the case, you put the wrong IP in the cgminer.conf.  The IP you want in the conf file is the IP you're running the mining monitor app from, ie, your PC.

M

[smilingloki]

Did that,

Restarted miner -

in one of the screens it now has this - CGMiner Conf

    api-listen

    True
    api-allow

    W:127.0.0.1,192.168.1.101

im assuming thats a good sign. but on the mantmonitor log it reads -

22/12/2014 4:56:39 p.m.: ERROR when querying SP:1.101GALACTICA (step 1.0): Value cannot be null.
Parameter name: s
22/12/2014 4:57:11 p.m.: ERROR when accessing API on 192.168.1.101: Thread was being aborted.

That doesn't seem quite right.  Above you wrote:

Unable to get a responses from 192.168.1.101

Which tells me the SP35 IP is 192.168.1.101.  If that's the case, you put the wrong IP in the cgminer.conf.  The IP you want in the conf file is the IP you're running the mining monitor app from, ie, your PC.

M

LMAO ! NOW i understand OMG such a noob - thanks M for putting up with my very noobish ways

[smilingloki]

STATS:
{"STATUS":[{"STATUS":"S","When":1419283234,"Code":70,"Msg":"CGMiner stats","Description":"cgminer 4.7.0"}],"STATS":[{"STATS":0,"ID":"S300","Elapsed":6,"Calls":0,"Wait":0.000000,"Max":0.000000,"Min":99999999.000000,"ASICs total rate":0,"Temperature front":32,"Temperature rear top":81,"Temperature rear bot":82},{"STATS":1,"ID":"POOL0","Elapsed":6,"Calls":0,"Wait":0.000000,"Max":0.000000,"Min":99999999.000000,"Pool Calls":0,"Pool Attempts":0,"Pool Wait":0.000000,"Pool Max":0.000000,"Pool Min":99999999.000000,"Pool Av":0.000000,"Work Had Roll Time":false,"Work Can Roll":false,"Work Had Expire":false,"Work Roll Time":0,"Work Diff":32.00000000,"Min Diff":32.00000000,"Max Diff":32.00000000,"Min Diff Count":131,"Max Diff Count":131,"Times Sent":21,"Bytes Sent":2484,"Times Recv":23,"Bytes Recv":1936,"Net Bytes Sent":2484,"Net Bytes Recv":1936},{"STATS":2,"ID":"POOL1","Elapsed":6,"Calls":0,"Wait":0.000000,"Max":0.000000,"Min":99999999.000000,"Pool Calls":0,"Pool Attempts":0,"Pool Wait":0.000000,"Pool Max":0.000000,"Pool Min":99999999.000000,"Pool Av":0.000000,"Work Had Roll Time":true,"Work Can Roll":true,"Work Had Expire":false,"Work Roll Time":60,"Work Diff":0.00000000,"Min Diff":0.00000000,"Max Diff":0.00000000,"Min Diff Count":0,"Max Diff Count":0,"Times Sent":6,"Bytes Sent":476,"Times Recv":8,"Bytes Recv":2103,"Net Bytes Sent":1055,"Net Bytes Recv":2588}],"id":1}

POOLS:
{"STATUS":[{"STATUS":"S","When":1419283234,"Code":7,"Msg":"2 Pool(s)","Description":"cgminer 4.7.0"}],"POOLS":[{"POOL":0,"URL":"my miner URL","Status":"Alive","Priority":0,"Quota":1,"Long Poll":"N","Getworks":1,"Accepted":19,"Rejected":0,"Works":73,"Discarded":57,"Stale":0,"Get Failures":0,"Remote Failures":0,"User":"my user name","Last Share Time":1419283228,"Diff1 Shares":608,"Proxy Type":"","Proxy":"","Difficulty Accepted":608.00000000,"Difficulty Rejected":0.00000000,"Difficulty Stale":0.00000000,"Last Share Difficulty":32.00000000,"Has Stratum":true,"Stratum Active":true,"Stratum URL":"stratum.bitcoin.cz","Has GBT":false,"Best Share":5254,"Pool Rejected%":0.0000,"Pool Stale%":0.0000},{"POOL":1,"URL":"my miner URL","Status":"Alive","Priority":1,"Quota":1,"Long Poll":"Y","Getworks":1,"Accepted":0,"Rejected":0,"Works":0,"Discarded":0,"Stale":0,"Get Failures":0,"Remote Failures":0,"User":"my user name","Last Share Time":0,"Diff1 Shares":0,"Proxy Type":"","Proxy":"","Difficulty Accepted":0.00000000,"Difficulty Rejected":0.00000000,"Difficulty Stale":0.00000000,"Last Share Difficulty":0.00000000,"Has Stratum":true,"Stratum Active":false,"Stratum URL":"","Has GBT":false,"Best Share":0,"Pool Rejected%":0.0000,"Pool Stale%":0.0000}],"id":1}

SUMMARY:
{"STATUS":[{"STATUS":"S","When":1419283234,"Code":11,"Msg":"Summary","Description":"cgminer 4.7.0"}],"SUMMARY":[{"Elapsed":6,"MHS av":434668.94,"MHS 5s":290669.00,"MHS 1m":39894.41,"MHS 5m":8545.00,"MHS 15m":2883.47,"Found Blocks":0,"Getworks":2,"Accepted":19,"Rejected":0,"Hardware Errors":0,"Utility":189.76,"Discarded":57,"Stale":0,"Get Failures":0,"Local Work":131,"Remote Failures":0,"Network Blocks":1,"Total MH":2611338.0000,"Work Utility":6072.26,"Difficulty Accepted":608.00000000,"Difficulty Rejected":0.00000000,"Difficulty Stale":0.00000000,"Best Share":5254,"Device Hardware%":0.0000,"Device Rejected%":0.0000,"Pool Rejected%":0.0000,"Pool Stale%":0.0000,"Last getwork":1419283233}],"id":1}


http://iforce.co.nz/i/lcczteuf.yha.jpg

Shows the ghs/5s and the Ghs/Avg but no fans speeds etc

[mdude77]

Shows the ghs/5s and the Ghs/Avg but no fans speeds etc

This is what there is to show for SPs.  Fanspeed is fixed by what you have in the UI, and doesn't show in the output.  Xs and frequency are Antminer specific, and as far as I can tell, the SPs don't have an equivalent.

I'll check out the output you listed above, but at first glance it's virtually identical to the SP20, just faster.  That's what I was hoping.

Thanks!

M

[ChineseSavior]

I'm getting this error when i scan.




Im also not showing any ants on my output view. I am running windows 8 and i have entered the ip addresses manually

[mdude77]

I'm getting this error when i scan.

Im also not showing any ants on my output view. I am running windows 8 and i have entered the ip addresses manually

Looks like you're trying to run the executable without the included DLLs.  Both the Newtonsoft.Json.DLL and Renci.SshNet.dll need to be in the same directory as MMinerMonitor.  Let me know if that fixes it.

M

[rsvoter]

I'm getting this error when i scan.

Im also not showing any ants on my output view. I am running windows 8 and i have entered the ip addresses manually

Looks like you're trying to run the executable without the included DLLs.  Both the Newtonsoft.Json.DLL and Renci.SshNet.dll need to be in the same directory as MMinerMonitor.  Let me know if that fixes it.

M

Fixed mine

[ChineseSavior]

im not sure I follow? They are all in the folder they downloaded in... there was no instal it only gave me the option to click on the program I do see the other two files tho.


wait nvm BBBBBBBBOOOOMMMMM BABBBBYYY (american savage voice)

edit wait now im just getting alerts but my ants are not rebooting. prety sure i have every possibly reboot setting click and also the < amount set to 200..





another edt*

It sems to be working? Its saying 6.5 th/s mmonitor side tho and 7.1 th/s pool side?

edit*

The antmonitor program is seeing 14 out of 15 miner. Coincidentally the final minder the program is not seeing is only running on 1 blade (other blades problems) Maybe that is why. I just see ? in the uptime window for this miner.

[mdude77]

im not sure I follow? They are all in the folder they downloaded in... there was no instal it only gave me the option to click on the program I do see the other two files tho.


wait nvm BBBBBBBBOOOOMMMMM BABBBBYYY (american savage voice)

edit wait now im just getting alerts but my ants are not rebooting. prety sure i have every possibly reboot setting click and also the < amount set to 200..

Have you customized your SSH username/pw?  What does the log show?

M

[ChineseSavior]

oh wait okay i figured it out lol...

I removed it from the "list" because it was only half hasing and I dont know how to program 1 single unit to reset at a specific hash rate not all s3's....

please advise this is solution i need to know how to make 1 single s3 running at half hash to auto reset on its on < hash command. Thanks

[mdude77]

oh wait okay i figured it out lol...

I removed it from the "list" because it was only half hasing and I dont know how to program 1 single unit to reset at a specific hash rate not all s3's....

please advise this is solution i need to know how to make 1 single s3 running at half hash to auto reset on its on < hash command. Thanks

At the moment you can't.  The S3 rules apply to all S3s.  However, if you set it to reboot when "hashrate" is less than something, it should only affect the degraded miner.

Right?

M

[ChineseSavior]

oh wait okay i figured it out lol...

I removed it from the "list" because it was only half hasing and I dont know how to program 1 single unit to reset at a specific hash rate not all s3's....

please advise this is solution i need to know how to make 1 single s3 running at half hash to auto reset on its on < hash command. Thanks

At the moment you can't.  The S3 rules apply to all S3s.  However, if you set it to reboot when "hashrate" is less than something, it should only affect the degraded miner.

Right?

M

right I understand. If you watch the s3's (at least mine) I am getting two main types of hash drops. The first is where the unit will half in hashing as if a board dies. After reboot this will be fixed (as prior stated this is why i was asking about programing each s3 because 1 of mine is permantly running at half efficiency)

The second is what I have posted below. With this shot notice the first spot is around 50gh/s while the second is showing 450ghs... Why is this doing this? it is only hasing at 50ghs poolside andit is a glitch. for some reason when my miners enter this type of state they will not reboot.

please advise

[mdude77]

right I understand. If you watch the s3's (at least mine) I am getting two main types of hash drops. The first is where the unit will half in hashing as if a board dies. After reboot this will be fixed (as prior stated this is why i was asking about programing each s3 because 1 of mine is permantly running at half efficiency)

Got it.  What I'd do is mark the S3 that is running at half efficiency as another type of Ant, such as an S1.  Most of them are interchangable.

The second is what I have posted below. With this shot notice the first spot is around 50gh/s while the second is showing 450ghs... Why is this doing this? it is only hasing at 50ghs poolside andit is a glitch. for some reason when my miners enter this type of state they will not reboot.

please advise

I'm not sure about that. Do you have the latest firmware on your S3s?  I thought I heard the latest has problems, so maybe one older than latest.

M

[ChineseSavior]

right I understand. If you watch the s3's (at least mine) I am getting two main types of hash drops. The first is where the unit will half in hashing as if a board dies. After reboot this will be fixed (as prior stated this is why i was asking about programing each s3 because 1 of mine is permantly running at half efficiency)

Got it.  What I'd do is mark the S3 that is running at half efficiency as another type of Ant, such as an S1.  Most of them are interchangable.

The second is what I have posted below. With this shot notice the first spot is around 50gh/s while the second is showing 450ghs... Why is this doing this? it is only hasing at 50ghs poolside andit is a glitch. for some reason when my miners enter this type of state they will not reboot.

please advise

I'm not sure about that. Do you have the latest firmware on your S3s?  I thought I heard the latest has problems, so maybe one older than latest.

M

where do I get the older firmware sir? Also will I be able to load the firmware remotely through the gui? Or would I need to make sure someone is on location to power cycle? I think that also this dropping may be a switch issue.

I'm just not sure why ant monitor is not detecting that drop and auto rebooting. Also just had my #14 unit quit hashing all together and it didn't try to reboot..?

[mdude77]

right I understand. If you watch the s3's (at least mine) I am getting two main types of hash drops. The first is where the unit will half in hashing as if a board dies. After reboot this will be fixed (as prior stated this is why i was asking about programing each s3 because 1 of mine is permantly running at half efficiency)

Got it.  What I'd do is mark the S3 that is running at half efficiency as another type of Ant, such as an S1.  Most of them are interchangable.

The second is what I have posted below. With this shot notice the first spot is around 50gh/s while the second is showing 450ghs... Why is this doing this? it is only hasing at 50ghs poolside andit is a glitch. for some reason when my miners enter this type of state they will not reboot.

please advise

I'm not sure about that. Do you have the latest firmware on your S3s?  I thought I heard the latest has problems, so maybe one older than latest.

M

where do I get the older firmware sir? Also will I be able to load the firmware remotely through the gui? Or would I need to make sure someone is on location to power cycle? I think that also this dropping may be a switch issue.

I'm just not sure why ant monitor is not detecting that drop and auto rebooting. Also just had my #14 unit quit hashing all together and it didn't try to reboot..?

Is the monitor running onsite with the miners, or remotely?  The reboots are run via SSH, are the machines accessible via SSH?  Check the log tab, it should have info there.

As for firmware, check the bitmain site.

M

[ChineseSavior]

right I understand. If you watch the s3's (at least mine) I am getting two main types of hash drops. The first is where the unit will half in hashing as if a board dies. After reboot this will be fixed (as prior stated this is why i was asking about programing each s3 because 1 of mine is permantly running at half efficiency)

Got it.  What I'd do is mark the S3 that is running at half efficiency as another type of Ant, such as an S1.  Most of them are interchangable.

The second is what I have posted below. With this shot notice the first spot is around 50gh/s while the second is showing 450ghs... Why is this doing this? it is only hasing at 50ghs poolside andit is a glitch. for some reason when my miners enter this type of state they will not reboot.

please advise

I'm not sure about that. Do you have the latest firmware on your S3s?  I thought I heard the latest has problems, so maybe one older than latest.

M

where do I get the older firmware sir? Also will I be able to load the firmware remotely through the gui? Or would I need to make sure someone is on location to power cycle? I think that also this dropping may be a switch issue.

I'm just not sure why ant monitor is not detecting that drop and auto rebooting. Also just had my #14 unit quit hashing all together and it didn't try to reboot..?

Is the monitor running onsite with the miners, or remotely?  The reboots are run via SSH, are the machines accessible via SSH?  Check the log tab, it should have info there.

As for firmware, check the bitmain site.

M

monitor is running on site on basic windows machine. I have been having lots of trouble with my ants dropping in hash. I really hope its a switch issue. I'm getting a drop like every 30 minutes.

Does the monitor lag behind a little to reset the machines? It almost seems like if I watch it I drive myself crazy and then if I let it do its own thing it works? Maybe I'm going crazy and/or the machines are resetting so often.

[mdude77]

monitor is running on site on basic windows machine. I have been having lots of trouble with my ants dropping in hash. I really hope its a switch issue. I'm getting a drop like every 30 minutes.

Does the monitor lag behind a little to reset the machines? It almost seems like if I watch it I drive myself crazy and then if I let it do its own thing it works? Maybe I'm going crazy and/or the machines are resetting so often.

Are your ants remote?  Or are they local?

How many ants are we talking about?  There was one user on here with 1000 S3s and the app saturated his network when it was scanning.  He had to bump up his hardware quality and bandwidth for it to work properly.

M

[ChineseSavior]

monitor is running on site on basic windows machine. I have been having lots of trouble with my ants dropping in hash. I really hope its a switch issue. I'm getting a drop like every 30 minutes.

Does the monitor lag behind a little to reset the machines? It almost seems like if I watch it I drive myself crazy and then if I let it do its own thing it works? Maybe I'm going crazy and/or the machines are resetting so often.

Are your ants remote?  Or are they local?

How many ants are we talking about?  There was one user on here with 1000 S3s and the app saturated his network when it was scanning.  He had to bump up his hardware quality and bandwidth for it to work properly.

M

im only running 14 s3's and 1 c1. all through some low grade 30$ asus I bought like a month ago. now has been discontinued. The ants are local in relation to the machine I am logging into though.


I'm still having issues when it drops to this odd 50/450 pic i just posted. It's like it's not understanding that its actually hashing at 50ghs and not 450ghs.