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

Hello, M

M's Ant Monitor It’s very good software, for thanks your and support your hard working, my boss (Mr. Wu, P2POOL first count force 1PGwNprChx745u6XdbcHttf7Y2MAaqXhsF) has sent 1BTC to 1PA1sji28iztspKxDquwFrNjp5SksjkCHE, please check.  

Currently, we have 1,000 ants S3, core switches do VLAN (currently four network segments), each network segment 253 mining machine.

Automatic search does not support multi-VLAN network segment, there is a little pain, can only add IP manually, if you add 1,000 mining machine, the software  refresh rate takes about 20 minutes,it is very slow….
At present our solution: use a computer to do the monitoring, using VMware made 4 XP virtual machine, a virtual machine a network monitoring. 253 machine default 300 seconds to refresh once, one second countdown began refresh mining machine working condition, this process takes four minutes to complete, after which the software restore 300 seconds countdown.
We hope that the software refresh rate can be faster, and VLAN support multi-segment search.
Another registry problems, such as adding a 1000 mining machine, then after I deleted 750 mining machine.but monitoring page still shows 1000, Delete is displayed as “? ? ?”. I must remove HKEY_CURRENT_USER \ software \ mantmonitor in the registry, and then re-add the IP. A little painful.
After the restart monitoring software MAntMonitor this IP order is chaos, can we order like 192.168.1.2 - 253?

IT people want to see this network!

1000?  Okay, timing is everything, I was just told I might want to multithread it.  Now it's obvious I do.


I'll see what I can do.

You can only get 250 or so per subnet.  How many subnets are you using?


Can you post a screenshot?  A picture is worth 1000 words.

M

Hello Mr. M

May I ask how many support the mining machine?

I tried a bit,

P2POOL first operator force,

1000 mining machine,  

OMG, the software is very slow reaction, there is no way to work properly.  



If you can solve this problem, the boss is willing to donate.  

Your wallet address? 1PA1sji28iztspKxDquwFrNjp5SksjkCHE

Registry

Really a lot of trouble

Minerals can not be deleted after an error

Sorry

Google Translation

Writing to an INI file isn't as easy as it used to be.  See point #1 .. using the registry is easy for me.

Ants shouldn't be regularly failing to respond.  Again, that's out of the ordinary processing. 


I thought I did have everything wrapped in try/catch routines, especially when an Ant fails to respond.  Are you using v3.1?  I think it was 2.9 or so that I found I had broken the exception handling around unresponsive Ants and fixed it.

M

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at MAntMonitor.frmMain.HandleAlerts()
   at MAntMonitor.frmMain.RefreshGrid()
   at MAntMonitor.frmMain.Form1_Load(Object sender, EventArgs e)
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34014 built by: FX45W81RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
MAntMonitor
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/jbdevu/Desktop/antmonitor/MAntMonitor.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 12.0.20806.33440 built by: FX45W81RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34003 built by: FX45W81RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml

opening a file in notepad is easier than using regedit and finding the right registry entries. A lot if the time when a ant fails to respond it hangs the UI, I can't remove it from the config screen.

also when the ant fails to respond it has an uncaught exception, I can hit continue and it'll keep running until the next uncaught exception.

you can add something to catch all exceptions at the application level, so you won't have any uncaught exceptions that crash the app.

This is my first time using this program.

Thanks for the feedback.  I'm familiar with multithreading and the advantages it adds.  And the complexity it adds.  (I have been programming on the side for 20 years now..)

There shouldn't be too much of a UI being frozen problem for normal API calls.  If an Ant doesn't respond, it should timeout fairly quickly.  I set the timeout lower purposely for that reason.  Also, you shouldn't regularly have Ants not responding.  That's an exception case, I don't see too much reason to put too much effort into that.

The "scanning" piece is awful, and will make the UI virtually unusable until it's finished.  I've never revisited that code since the original design.  It could be much better.  But I figure it's a one time deal for most people, and you can always enter your Ant info manually if you need to.

I use the registry for a two reasons:

1 - it's easy to do
2 - it's easy to view/edit outside of the app

If you're familiar with the registry, it's easy to export it and import it to another machine.

That said, I never considered multithreading anything, or using anything other than the registry for storing the config.

Thanks again for the input.

M

I understand, its very useful app. I'm having a lot of usability problems.

a couple things off the top of my head.

can you make each query for data from the ants run in its own thread, or in newer versions if .net a worker process makes multithreading easy. This would stop the UI from being froze. Waiting for data to come back and or breaking the UI when a ant fails to respond.

also saving data in the registry could be much better if you serialized the data objects into json or XML and asaved on disk. You could transfer the config file to other machines and if you don't want people messing with it you can binaryserialize it.

overall the app I'd a great idea and I like using it. I'm typing this from my phone so excuse the typos and stuff

Of course. 

Keep in mind I threw this together in my spare time.  It started out as a quick way for me to monitor my ants.  It was originally designed for web scraping.  Once I learned the API was available, it was added.  It's not like this was designed from scratch to be as it is .. that's why it's at v3.1.

M

are you open to constructive criticism from a software architect?

I might have broken something.  I'll have to test this.

Have you used this before?  Or is this your first time?

M

Here's the error I received in detail:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at MAntMonitor.ControlsByRegistry.SetRegKeyByControl(CheckedListBox& chkLstAny)
   at MAntMonitor.frmMain.cmdSaveConfig_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18444 built by: FX451RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
MAntMonitor
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///D:/Users/XXXXXX/XXXXXXXXXXXX/XXXXXXXX/MAntMonitor.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 11.0.50938.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34108 built by: FX45W81RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
Newtonsoft.Json
    Assembly Version: 6.0.0.0
    Win32 Version: 6.0.4.17603
    CodeBase: file:///D:/Users/XXXXXX/XXXXXXXXXXXX/XXXXXXXX/Newtonsoft.Json.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:


   


When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


Sorry for the long amounts of text, there doesn't seem to be a spoiler button on the forum.

I don't get it.  It works properly for me.  Can you PM me a screen shot?

M

Can you post the top part of the error?

M

Really useful program for monitoring my S1. One problem I'm having though, when I try to save my configuration, I get an unhandled exception error, and it doesn't save. Does anyone have any ideas on fixing this issue?

On the main "page" where all the stats are seen.

Maybe it's a web scraping thing but it shows the full link crap.

It works.

M

Any word on the new antminer s3 firmware working with this software?