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.

On Sunday I will try these solutions and I will tell you what I will get .
Thank you very very much :)

@glamprecht There should be an error logged in your ma.log file (find it under System Status in the Administration menu). Please post this.

You can try using the "Bulk data point edit" page in the new UI if you are on a recent version of Mango.

Hi Alex,

No, that's isn't possible. You could have a naming schema or XID schema that made filtering the do-not-publish points out of the publisher's "Add points" table, but there is no way to exclude them entirely from that list.

@phildunlap Thank you for your help! :)

Thanks for sharing the resolution Bryce! Keeping the pointValues table in check is definitely a necessity for users who don't have the NoSQL module!

We moved to email, but the next version of MangoNoSql, 3.5.1, will improve the handling of corruption in the database that is to be merged. This is what caused the buffer overflow exception at the end of the log, and the returning to IDLE state before finishing all the data points.

Sorry I keep pasting the entire file within the post, if there's a better way to share it please let me know.

Tis better to log the whole log than no log at all!

I would think so. Cache control on the functions was added in 3.5. Prior to that they were always using the cache.

By default the client should forward port 22 for SSH which you will need to change to 2222 for a MangoES yes.

The web port should default to forwarding the non-SSL web port from the env.properties file however.

Okay great!

Yeah I've never seen this error since we got Mango, for all these years.

Nicely done!
I'll get an ES updated and will test with my code.

@phildunlap
Hi Philip,
convert functions into my select statement work!

Thanks
Ste

Thanks Craig!

Alex,

Are virtual data points different than meta data points?

Yes, briefly,

Virtual points can:

Have simple change types to simulate data easier. Performs a 'change' when refresh point value is called Not be polled so that they're only user updated (data source setting)

While Meta points can

Have a script executed on cron patterns or from point events (updated, changed, logged) Have a script executed when the point's value is refreshed return UNCHANGED; to not update their value

So very different!

Hey Phillip,

If you inadvertently have both the client and server set to start with Mango and cause Mango to restart neither the client or server will have public keys available. You will also see CloudConnectServer errors in the logs for bind exception.

Hi Ricardo,

There is not a setting to modify how that duration is formatted currently.

If one wanted to achieve something like this, they could create a modified, custom version of the <ma-events-table></ma-events-table> directive and modify the Moment.js function invoked on the duration in the durationFilter.js from 'humanize' at https://github.com/infiniteautomation/ma-dashboards/blob/main/UI/web-src/ngMango/directives/eventsTable.html#L72 to a function that results in the format you seek. Then you could use this modified directive (you'd have to give it a different name) on custom pages.

Hi ricardo,

Yes the HTTP receiver still works through https

I just tested a Mango running with a selfsigned certificate and I was able to get values into my JSON receiver point with identifier /key by both

#HttpPost.txt POST /httpds HTTP/1.1 User-Agent: Mango M2M2 HTTP Sender publisher Content-Length: 15 Content-Type: application/json Host: localhost:8088 Connection: Keep-Alive {"key":"value"}

nc 127.0.0.1 8080 < HttPost.txt

and via curl to the SSL port,

curl -v -k -H "Content-Type: application/json" -d "{\"key\":\"value2\"}" https://127.0.0.1:8443/httpds

Note that I'm using 127.0.0.1 instead of localhost, which can resolve to ::1 which doesn't pass the whitelist check. Whitelisting for IPv6 addresses was added to Mango 3.5 but the entry *:*:*:*:*:*:*:* is not present by default yet.

I think it's more a working understanding of how things seem to happen around here. :)

I adjusted the purge settings down to 6 months, ran the purge and have told the people who watch the Mango to adjust the settings to it fits their needs, but to be aware of if they set it back to a year, chances are it will fill up again.

We shall see how it goes.