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.

Ah good idea man, mondays... EDIT: 220 smtp.gmail.com ESMTP x15sm16801291pfa.80 - gsmtp I get the feeling this is JDK related...

Hi @cwangv This has been fixed in 3.7 and on a beta version that has not been released yet. As Fox mentioned you will need to use another browser if it is affecting you. Thank you for the feedback tho.

Wanted to give a quick update to let others know how this was resolved. After working with the support team (thanks, Craig!) we found it it was a licensing issue. Once our license was updated and applied everything worked as expected.

Not really possible right now but I do like the idea. I have seen other systems use a "burst logging" where the value gets logged on change when it is over or under a certain limit.

Hi Ralf Untill the next beta is released you can use Firefox which does not have the bug.

Has anyone been able to duplicate this? Any other thoughts or theories? Suggestions, what should I try?

After some more experience, going through this several more times, I seem to have found a pattern. Apparently, this kind of problem arises when I reboot the MangoGT without explicitly stopping Mango first. Having examined the output from systemctl show mango.service -p TimeoutStopUSec which shows TimeoutStopUSec=1min 30s it appears the service file is correctly configured; however, my experience suggests there is a failure somewhere in there. Additionally, a reboot command seems to execute immediately, too soon to properly shut down. What do you think?

Thanks for your reply I configure the URL with login time Out and now it work correctly.

Thanks, Craig, for the info. I've removed the Font Awesome JS reference and can still see the icons, so that's good. The bad news is that I still get the error posted in my initial post. Not sure what's causing it now. The only thing I thought each page with the error had in common was using Font Awesome, but it must be something else. I even removed all references to Font Awesome and still got an error. I have a work-around, so it's not the end of the world, just a little annoying. Thanks, Chad

OK, I generate an easy generic topic for the problem....

@jcaballeroa Mango 4.0.0 is a paid upgrade.

Happened again today. Had a customer call to say they couldn't see their live data or control information. Need this fixed guys. Fox

3.7.7 defaults to 0 seconds if no duration is entered, v4 enforces a user-defined duration. I think v4 is a better strategy.