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.

My only thought is maybe some additional high priority threads may be required to help smack out the calcs.
Alternatively have two scripted datasources updating a single virtual datapoint. That way they can fire independently of each other.
These are just ideas, I'm not sure what else to suggest.

I have discovered that the system-timesyncd service is installed and runs out of the box (on the mangoGT). It's not able to sync for us with the default debian servers due to firewall restrictions. I just needed to put our local ntp servers in /etc/system/timesyncd.conf and it works fine.

Thanks

Wow, you're correct

Just press ENTER !

Didn't press ENTER, just SAVE.

Thanks

At this point it will be part of Mango 4.0 which will come out in the next few months. We are currently working towards that release.

@MattFox - Case closed. I stupidly put a non-specific div {...text-align:center}in one of my css files. Probably would have caught that, but the ace_text-layer width (& height) is set at 1000000px in ace/css/ace_editor.css, and height is further set to 1e+06px inline.

After much searching, I'm unable to find an example of why one would want to do that - although there must be one! Interestingly Chrome was rendering veeerrry slowly - when I lowered the width to 10000px, it sped up markedly.

I've still got the API dropping in and out, can't always log in. Can I get someone to remote in and take a look?

Fox

will do. thanks... and nothing there should be construed as in any way critical!

This is working now. I think the main issue was simply that 'DHCP' needs to be upper case. Other things I noticed were that the script takes about 1 minute to complete, the LED's do NOT go off (even after about an hour) and the mango needs to be rebooted (it does not need a reboot when changing to a fixed IP address).

Oh well, I'm sorry but I take it back, seems like we can't stop the loop, even with the Log4j approach we are still getting thousands of events. More than 24,000 in a couple of hours. Most of them are like this:

ERROR 2019-10-29T11:44:19,621 (com.infiniteautomation.mango.slack.event.SlackMessageEventHandlerRT.postMessage:145) - Slack message failed to send java.net.ConnectException: ratelimited at com.ullink.slack.simpleslackapi.impl.SlackWebSocketSessionImpl.connectImpl(SlackWebSocketSessionImpl.java:338) ~[?:?] at com.ullink.slack.simpleslackapi.impl.SlackWebSocketSessionImpl.connect(SlackWebSocketSessionImpl.java:292) ~[?:?] at com.infiniteautomation.mango.slack.event.SlackMessageEventHandlerRT.postMessage(SlackMessageEventHandlerRT.java:122) ~[?:?] at com.infiniteautomation.mango.slack.event.SlackMessageEventHandlerRT.eventRaised(SlackMessageEventHandlerRT.java:67) ~[?:?] at com.serotonin.m2m2.rt.EventManagerImpl.handleRaiseEvent(EventManagerImpl.java:1048) ~[mango-3.6.4.jar:?] at com.serotonin.m2m2.rt.EventManagerImpl.raiseEvent(EventManagerImpl.java:243) ~[mango-3.6.4.jar:?] at com.serotonin.m2m2.rt.event.detectors.PointEventDetectorRT.raiseEvent(PointEventDetectorRT.java:43) ~[mango-3.6.4.jar:?] at com.serotonin.m2m2.rt.event.detectors.PointChangeDetectorRT.pointChanged(PointChangeDetectorRT.java:54) ~[mango-3.6.4.jar:?] at com.serotonin.m2m2.rt.dataImage.DataPointRT$EventNotifyWorkItem.execute(DataPointRT.java:817) ~[mango-3.6.4.jar:?] at com.serotonin.m2m2.rt.maint.BackgroundProcessingImpl$RejectableWorkItemRunnable.run(BackgroundProcessingImpl.java:632) ~[mango-3.6.4.jar:?] at com.serotonin.timer.Task.runTask(Task.java:179) ~[mango-3.6.4.jar:?] at com.serotonin.timer.TaskWrapper.run(TaskWrapper.java:23) ~[mango-3.6.4.jar:?] at com.serotonin.timer.OrderedThreadPoolExecutor$OrderedTaskCollection.run(OrderedThreadPoolExecutor.java:336) ~[mango-3.6.4.jar:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_172] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_172] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_172]

Couldn't find out what is triggering these changes that raise the event detector.

Tried turning off the "Error" data point but now the "Warning" one is also sending weird messages, like this one:

WARN 2019-10-29T12:01:45,429 (com.serotonin.m2m2.web.dwr.MiscDwr.jsError:167) - Javascript error Description: Error: Tried to register widget with id==chartRendererSelect but that id is already registered Page: http://192.168.100.33:8088/resources/dojo/dojo.js?v=1571864830 line 345 > Function line 3 > eval Line: 2 Browser name: Firefox Browser version: 71 osName: Windows location: http://192.168.100.33:8088/data_source_edit.shtm?dsid=498 @ Oct 29, 2019 12:01 PM

We are getting this message when we try to edit the Log4j data points in the old UI (so we can access the event detectors and the purge now button). Explanation below:

Strangely, when we try to edit the data source in the old UI, the "Data points" tab is not existent inside the data source. So I look for the points in the global "Data points" tab, where all data points appear, I filter them by name to find the Log4j Slack Messages Data Points, but most times, when I click the edit (pencil) button on any of the 4 data points, I only get the above "Warning" message in Slack and this same message on a blue box in the old UI:

Error: Tried to register widget with id==chartRendererSelect but that id is already registered

It works super randomly; I seldom get to edit the data point. It's a strange behaviour, something I never saw before with any other data source. I did add the line @terrypacker suggested in the log4j2.xml, inside the loggers section, and restarted it btw.

Is there a quick fix to this? Thanks!

Hi cwangv,

If you open the browser's developer tools, you can see the actual request being made has a "fields" property in the POST payload. If you were to make the rest request for the data yourself, you could modify what fields are in the resulting response.

Alas I do not believe tags are currently available to be included as an available field, though.

Hi cwangv,

Thanks for bringing this to our attention!

@fleh said in Bug with amcharts(?): Preview works but page view does not:

I actually wanted to emphasize how much I appreciate your forum support. Many help pages are really good and the coverage with video tutorials is excellent to get an overview.

Thanks!

@fleh said in Bug with amcharts(?): Preview works but page view does not:

I spent quite a bit of time on issues already which where incomplete or missed critical info. For example, the help pages for egauge, egauge datapoint, Environment Canada Data Point, ""Environment Canada"", M Bus, and M Bus datapoint simply went AWOL..

I will check up on those. I am not sure that the Environment Canada DS is still supported, it is a very niche data source that can easily be replaced with a HTTP data source.

@fleh said in Bug with amcharts(?): Preview works but page view does not:

Thanks for the user module @Jared-Wiltshire! It does not work when copying it into a new page for me, but I'll go through it line-by-line to see what its purpose is. Have a nice weekend, y'all!

It doesn't go directly into the page markup, you save it into a .js file and reference it from UI Settings -
https://help.infiniteautomation.com/getting-started-with-a-user-module

Basically it defines a new component, then you use the component inside your page. e.g.

<my-chart point-values="pointvalues"></my-chart>

Phil:

I discovered something that might be helpful with locating the cause of the issue with multistate data points in virtual data sources.

It only seems to fail to properly save the state values and start value when the change type is set to "no change".

@phildunlap
good on you, Phil.
it is working.
Thanks.

Hi Brian,

Thanks for bringing this to our attention, I have created a git issue about it.

Ah!! I was not following that sequence. I was inputting the key name, but then hitting save. I thought the + button was to add an additional tag not to continue with the current one.

I now have tags. Thanks so much for the reply!

Peace

-Dave

@Jared-Wiltshire Thanks for the heads up and the swift response, I'll let my admin know about module update.

@phildunlap Thanks for the welcome!

That is a kind sentiment to share, surely!

Hi everyone,

Thank you for all the advice. The information is very helpful.

Best regards
Ramhuzaini