• Recent
    • Tags
    • Popular
    • Register
    • Login

    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.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    Failure to start/restart Mango - thread exception

    User help
    3
    4
    2.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mlavelle42
      last edited by

      I'm running Mango 2.7.10 on the Raspberry Pi version 4.1.18-v7+. I originally had a startup problem about a month ago but after that the system ran OK - until yesterday.

      Yesterday it became non-responsive. Restarting Mango was not successful. I also restarted Linux several times - to no avail. Mango is set to auto-start on bootup too - and, of course, it didn't.

      I see the following in my command window after startup.

      INFO 2016-04-20 13:33:59,593 (com.serotonin.m2m2.Lifecycle.terminate:344) - Mango Lifecycle terminating...
      Exception in thread "high-pool-1-thread-2" java.lang.NullPointerException
      at com.serotonin.m2m2.CoreLicenseDefinition$2.run(CoreLicenseDefinition.java:149)
      at com.serotonin.timer.sync.Synchronizer$TaskWrapper.run(Synchronizer.java:155)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      at java.lang.Thread.run(Thread.java:745)
      INFO 2016-04-20 13:33:59,726 (com.serotonin.m2m2.Lifecycle.terminate:446) - Mango Lifecycle terminated.
      INFO 2016-04-20 13:33:59,731 (com.serotonin.m2m2.Lifecycle.terminate:344) - Mango Lifecycle terminating...
      ma-start: no restart flag found, not restarting MA
      ma-start: MA done

      The ma.log file now shows this...

      at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:199)
      at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:111)
      at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:77)
      ... 12 more
      

      INFO 2016-04-20 13:33:59,593 (com.serotonin.m2m2.Lifecycle.terminate:344) - Mango Lifecycle terminating...
      INFO 2016-04-20 13:33:59,726 (com.serotonin.m2m2.Lifecycle.terminate:446) - Mango Lifecycle terminated.
      INFO 2016-04-20 13:33:59,731 (com.serotonin.m2m2.Lifecycle.terminate:344) - Mango Lifecycle terminating...

      Earlier the startup process showed this...

      INFO 2016-04-20 13:33:59,593 (com.serotonin.m2m2.Lifecycle.terminate:344) - Mango Lifecycle terminating...
      Exception in thread "high-pool-1-thread-2" java.lang.NullPointerException
      at com.serotonin.m2m2.CoreLicenseDefinition$2.run(CoreLicenseDefinition.java:149)
      at com.serotonin.timer.sync.Synchronizer$TaskWrapper.run(Synchronizer.java:155)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      at java.lang.Thread.run(Thread.java:745)
      INFO 2016-04-20 13:33:59,726 (com.serotonin.m2m2.Lifecycle.terminate:446) - Mango Lifecycle terminated.
      INFO 2016-04-20 13:33:59,731 (com.serotonin.m2m2.Lifecycle.terminate:344) - Mango Lifecycle terminating...
      ma-start: no restart flag found, not restarting MA
      ma-start: MA done

      I was suspicious of the "high-pool-1-thread-2" exception. Just before it would not run properly I noticed a total Exceptions of about 27,000 - which seemed like a huge number.

      Meanwhile the H2 database is up to 593 MB, which I assume is partly because of the alerts (alerts may be the wrong word - maybe "exceptions") logged within.

      Questions:

      • Any comment on the "high-pool..." exception? Could it be caused by the large number of alerts?

      • Is there any way to clean out the alerts manually?

      Any suggestions to fix this problem?

      1 Reply Last reply Reply Quote 0
      • terrypackerT
        terrypacker
        last edited by

        @mlavelle42 said in Failure to start/restart Mango - thread exception:

        • Any comment on the "high-pool..." exception? Could it be caused by the large number of alerts?

        This is probably some sympathetic exception message the real problem must be earlier in the log file. Mango has chosen to shut down and is having issues because it was not fully initialized.

        • Is there any way to clean out the alerts manually?

        Yes there is a shell script at bin/h2-web-console.sh that will open up a port that you can connect to via a web browser. Read the script first before executing it. This will provide you with an SQL console that you can explore and modify the database. Use at your own risk.

        1 Reply Last reply Reply Quote 0
        • M
          mlavelle42
          last edited by

          I was able to access the database using H2 db tools. However I'm unable to see the data tables. Below is a snapshot of my connection.
          ![alt text](0_1461269857704_Screen Shot 2016-04-21 at 4.10.26 PM.png image url)

          Here's what I see after connecting:
          0_1461270014566_Screen Shot 2016-04-21 at 4.03.50 PM.png

          What am I missing? Why don't the data tables show up as in your example?

          1 Reply Last reply Reply Quote 0
          • JoelHaggarJ
            JoelHaggar
            last edited by

            This should help: http://help.infiniteautomation.com/m/55730/l/519384-about-the-h2-database

            1 Reply Last reply Reply Quote 0
            • First post
              Last post