• 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

    Upgrade Issue from 2.4.8 to 2.8.8 (again)

    User help
    2
    3
    1.2k
    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.
    • danD
      dan
      last edited by

      Hey Guys, I have a MangoES box here that I've been struggling to upgrade successfully to 2.8.8.
      It performed the upgrade after I followed the manual upgrade instructions. It upgraded the modules etc successfully, but when it went to start up I get the following error...

      INFO  2018-12-08 19:58:29,138 (com.serotonin.m2m2.db.upgrade.DBUpgrade.checkUpgrade:36) - Starting instance with core version 2.8.8, db 13
      
      
      INFO  2018-12-08 19:58:32,107 (com.serotonin.m2m2.rt.RuntimeManager.initialize:141) - Starting 1 Publishers...
      INFO  2018-12-08 19:58:32,108 (com.serotonin.m2m2.rt.RuntimeManager.initialize:143) - Starting publisher: Alerts
      INFO  2018-12-08 19:58:32,108 (com.serotonin.m2m2.rt.RuntimeManager.initialize:153) - 1 Publisher's started in 25ms
      ERROR 2018-12-08 19:58:33,397 (com.serotonin.m2m2.Lifecycle.fullyInitializeWebContext:971) -
      java.lang.NullPointerException
              at com.serotonin.m2m2.Lifecycle.fullyInitializeWebContext(Lifecycle.java:967)
              at com.serotonin.m2m2.Lifecycle.initialize(Lifecycle.java:324)
              at com.serotonin.m2m2.Main.main(Main.java:115)
      ERROR 2018-12-08 19:58:33,407 (com.serotonin.m2m2.Main.main:119) - Error during initialization
      java.lang.NullPointerException
              at com.serotonin.m2m2.Lifecycle.configureStartupDwr(Lifecycle.java:1023)
              at com.serotonin.m2m2.Lifecycle.fullyInitializeWebContext(Lifecycle.java:974)
              at com.serotonin.m2m2.Lifecycle.initialize(Lifecycle.java:324)
              at com.serotonin.m2m2.Main.main(Main.java:115)
      INFO  2018-12-08 19:58:33,408 (com.serotonin.m2m2.Lifecycle.terminate:353) - Mango Lifecycle terminating...
      INFO  2018-12-08 19:58:33,438 (com.serotonin.m2m2.rt.maint.BackgroundProcessing.joinTermination:373) - All medium priority tasks exited gracefully.
      INFO  2018-12-08 19:58:33,439 (com.serotonin.m2m2.rt.maint.BackgroundProcessing.joinTermination:378) - All low priority tasks exited gracefully.
      INFO  2018-12-08 19:58:33,890 (com.serotonin.m2m2.Lifecycle.terminate:453) - Mango Lifecycle terminated.
      
      

      Then the mango daemon just keeps restarting looping. I've had similar problems before and had to delete all the stuff in overrides/lib, I tried that in this instance and it still stops at starting publishers...

      Is there anything that jumps out at you in this log that I'm missing?

      Cheers
      Dan

      1 Reply Last reply Reply Quote 0
      • phildunlapP
        phildunlap
        last edited by phildunlap

        Hi Dan,

        The old threads were these, I believe, https://forum.infiniteautomation.com/topic/3749/mango-using-100-cpu and https://forum.infiniteautomation.com/topic/2308/upgrade-to-latest-version-wont-startup

        I've not tracked down exactly what causes that stack trace, if indeed it is only caused by one thing. It can usually be resolved by one of,

        1. Start on clean database and restore a backup
        2. Ensure there are no overrides in the classes or overrides folders
        3. Update Java
        4. Reinstall Mango

        There may be another stack trace making it to stderr, which you could try to launch Mango on the command like to see that output.

        1 Reply Last reply Reply Quote 0
        • danD
          dan
          last edited by

          Hey Phil, thanks for that.
          I'll give it a go on a clean installation.

          Cheers
          Dan

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