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.

Terry,

Updating the priority seemed to do the trick. The job ran on time this morning.

Another factor that I'm sure contributed is that we didn't realize our CPU was pegged for a couple days and had to restart Mango to clear that up. (Different post created for that issue...)

Thanks,
Chad

@cbyrne
I have solved the problem. I will post it tomorrow if you are interested.

Use a text editor to escape them with another backslash. Its likely trying to treat the * as a control character...

\\

Fox

Hi @cwangv there is a use cron checkbox at the top which brings out the corn pattern input.

@craigweb
I did not enable SSL. I have the same problem in Debian and Mac.
But why would beta 4.0.3 work but not 4.0.5 when installed in the same environment? I have tried fresh installed as well but no luck for both Debian and Mac.
It baffles me.

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?