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

Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website

  • I have a mango es that I upgraded to from v2 to v3. It was originally stopping because it was in demo mode, but it now has a paid license on it. Every couple days since I put it into production the core just stops running. The ES is still on, I can access webmin and DGLux 5 server keeps running. The logs just stop running and don't show whats happening. I can start Mango again and its run fine until it stops again.

    Where should I start looking?

  • Hi solarnathan,

    1. Mango/logs/ma.log should be looked at for errors or related messages from why Mango may have stopped.
    2. But, more likely from your description there will be some hs_err_pid files in /opt/mango/ that describe the cause of the failure.

  • There is a hs_err_pid log from when it stopped working

    # A fatal error has been detected by the Java Runtime Environment:
    #  Internal Error (cfgnode.cpp:706), pid=2021, tid=1902113888
    #  Error: ShouldNotReachHere()
    # JRE version: Java(TM) SE Runtime Environment (8.0_33-b05) (build 1.8.0_33-b05)

  • Update Java, that looks like a Java bug.

    Normally we would have recommended the latest Oracle JDK 8, but you would have to read the license terms for that and see if you consent. Now we are likely to begin recommending OpenJDK 12, but we are still doing some evaluation.

    You could install OpenJDK 8 to be on the safe side. Here's a thread with instructions on doing the Java upgrade:

  • I installed openjdk 1.8.0 1069. Hopefully this will fix it. Thanks for the help.

  • Looks like the problem is back and worse. Three times this morning it crashed with this in the hs_err_pid log.

    # A fatal error has been detected by the Java Runtime Environment:
    #  SIGSEGV (0xb) at pc=0x00000000, pid=13432, tid=0x6e20f460
    # JRE version: OpenJDK Runtime Environment (8.0_171-b11) (build 1.8.0_171-8u171-b11-1~bpo8+1-b11)
    # Java VM: OpenJDK Client VM (25.171-b11 mixed mode linux-aarch32 )
    # Problematic frame:
    # C  0x00000000

  • Hmm. Is that the latest OpenJDK 8 version? Still looking like a JVM issue, most likely.

    If it crashes quickly and readily, you can try running Mango in safe mode by creating a file with touch /opt/mango/SAFE and see if there is more stability with the data sources disabled. Then maybe hunt down the cause of the failure. I've seen one instance where it kept crashing with a SIGBUS any time a particular unit attempted to poll a wireless mesh Modbus network (solved by using another unit the client had on hand, with same Java doing same thing), but I would think a SIGSEGV at 0x00000000 sounds like a null pointer in some C code, which would be a JVM bug.

  • I'm not positive if its the latest because version 8 of debian that is installed on the Mango Es doesn't have openjdk in the standard sources, only in the backports sources. Looks like maybe there is newer, but I can't see to locate a version for armv7l

  • I switched back to java se. I was able to get version 1.8.0 212-b10 installed. Hopefully this will be the fix.