Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Copying Internal system datasource
-
I noticed this in the data source under available upgrades point ... "Missing monitor with id com.serotonin.m2m2.rt.maint.UpgradeCheck.COUNT"
Can I export this Mango Internal ds from another enterprise system and delete and import it back in to this one? Or is this indicative of another issue as it complains when I check for upgrades ... "Could not resolve host, check your DNS or internet connection.. store.infiniteautomation.com temporary failure in name resolution" -
Phillip,
Yes this is a direct result of the "Could not resolve host..." failure message. That monitor only gets initialized after a successful request of available upgrades. Obviously that Mango cannot connect to the store, so once you sort out that problem the monitor point will become available.
-
This upgrade issue relates to how the licence was generated a couple months ago. At that time we asked Phil to provide an enterprise licence for a cloud server. Phil said he didn't have the details about the system licence we purchased and I told him it was an enterprise so he created something he called a "free" licence for the GUID I sent over. From the system, I was not able to get the store to find the licence but I went to the store and downloaded the xml for that GUID it worked to licence the system. Since then I have had to upgrade by putting the core.zip in the root and restarting. How would you suggest I go about resolving the issue?
-
To get the monitor point to show up correctly Mango must be able to connect to the Store and request if there are upgrades available. I will discuss a better way to handle this situation with our developers but setting the value to 0 on a failed request is not an option as it is misleading and Mango is not able to log a null value.
