Topic: M's Miner (Ant/SP) Monitor v5.2: alerts,auto/mass/scheduled reboot/mobile miner - page 29. (Read 209500 times)

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.

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

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

Are they all using the latest firmware?

What does the error log show?

M

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

No, that's expected.

M

S3  - would the login page that initially comes up in place of the status page cause the error?

You're the 2nd person to report this.  I must have something broken there.  Is this an S1 or S3?

M

When using the non-api method to get the info I get in the log - and nothing in the ants tab

"04/09/2014 10:49:09: S3:1.102:80 responded with status page
04/09/2014 10:49:09: An error occurred when parsing the web output for http://192.168.1.102/cgi-bin/luci/;stok=/admin/status/minerstatus/: Object reference not set to an instance of an object."

It appears using that link even if you are logged in to your Ant it wants you to log in again

I know it's easy enough to swap to API, but if you swap from API to web then api (and then in this case back to web) the Ant section gets filled with error details rather than overwriting the bad one

http://oi61.tinypic.com/2wnsoc8.jpg

Hello, see version 3.3.  It addresses the issue with Ants not found when you enter the addresses with leading zeros, which you did by my suggestion for them to sort properly.

MAntMonitor33.zip

M

V3.2b version of the test results
253 ants around 10-12 seconds to refresh
No problems to found.

V3.2b2,V3.2 official version of the test results
I set up 24 threads, refresh time: 5-10 seconds
It can not work properly, and many machines are not shown.
Totally confused, half machine can not be found.
Please correct this problem, the speed does not necessarily to be very fast.
Stable and effective work is the best.

Mr. M, thank you for your hard work always.

I think you might have to change your refresh to every 2 seconds.  Prior to the multithreaded change, the "responded" message would be based on the round of checking all the Ants.

Now there's no longer a round.  Each time an Ant refresh completes, it checks to see how many have "" and that becomes the responded message.  Because you're running every second, there will be times when one has because it was just submitted.

M

do you mean the refresh every: or Display refresh?

Currently I have refresh every 1 seconds and display refresh 0

Try setting the display delay to 0.

M

I only have two ants but I have the refresh set at 1 second. since the update to 3.3 I get every second response only 1 of 2 responded.

Here's v3.3. 

This fixes the problem with leading zeros in Ant addresses not working.  ie, 192.168.000.091 doesn't work, but 192.168.0.91 does.
This also starts the process of removing the theoretical code to support DNS addresses instead of pure IP addresses.

Download link: MAntMonitor33.zip.

M

I confirmed, for some reason the microsoft tcpclient doesn't know what a leading zero is in IP address.

I should be able to fix this quickly.

M

Actually, I think you're saying when they are entered without the leading zeros, they work.  Otherwise they do?

M

Cool, well here's hoping I don't need to find out since I haven't seen any X's since. Which kinda sucks for being able to test it lol