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.

I just thought of another possibility. Mango 3.x uses Log4J2 where previous versions of Mango used Log4j. If you have a log4j jar that is getting loaded it won't pickup the log42.xml configuration and would probably use some default of only printing to stdout. I would check your <ma-home>/lib folder and see if there are log4j and log4j2 jars. ls <ma-home>/lib/*log4j* This should list only these jars: lib/log4j-api-2.10.0.jar lib/log4j-jcl-2.10.0.jar lib/log4j-core-2.10.0.jar lib/log4j-slf4j-impl-2.10.0.jar

I had missed setting the permission for the JSON store UI pages and UI menus as you suggested. Thanks Phil.

Was there any more info available with regards to LDAP availability? @Jared-Wiltshire

@MStangl You can create a PowerShell script which you schedule on your Windows server. I started with a snippet created by the Chrome DevTools, you go to the network tab and find the API request and copy the network request as shown below. [image: 3Kt8ZKh.png] You just need to create an authentication token (on your users page) and add it as a header as shown below. Invoke-WebRequest ` -Uri "http://yourmangohostname:8080/rest/v2/point-values/single-array/time-period" ` -Method "POST" ` -Headers @{"Accept"="text/csv"; "Authorization"="Bearer yourlongtokenthatyougenerated"} ` -ContentType "application/json;charset=UTF-8" ` -Body "{`"dateTimeFormat`":`"yyyy-MM-dd'T'HH:mm:ss.SSSXXX`",`"from`":`"2018-10-23T21:54:58.951Z`",`"to`":`"2018-10-24T21:54:58.952Z`",`"bookend`":true,`"timezone`":`"UTC`",`"fields`":[`"TIMESTAMP`",`"VALUE`"],`"xids`":[`"DP_9004cb57-f1cb-4415-a078-b60999f06c4d`",`"DP_cd2587fa-93ab-492a-9963-e9f5c4e0a40d`",`"DP_915fb444-6133-45eb-a700-4f415662e108`",`"DP_506cab2d-8f10-46ca-90aa-ff9d8f6c0400`"]}" ` -OutFile "myData.csv" You will just need to modify the script so that it gets data relative to the time it runs at and names the output file accordingly. And also obviously make it get the XIDs you are interested in.

@pspivey said in Point value may not be reliable: will i be able to fix the issue on a V2 mango without upgrading to V3? I suggested a fix for backwards compatibility with v2 publishers to one of our developers who was working on it. I'll see what became of it.

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.