• 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

    "Error checking for upgrades - Server Error"

    Scheduled Pinned Locked Moved User help
    8 Posts 3 Posters 1.8k Views 3 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.
    • TurboT Offline
      Turbo
      last edited by

      This is a new one for me.

      Fresh Mango install, and the Modules -> Check for Upgrades says this instantly when I click the "check for upgrades" button.

      ma.log doesn't record anything when this happens.

      Checked out my DNS settings, and I can ping/nslookup etc from my command line, but Mango seems to have trouble checking for updates.

      Not a big deal, since I can manually upgrade stuff, but I dunno why this is happening. First time I've seen this on a dozen Mango installs here now.

      1 Reply Last reply Reply Quote 0
      • MattFoxM Offline
        MattFox
        last edited by

        Out of curiosity, what upgrade channel are you using? Production? Dev?

        Do not follow where the path may lead; go instead where there is no path.
        And leave a trail - Muriel Strode

        1 Reply Last reply Reply Quote 0
        • TurboT Offline
          Turbo
          last edited by

          Upgrade Release Channel shows Production. I've never configured the release channel for Dev.

          1 Reply Last reply Reply Quote 0
          • MattFoxM Offline
            MattFox
            last edited by MattFox

            I think the logs you may also wish to look at should be along the lines of "com.serotonin.m2m2.db.upgrade.Upgrade" - basically anything with .upgrade in the name,

            If there's nothing in there, definitely flick infinite an email.

            Do not follow where the path may lead; go instead where there is no path.
            And leave a trail - Muriel Strode

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

              Hi Turbo,

              Can you check to ensure the store.url in your Mango/overrides/properties/env.properties file is set like,

              store.url=https://store.infiniteautomation.com
              

              You could try running on the command line and then triggering it, to see if something were somehow escaping to stderr, but I wouldn't expect that to be the case.

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

                Can you also ensure that "Enable checking for upgrades" is checked on the /ui/administration/system/information page?

                1 Reply Last reply Reply Quote 0
                • TurboT Offline
                  Turbo
                  last edited by

                  Yeah. I'm a clown.

                  I disabled "Enable checking for upgrades"-- I don't want these instances auto-upgrading (since most are on cell plans, and I need to keep my Cell data budget under control), so I'll just have to remember to re-enable that box before checking.

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

                    By no means! One would expect the check for upgrades button to still check for upgrades, or at least error with a message related to what's happened. That is why there is the git issue, https://github.com/infiniteautomation/ma-core-public/issues/1471

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