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.

One other note on this.

I found the following info on the 65533 value/� symbol:

U+FFFD (decimal 65533) is the "replacement character". When a decoder encounters an invalid sequence of bytes, it may (depending on its configuration) substitute � for the corrupt sequence and continue.

One common reason for a "corrupt" sequence is that the wrong decoder has been applied.

@ricardo said in Which NoSQL is used by Mango?:

@craigweb Is timeScaleDatabase ready? Any material on how to use it? I am interested in hosting the DB for the point values on another server apart from the application server.

Hi Ricardo,

Sorry to bear disappointing news, but no, the Timescale module is not ready for use. It was developed for a very specific internal use case and was never intended to be released as a general purpose module.

However we are currently developing support for other time series databases, it is very likely this will include Timescale support. I cannot give you 100% confirmation on this, or a release date, but it should ship with Mango 4.3 when it is released.

-Jared

Hi Joel,

is there already a release date for the OPC UA module?
Any beta-version we can test?

@Ricardo thanks, that all looks ok to me. Basically what is happening is that Mango uses a pool of TCP/IP connections to the database and when choosing one to use it tests it first to ensure it is still connected. In this case Mango sees that the connection is broken and the database pool library (Hikari) is logging that.

For some reason the database connections that Mango is opening are being closed. This is not normal. From your log posting I can see that the delay is pretty close to 10 minutes, so I would be looking for any settings between Mango and your MySQL server that timeout at 10 minutes. It is possible you have a Proxy or Firewall between the 2 that is severing the connections at 10 minutes...

If none of that helps then I suggest you post the mango.properties for your database. The begin like this:

# MySQL database settings. Your MySQL instance must already be running and configured before this can be used. db.type=mysql ...

Hi Everyone. As promised we have added Series 4 pricing to the radixiot.com website. You can find it under Products / Pricing. At this point, it is a direct PDF, but as we have eluded to we have a 100% new website coming out hopefully in the next month that merges all of the other websites into one resource, and this will include an interactive pricing page.

You can also directly link to the pricing here:
https://radixiot.com/wp-content/uploads/2021/10/mango_v12.0_pricing_guide-FINALa.pdf

@jared-wiltshire Since I cannot do database conversion, I tried reinstalling mango via the script again and was successful after creating the .mylogin.cnf file for the root account.

sudo -s
mysql_config_editor set --host=...

Thanks for your help!

@jared-wiltshire

Yep, that did it, thanks!

@cmusselm
that is a good outcome! Thanks for the update.

Hi Guys, Thanks for your pointers I manageed to get it sorted. Looking at the log it is using
$mango_paths_data/mango.properties. By default after installation it was running SSL. I had commented out the SSL keystore location and password lines, added web.port=8080 and changed ssl.on=true to ssl.on=false - That was where the issue was. I commented out the ssl.on line - did a restart and all runs well with port 8080

@jared-wiltshire Oh I know... that's a whole other issue. I'm painfully aware how silly this is!

Hi, Terry,

Is the comment you made here: https://forum.mango-os.com/topic/4691/virtual-serial-client/24 still valid? This seems like the exact situation we have.

This device is a black box, and cannot connect to our IP:port, we have to open a socket to it and just listen to capture packets that it sends out. Based on your note, it sounds like using a Virtual Serial Client with a Serial data source won't work.

If that's the case, is the only real solution to create some middleware/applet that connects to the host and reads the data, then pass it along to Mango in a way it can read?

We thought that if the device passes data every 6 seconds, and we use a TCP/IP Data Source to poll it every 3 seconds, we'd be guaranteed to get all of the packets, but that actually made the results worse, and we got fewer packets than when we had it polling every 6.3 seconds. (Don't know why adding the 0.3 seconds makes a difference, but it definitely does.)

Thanks,
Chad

I am trying to connect mango to AWS IoT using the MQTT client module. I faced problem connecting to AWS. The reason being I am not able to attach the 3 certificates provided by AWS. Will there be plans to support this feature?

@dan I have the same issue after updating Mango to the core v3.7.7
Chrome version is 92.0.4515.131 (Official Build) (64-bit)

When I switch to the old interface and switch to the Datasources tab, the list of data sources does not appear, just the empty white space. The data point tab works well. In the new interface, everything is alright.

When checking the browser's console I found there a bunch of errors like this ones:

Note: The actual IP address is removed and changed with <IP_address> tag.

DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/layout/TabController.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/layout/StackController.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/Menu.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/DropDownMenu.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/_MenuBase.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/_KeyNavContainer.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/_KeyNavMixin.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/MenuItem.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/layout/ScrollingTabController.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/PopupMenuItem.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/_WidgetsInTemplateMixin.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/CheckedMenuItem.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/MenuSeparator.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

@robmalone said in SSL/HTTP Post error:

Once the Mango environmental properties file was pointing to the keystore it worked.

So you are all good now? Or still having issues? If you are still stuck you should follow the recommendations in that StackTrace link about enabling SSL logging by adding this to the java command that is starting mango:

-Djavax.net.debug=SSL

And seeing what the details of the problem are.

@holzatelier Just a little update on this.
It seems the data points are indeed updated on my system when timestamps are passed along with the JSON data. What I didn't realize is that if the timestamp predates the last entry in the point value history then the browser window needs to be refreshed to show the added historic data value.

So this works for me now besides the missing JSON parsing Error.

Thank you again for your attention.