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

[wlz2011]

More on a machine malfunction

These machines work properly.

This problem may also be .001.002

Monitoring alone an error of the machine,

Display will become normal.

Google Translation

[1714934461]

1714934461

[mdude77]

More on a machine malfunction

These machines work properly.

This problem may also be .001.002

Monitoring alone an error of the machine,

Display will become normal.

Google Translation

Are they all using the latest firmware?

What does the error log show?

M

[mdude77]

Here's a minor change, released as a beta of 3.4b.  It's literally a one line change that appears to get it to work with the prior firmware version for the S3s.  Since I only have one S3, it's a bit awkward to continually reflash to the other version to make sure it works.  This worked for me with the prior version, and the current version.  Note that I didn't test it with the questionable version that was just released within the last few days.

Download link: MAntMonitor34b.zip

M

[mdude77]

Here's another beta of 3.4.

This contains my rewrite of the Ant scanning routine.  It now uses the API to find the Ants, making it much quicker, more responsive, and allows scanning of whatever segment you enter.  Note that it'll still wait up to 5 seconds for each address to respond, so you can do the math to figure out how long it will take based on how many Ants you have (or don't have).

MAntMonitor34b1.zip

M

[wlz2011]

Here's another beta of 3.4.

This contains my rewrite of the Ant scanning routine.  It now uses the API to find the Ants, making it much quicker, more responsive, and allows scanning of whatever segment you enter.  Note that it'll still wait up to 5 seconds for each address to respond, so you can do the math to figure out how long it will take based on how many Ants you have (or don't have).

MAntMonitor34b1.zip

M

Mr. M Hello

Identified cause.

Software is fast, very smooth.

However, it will consume a large amount of network.

Network almost collapsed,

Can not view Internet pages.

I set 50 ants, use 64 threads.

Display refresh one second,

Refresh every 300 seconds.

Only need one second you can scan all 50 mining machine.

All mining machine display properly.

If I use the Refresh every 100.

So will see 4-8 sets of mining machinery ERROR.

I try to reduce the thread, there is no effect.

I tested 1,000 ants, use 64 threads.

Consider the following diagram,

The network is consumed,

Network recovery,

The network is consumed,

Cycle.

Pictures lot, a lot,

If affects everyone browsing, I'm sorry.


Google Translation












2014/9/8 19:43:58: M's Ant Monitor v3.4b1 starting
2014/9/8 19:43:58: Initiated Ant refresh
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.022:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.22:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.012:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.12:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.049:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.49:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.059:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.59:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.016:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.16:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.008:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.8:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.051:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.51:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.032:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.32:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.028:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.28:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.036:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.36:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.030:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.30:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.054:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.54:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.038:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.38:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.002:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.2:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.058:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.58:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.010:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.10:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.050:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.50:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.034:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.34:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.014:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.14:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.046:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.46:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.026:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.26:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.062:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.62:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.042:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.42:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.006:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.6:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.018:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.18:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.060:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.60:4028
2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.052:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.52:4028
2014/9/8 19:44:19: ERROR when querying S3:001.012:80 (step 3): Value cannot be null.
Parameter name: s
2014/9/8 19:44:19: ERROR when querying S3:001.049:80 (step 3): Value cannot be null.
Parameter name: s
2014/9/8 19:44:19: ERROR when querying S3:001.059:80 (step 3): Value cannot be null.
Parameter name: s
2014/9/8 19:44:19: ERROR when querying S3:001.016:80 (step 3): Value cannot be null.
Parameter name: s
2014/9/8 19:44:19: ERROR when querying S3:001.008:80 (step 3): Value cannot be null.
Parameter name: s
2014/9/8 19:44:19: ERROR when querying S3:001.051:80 (step 3): Value cannot be null.
Parameter name: s
2014/9/8 19:44:19: ERROR when querying S3:001.032:80 (step 3): Value cannot be null.
Parameter name: s
2014/9/8 19:44:19: ERROR when querying S3:001.028:80 (step 3): Value cannot be null.

2014/9/8 19:47:10: ERROR when querying S3:002.007:80 (step 1): Value cannot be null.
Parameter name: s
2014/9/8 19:47:10: ERROR when querying S3:002.002:80 (step 1): Value cannot be null.
Parameter name: s
2014/9/8 19:47:10: ERROR when querying S3:002.014:80 (step 1): Value cannot be null.
Parameter name: s
2014/9/8 19:47:10: ERROR when querying S3:002.015:80 (step 1): Value cannot be null.
Parameter name: s
2014/9/8 19:47:10: ERROR when querying S3:002.008:80 (step 1): Value cannot be null.
Parameter name: s
2014/9/8 19:47:10: ERROR when querying S3:002.013:80 (step 1): Value cannot be null.
Parameter name: s
2014/9/8 19:47:10: ERROR when querying S3:002.005:80 (step 1): Value cannot be null.
Parameter name: s
2014/9/8 19:47:10: ERROR when querying S3:001.254:80 (step 1): Value cannot be null.



Parameter name: s
2014/9/8 19:47:10: ERROR when querying S3:002.011:80 (step 1): Value cannot be null.
Parameter name: s
2014/9/8 19:47:10: ERROR when querying S3:002.012:80 (step 1): Value cannot be null.
Parameter name: s
2014/9/8 19:47:10: ERROR when querying S3:002.018:80 (step 1): Value cannot be null.
Parameter name: s
2014/9/8 19:47:10: ERROR when querying S3:002.010:80 (step 1): Value cannot be null.
Parameter name: s
2014/9/8 19:47:10: ERROR when querying S3:002.006:80 (step 1): Value cannot be null.
Parameter name: s
2014/9/8 19:47:10: ERROR when querying S3:002.009:80 (step 1): Value cannot be null.
Parameter name: s
2014/9/8 19:47:10: ERROR when querying S3:002.016:80 (step 1): Value cannot be null.
Parameter name: s
2014/9/8 19:47:10: ERROR when querying S3:002.004:80 (step 1): Value cannot be null.
Parameter name: s
2014/9/8 19:47:10: ERROR when querying S3:002.017:80 (step 1): Value cannot be null.

[mdude77]

Mr. M Hello

Identified cause.

Software is fast, very smooth.

However, it will consume a large amount of network.

Network almost collapsed,

Can not view Internet pages.

I set 50 ants, use 64 threads.

Display refresh one second,

Refresh every 300 seconds.

Only need one second you can scan all 50 mining machine.

All mining machine display properly.

If I use the Refresh every 100.

So will see 4-8 sets of mining machinery ERROR.

I try to reduce the thread, there is no effect.

I tested 1,000 ants, use 64 threads.

Consider the following diagram,

The network is consumed,

Network recovery,

The network is consumed,

Cycle.

Pictures lot, a lot,

If affects everyone browsing, I'm sorry.

It sounds like your network can't handle querying all the Ants that quickly?  Even if the thread count is at the lowest?

M

[mdude77]

It sounds like your network can't handle querying all the Ants that quickly?  Even if the thread count is at the lowest?

M

If it's a network saturation issue, I can add an optional 1 second delay between calls.  If you set it to refresh every, say, 1100 seconds, it'll continually be refreshing all 1000 ants, one at a time.  Assuming all Ants respond in a timely manner, you're looking at about 17 minutes for a complete refresh.

Sound doable?

M

[wlz2011]

It sounds like your network can't handle querying all the Ants that quickly?  Even if the thread count is at the lowest?

M

If it's a network saturation issue, I can add an optional 1 second delay between calls.  If you set it to refresh every, say, 1100 seconds, it'll continually be refreshing all 1000 ants, one at a time.  Assuming all Ants respond in a timely manner, you're looking at about 17 minutes for a complete refresh.

Sound doable?

M

Two threads of thread or 4,

Yes, the error less.

Still an error occurs.

Since 1000 the ants, the impact is still very large.

Your method can try.

Because the translator is not,

I can Google translate,

Etc. translator came,

I asked him to re-translate once.

[wlz2011]

It sounds like your network can't handle querying all the Ants that quickly?  Even if the thread count is at the lowest?

M

If it's a network saturation issue, I can add an optional 1 second delay between calls.  If you set it to refresh every, say, 1100 seconds, it'll continually be refreshing all 1000 ants, one at a time.  Assuming all Ants respond in a timely manner, you're looking at about 17 minutes for a complete refresh.

Sound doable?

M

Hello Mr. M
Software is fast and smooth. But it will consume large amounts of network, resulting in network congestion, can not open a web page in normally.
I tested 50 ants S3, use 64 threads, display refresh one second refresh cycle 300 seconds. 1 second to 50 units will be able to check the working condition of ants, everything is normal..
If I change the refresh cycle is 100 seconds, you will find there are 4-8 sets of ants S3 displays an error.
Try two threads, still error occurs. I do not know it is the core network segment VLAN switch problems, or other reasons.
Test 1,000 ants S3, first pause about 5-10 seconds, check to 30 mining machine working status after an error occurs. Finally, a large area of error and  not working. Network is not down, you can not browse the Web, other computer turns ants console page.
I think it is a program to check the dozens of mining machine, got a job status information, but these threads still remain and mining machines to connect and not disconnected, causing network congestion.
You can try your method, do a version
I also have a stupid way like this
Option 1, for example, 64 threads, according to the IP address has been added to check the order of 64 mining machine working condition, after get a result, if there is no machine need to restart, then end off this 60 threads, pause for a few seconds, in order to continue check mining machine operation, until checked all mining machine.
Option 2: You can set the time to detect 50 mining machine (IP2-51, 300 seconds after the break, continue to check the working status of 50 mining machine (IP 52-102), loop executes until the examination was part mining machine.
Many thanks for your hard work, you've done well, I'm here got many  machines, multi-network segment. You do not have the embarrassment, you have a good technique. You and your M monitoring are great!

[cat2]

Really like the software!
Any chance of adding a name field?

[MoreBloodWine]

Due to some personal things I haven't been able to pay attention to this thread like I would have liked. That being said, M, what's the most recent version and what if any of my "issues" does it address.

Ty.

[mdude77]

Due to some personal things I haven't been able to pay attention to this thread like I would have liked. That being said, M, what's the most recent version and what if any of my "issues" does it address.

Ty.

None of your issues have been addressed unfortunately.  I don't have much time, and it's going to be getting slimmer for a few months.

M

[wlz2011]

It sounds like your network can't handle querying all the Ants that quickly?  Even if the thread count is at the lowest?

M

If it's a network saturation issue, I can add an optional 1 second delay between calls.  If you set it to refresh every, say, 1100 seconds, it'll continually be refreshing all 1000 ants, one at a time.  Assuming all Ants respond in a timely manner, you're looking at about 17 minutes for a complete refresh.

Sound doable?

M

Hello Mr. M
Software is fast and smooth. But it will consume large amounts of network, resulting in network congestion, can not open a web page in normally.
I tested 50 ants S3, use 64 threads, display refresh one second refresh cycle 300 seconds. 1 second to 50 units will be able to check the working condition of ants, everything is normal..
If I change the refresh cycle is 100 seconds, you will find there are 4-8 sets of ants S3 displays an error.
Try two threads, still error occurs. I do not know it is the core network segment VLAN switch problems, or other reasons.
Test 1,000 ants S3, first pause about 5-10 seconds, check to 30 mining machine working status after an error occurs. Finally, a large area of error and  not working. Network is not down, you can not browse the Web, other computer turns ants console page.
I think it is a program to check the dozens of mining machine, got a job status information, but these threads still remain and mining machines to connect and not disconnected, causing network congestion.
You can try your method, do a version
I also have a stupid way like this
Option 1, for example, 64 threads, according to the IP address has been added to check the order of 64 mining machine working condition, after get a result, if there is no machine need to restart, then end off this 60 threads, pause for a few seconds, in order to continue check mining machine operation, until checked all mining machine.
Option 2: You can set the time to detect 50 mining machine (IP2-51, 300 seconds after the break, continue to check the working status of 50 mining machine (IP 52-102), loop executes until the examination was part mining machine.
Many thanks for your hard work, you've done well, I'm here got many  machines, multi-network segment. You do not have the embarrassment, you have a good technique. You and your M monitoring are great!

hello Mr. M,
I have solved the problem.
I try to let the computer which been installed M monitoring software using the core network switch port VLAN assignment.
All problems solved, 51 seconds to scan 1,200 ants mining machine. One second refresh time.Refresh cycle time is 1000s.

I guess it should be out in a soft routing firewall, the packet may be too large to scan M monitoring,
Because I saw an instant network uses 10Mbps. Firewall denied network access
Mr. M, sincerely thank you, great software. best Wishs

[mdude77]

hello Mr. M,
I have solved the problem.
I try to let the computer which been installed M monitoring software using the core network switch port VLAN assignment.
All problems solved, 51 seconds to scan 1,200 ants mining machine. One second refresh time.Refresh cycle time is 1000s.

I guess it should be out in a soft routing firewall, the packet may be too large to scan M monitoring,
Because I saw an instant network uses 10Mbps. Firewall denied network access
Mr. M, sincerely thank you, great software. best Wishs

Excellent!   Thanks for the good news.

M

[Epoch]

v3.3 doesn't appear to support the current S3 firmware S320140826.bin.

[mdude77]

v3.3 doesn't appear to support the current S3 firmware S320140826.bin.

Is that the version that the hash didn't match what bitmain posted?

M

[Paxter]

thank you i sent a tip since this version is working for me now not that much but i hope you enjoy anyway thank you again

[mdude77]

thank you i sent a tip since this version is working for me now not that much but i hope you enjoy anyway thank you again

Got it, thanks!

M

[MoreBloodWine]

I don't know if I asked this before but could your app be made to possibly work with other machines like say Dragons or something ?

I know it would require you to physically have said machines in hand but I guess what I'm asking is have you ever thought of expanding upon your app beyond the Ants.

Ty.

[mdude77]

I don't know if I asked this before but could your app be made to possibly work with other machines like say Dragons or something ?

I know it would require you to physically have said machines in hand but I guess what I'm asking is have you ever thought of expanding upon your app beyond the Ants.

Ty.

I have thought about it.  You are correct, I need to have access to the machines.  I'm a low end miner, and I lost a lot in the JamesC hosting that went belly up, so I don't have the resources available to buy other hardware, even if I thought I might ROI without any contributions from my software. 

Now if someone could convince the manufacturers to send me a unit for me to add support, I'd certainly jump on it.

M