@terrypacker
Thanks for the information. This is a pretty major thing to remove. Will you be building tools to port across the tree structure into tags? If not, I can't see us ever upgrading to 4.0.

Andrew

Hi

We are trialling Mango 3.7 and have noticed the Data Point Hierarchy has some support in the new front-end, but the Data Point Hierarchy page has not been created in the new UI. We also heard rumours last year that the DP hierarchy was planned to be dropped in favour of just using tags. We find the DP hierarchy very useful and would like to clarify IA's roadmap for it.

Can someone please clarify the roadmap for the Data Point Hierarchy?

If the standard System data source that reads from "/opt/info/systemInfo.txt " happens to start up a couple of seconds after a whole or half minute boundary, an event with the following text can be generated several times an hour:
"'MangoGT System': File not found: /opt/info/systemInfo.txt (No such file or directory)".
This appears to be a timing issue - it's likely to occur because/when the script happens to be deleting the old file and renaming the temp file (systemInfo-new.txt). We have seen this on both ES and GT mangoes.
Can something be done to the default configuration for this DS to avoid this occurring?

Thanks Terry
Yes, I did find that recently, and it does help.
Andrew

Anyone?

I'm happy to be corrected by someone from IA, but I believe the best current info on the GT mango is at:
https://static1.squarespace.com/static/58d15f4a6b8f5bad3a9a578c/t/5e3331733e07947c1b1619bf/1580413303213/MangoGT+Spec.pdf

You may already be aware, but there are several settings on the "Administration -> System Settings -> Mango ES Configuration" page that display '*' even though they have settings when you go to the corresponding page in the old UI.
Settings we have noticed missing or different in the new UI:
eth0:
IPv4 (most important for us): Gateway, DNS servers missing
IPv6: Address is displayed, but it seems to be the hardware address.
wlan0:
IPv4: subnet mask
IPv6: subnet prefix length

Also, the title "Mango ES Configuration" should probably be updated.

Hi
Have you had any luck with this?
Andrew

Are you please able to provide any details about the security concerns?

Hi Matt

Sorry, I don't have a link. Hopefully someone from IA can provide some information.

Andrew

Thanks Dave

Hi
I'm using mango 3.5.
I have a meta data that contains a (calculated) data point that combines 2 data point values. Each of these 2 data points has 'Update context' ticked. I have discovered that if the 2 points are updated within about 3 seconds, the script is NOT triggered when the second data point is updated. I think I can work around this by setting the Execution delay to be at least 4 seconds.
Is this expected behaviour?

I have performed further testing and found the above script needs an Execution delay of at least about 5 seconds to work. This is because if the 2 source data points update within a few seconds, the script is only triggered when the first one is updated, not the second one (ie the script won't trigger again within a few seconds of it running).
Unfortunately, further testing has indicated that the script no longer works reliably where there is a comms outage causing a delay in some of the data.

Hi
Are there any updates on this please?
Thanks

If you are looking at the HTS units, I'd recommend you also look at the new GT mangoes. We are trialling some now with the view to use these instead of the ES mangoes in the future. The GT's have lower processing power, but a higher temp rating and no fan (which we have found to be a common point of failure in some conditions).

Hi Joel

It's only the config DB that's regenerated, not the time series DB. We have done it several times when the config DB has blown out to about 100 times the normal size and we haven't lost any of the time series data. Having said that, starting in Safe Mode sounds like a good idea. I'll give it a try next time.

mseverin - see https://help.infiniteautomation.com/starting-in-safe-mode/

I have discovered that the system-timesyncd service is installed and runs out of the box (on the mangoGT). It's not able to sync for us with the default debian servers due to firewall restrictions. I just needed to put our local ntp servers in /etc/system/timesyncd.conf and it works fine.

Thanks

I had a similar problem, but with a publisher. I disabled the publisher that was generating the events (immediately after a restart was easiest). The system was then stable/responsive enough for me to get to and click on "purge all events".

If this doesn't work, you could try this (assuming h2) [you may want to confirm with someone from IA first]:

• stop mango
• rename the config file (/opt/mango/databases/mah2.h2.db)
• download and edit the most recent config backup json file to set enabled=false for the problem component(s)
• start mango (this will generate a new out-of-the -box config)
• login with the default admin login (the other logins will have been cleared)
• go to "Administration -> Configuration import/export", click "upload json file" and upload the file you modified.
• probably restart mango from the Modules page
• if this fails and you need to roll back, simply stop mango, rename the config files back as they were and start mango again.
  I think this will effectively purge all the events, but if not, the system should then be responsive enough to do that. As a bonus, this can significantly reduce the size of the h2 config DB.

Good luck.
Andrew

Hi
We used the ntp service on the mangoES devices for time syncing. We just had to update /etc/ntp.conf with our internal ntp server ip addresses.
It looks like the ntp service/daemon isn't available on the GT mangoes. I have tried running 'sudo apt install ntp', but It's getting blocked by the firewall. Do you have a recommended way to set up time syncing on the mangoGT?

I'm thinking now that the problem was with the data point 'MangoES_Disk_Percent_Used'. This fails to import, then all the watch lists, event handlers, etc that are linked to it also fail. It appears this also causes the entire DP hierarchy to fail to load. I believe I'll need to remove all references to this DP from the json file before importing. I understand tha a DP starting 'mangoES' doesn't belong on a GT mango, but there are other points like this (eg MangoES_Disk_Space_Remaining) that seem to be imported OK. Is there something in the import processing that's preventing 'MangoES_Disk_Percent_Used' from being created?