It means there is an error in the start up process. Could be a port conflict, cant' find your JAVA_HOME environmental variable or a database connection issue.
If you open the terminal from the start menu: search for CMD on the start menu > right click and run as administrator.
Then CD <your mango install folder> now you can type ma-start.bat and if it errors it won't close so you can see the error in the terminal. You can copy and past if here if you can't figure out what is causing it. You can also look in your /logs/ma.log file and it should contain the error from the last start up attempt.
Sorry for the late reply on this. You can look in your ma.log file in your logs folder and it should tell you the error. Feel free to email that to: support at infiniteautomation dot com and we'll take a look at it.
Mango is indeed scalable in both dimensions. There exist users running central instances through cloud services. There are capabilities to add data collection nodes and network them to existing Mango instances, and Mango is highly threaded for vertical scaling.
As far as middleware, we're actively trying to determine what sort of middleware or message bus will be most suitable to Mango's architecture, but there is no uniform API as of yet. That doesn't affect the performance of the server, though.
And for databases we have an implementation of a embedded, NoSQL database under active development. There is also an existing implementation of Cassandra database services, although it has been sitting in the garage for a while and needs a thorough tuning before it's fit for deployment. Existing database solutions, like MySQL or Amazon's cloud database, can be sufficient for terabytes of data, depending on your use case.
Also, as Mango is capable of being deployed in configurations where servers aggregate to database servers, there is basically no limit to the quantity of data you can acquire. These questions fundamentally rely on your use case and the structure of how you intend to use the data. While Mango could function in a swarm configuration, it requires a slightly different set of considerations than a hierarchical aggregation of data.
I got it to work. It is nothing on your end. Long story short, the quad wireless is uber-slow and when I copied the m2m2 content from a NAS I thought everything was copied over. It looked like it was complete. Anyway, not all files where there hence the problem. The core works (started without error and can login ) on JDk 1.70_45 (soft float) and Java 6 open JDK-Armel.
I was hoping not have to go down the JDK 8 route as there is no soft-float release from what I can see.
Depending on your DGLux licensing, you can either save the dashboard to disk and reopen it elsewhere, or you can directly copy the dgml files over. They can be found in MANGO_HOME/web/modules/dglux/web/dgml
I greatly appreciate your help! I have no errors when trying to create a modbus serial data source now. I placed the files into the correct java folders, however I didn't realize that I needed to place into Mango/overrides.
Hard to know with out a bit more information. I would recommend starting over with fresh files, make sure you have the latest version. M2M2_HOME is not needed any more and was for an older version, just JAVA_HOME.
You can also call in for support if you need some live help.
I am having the same issue where mango seems to run on Derby but not mysql. We have a similar configuration on another machine that works, and comparing apples to apples, it all looks the same. This is the error I get:
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/comms/httpclient/Credentials at com.serotonin.m2m2.Main.main(Main.java:63)
the db user created to access mysql has the GRANT ALL privileges so no access restrictions.
I'm not having luck installing Mango on a Mac OSX 10.5.8 with Java 1.6.0. File name was changed from "ma-start.sh" to "ma-start.command". Line 15 was changed from "ma-start.sh" to "ma-start.command". "chmod +x ma-start.command" was executed via terminal to gain access to the file. The following was returned in the terminal window upon execution of "ma-start.command":
Applications/Mango/ma-start.command ; exit;
Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.security.AccessController.doPrivileged(Native Method)