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.

Thanks!

Version 2 and version 3 are two completely different versions of mango. You will have to pay for a license upgrade or a new license depending on the ts&cs

Fox

Either get more memory or try this env property:

#Set the number of files the database can have open at one time db.nosql.maxOpenFiles=500

It will close/unmap files at the expense of cpu use. If this problem persists then try another stream type:

#Query Performance Tuning, File Access Type:Available[INPUT_STREAM,FILE_CHANNEL,RANDOM_ACCESS_FILE,MAPPED_BYTE_BUFFER] db.nosql.shardStreamType=MAPPED_BYTE_BUFFER

You ever find a way? I have the same issue right now.

P.S. I also purged the /work directory, just to eliminate variables

The log files are not much help as there is only one entry in the ma.log:
INFO 2020-11-30T09:58:50,027 (com.serotonin.m2m2.Main.main:121) - Starting Mango 3.7.7 with Schema Version: 29
Let me know which ones you'd like to see the contents of and I'll post it here.

I just came accoss this same issue on one of my ES units, any thoughts?

I believe you can download older modules and manually stick them in the mango folder, however this is tedious because you need to make sure you have all of the correct modules you need for upgrading.

Fox

@mseverin did you get any further? That last log message looks like somehow you assigned the points from an Ascii File data source to an Internal Data Source. I am not aware how that could happen unless you are using the REST api and your own code, and even then this should not be possible or have executed some SQL commands on the database to move data points around?

@jared-wiltshire said in Binary Output Priority Array in BACnet and Command Null:

@techalton Phillip does not work at Infinite Automation any more.
Can you please clearly describe what you are trying to achieve. Please detail your current setup (details about your dashboards, data source, etc) and what exactly is not working the way you want.

Hi @Jared-Wiltshire

can we read BACnet priority array status as image above?

@terrypacker Now the new version working fine. I'm able to detect all my BACnet devices. thank you for your support.

I responded in this thread: https://forum.infiniteautomation.com/topic/4425/data-sources-does-not-appear

You do not need to make another thread, and certainly not if you're going to provide less information there than here.

@phildunlap said in Cannot upgrade:

administration/system/information

That was it, thanks Phil

Thanks for sharing the resource that helped you!

This thread has some information on updating Java that could be useful if Mango is being run on a lower privileged user at port 80: https://forum.infiniteautomation.com/topic/2678/java-update-encouraged

Hi charlesced, welcome to the forum!

Alas, that is absolutely no information about the problems you are having. In your emailed variant of this question, I replied all one must need do is connect the RS-485 port (if it's an RS-485 serial network), configure the BACnet local device via either the system settings page in the old UI or the local devices config in the new UI (maybe have to enable in the edit menu page and be on an up to date version), and then create a BACnet MS/TP data source on the data sources page.

But again, without a specific question or really any hint of the problem, I don't know what help to offer.

Hi Brad,

I can't say for sure what the issue would be. If you're transferring the image from one eMMC to a newer eMMC it's possible you'll need to update Linux before it will boot. There are also some hidden boot sectors that can cause issues between eMMC board revisions. Likely if you put this question to the Odroid forum, they would want to know the color of the eMMC to find the revision number and the version number / type of operating system installed.

Release is
Distributor ID: Debian
Description: Debian GNU/Linux 9.7 (stretch)
Release: 9.7
Codename: stretch

Kernel is 3.8.13.30

Alright, great help @mattfox & @Jared-Wiltshire. Thanks a lot!