• 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

    Update core 5.4.1 core 5.5.2 failed

    Scheduled Pinned Locked Moved User help
    3 Posts 2 Posters 8 Views 2 Watching
    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 Offline
      mihairosu
      last edited by

      I tried to update Core and all modules from 5.4.1 to 5.5.2 and now Mango won't start up. I don't have permissions

      See link to ma.log file.

      1 Reply Last reply Reply Quote 0
      • M Offline
        mihairosu
        last edited by

        I'm going to revert to a backup until there's a resolution.

        1 Reply Last reply Reply Quote 0
        • joeamiragliaJ Offline
          joeamiraglia
          last edited by joeamiraglia

          @mihairosu said in Update core 5.4.1 core 5.5.2 failed:

          mihairosu
          2 days ago

          I tried to update Core and all modules from 5.4.1 to 5.5.2 and now Mango won't start up. I don't have permissions

          See link to ma.log file.

          Hi @mihairosu,

          Thanks for sharing the details and sorry to hear about the trouble after upgrading to 5.5.2.

          This issue is related to a known bug that was introduced in Mango version 5.5.0 and will be resolved in the upcoming 5.5.3 release.

          In the meantime, a workaround is available:

          You can manually change the system setting for the alarm level of the system event MAX_ALARM_LEVEL_CHANGED directly in the database while Mango is offline. Here's the SQL command:

          UPDATE PUBLIC.SYSTEMSETTINGS t
          SET t.SETTINGVALUE = '0'
          WHERE t.SETTINGNAME = 'systemEventAlarmLevel.MAX_ALARM_LEVEL_CHANGED';
          

          This should help bypass the startup issue you're encountering. Once Mango is back online, you can verify the change and proceed with your upgrade path or if your not comfortable making this change wait for the Mango v5.5.3 release.

          Let us know if you any further questions or if anything else comes up!

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