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 think so, but not sure why we wouldn't see it as well. Maybe a plugin or something? Can you check the SVG to see if that downloaded a zero pixel plot area (i.e. the <svg> opening tag's height and width are 0)? Maybe try clearing the browser cache?

Feel free to get things running again. The only thing that occurs to me is that the Mango/databases/mangoTSDB/*/{dataPointId}/{lastShardNumber}.data.rev file could be interesting, but if you already read from the point or whatnot that may have been repaired if it was to do with corruption. You would see something about that data point ID in the Mango/logs/iastsdb-corruption.log file if it had something to do with corruption. May be interesting to check that, too.

@CraigWeb I agree and actually right after I made my previous post took a deeper look into what is going on with the internals of our Units library. I think something isn't working quite right with our Unit Aliases so I opened this issue: https://github.com/infiniteautomation/ma-core-public/issues/1331

Hi Phil, This was on mango 3 at all times. I had upgraded to the latest mango 3 a week ago after the problem happened the first time. I have just upgraded the mangoNoSQL module. No update to the excel reports appeared in the list of newly released modules. We will make sure to upgrade all of the MangoES with version 2.8 to the latest 2.8 as well. Thanks for such a quick turn around!

Hi Craig, To add to what Joel said, None level events are recorded in the database. Whether or not anything will appear in ma.log will depend on the Log4j configuration you are using, more likely.

We have just released a new version of the MangoNoSQL module that has finer grained purging. So basically you can now accurately purge down to a one day level. This setting is not enabled by default for periods larger than about 25 days but can be enabled by checking the Purge within shards checkbox on the System settings page in the Mango NoSQL Information area. Excerpt from help file: Purge within shards This setting governs if the purge task will delete values from within a shard file. With this unchecked, purges are much faster because data is purged in whole shards as opposed to excising individual samples. If the purge period is smaller than a single shard (about 25 days), however, the data older than the purge configuration is deleted from all shards, regardless of this setting.

I'll try to check tomorrow when I'm back there

any fanless hardware on the horizon?

Craig, Currently the REST api does not support image data types. We are adding support for Image data types to the NoSQL point value store for Mango 2.8.0. It makes sense to implement all the REST api functionality for Image data types at the same time so we can bundle the testing. I've created a git issue to track our progress here: https://github.com/infiniteautomation/ma-core-public/issues/719 Thanks, Terry

Hi psysak, Thanks for bringing this to our attention. That will be fixed in Mango 3.4 Just checking, but this was in the emailed report, correct?

It is released.

Hi Phil, There are no report instances that we wish to save, they go out by e-mail and that is the end of them so for the time being i will have to remember to wipe the databases/reports directory every month. It seems you have already identified a fix in the github issue so hopefully it gets some attention for a release in the next couple months. thanks both for your time and assistance

@terrypacker Thanks for the update. Please keep in mind that this problem is not unique to my installation.

We are working to replace the JFreeCharts with the new AmCharts found in the DataPointDetails module. The new charts use new methodology to generate the data which include 'rollups'. Rollups allow you to request data placed into bins. So for example you could request the past 24hrs worth of data averaged at 10 minute intervals.

Yes, not using the NoSQL module will help, because the NoSQL module tries to store all pointValues (including Image pointValues) but the support for images was never added. i believe using MySQL or H2 will solve the problem. It is a fairly simple thing to add the functionality from the SQL Point Value Dao to the NoSQL if that gets traction. We'll keep you posted.

removing the excelReports module solved the issue.

Yes, this is the correct fix. It already made it into 1.13.x, but didn't make it back into 1.12.x.

When I create a new datapoint on a virtual or vmstat data source (but not modbus), there is an error that occurs with current version of chrome (20) but not firefox (13) "can't read property 'style' of null" is the error message, it comes from engine.js. I tried upgrading to dwr 2.0.10 and this didn't resolve, and dwr 3.0 was more than a straight drop in. Chrome 20 with mango 1.7 exhibit the same problem, but I don't believe I ran in to this problem with earlier versions of chrome.

I had the same problem in mango 1.12.3 and I solved it using the Derby.jar file from mango 1.12.5

updated patch against mango 1.12.4. the filedata one places the files in dated directories of the format YYYY/YYYY-MM-DD so I don't have thousands of images in a single directory in 10 years Attachment: download link