• 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

    Graphical views not rendering due to Error: xhrFailed /resources/dojo/dojo.js

    User help
    3
    10
    2.3k
    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.
    • P
      Pedro
      last edited by Pedro

      I downloaded the latest Mango 2.8.8 update as I was planning to initiate an upgrade to core 3.3. According to the module update page the only 2.x update was mangoNoSqlDatabase 1.3.12. After a restart and login, the graphical views do not render, and mango/logs/ma.log displays:

      WARN  (com.serotonin.m2m2.web.dwr.MiscDwr.jsError:178) - Javascript error
         Description: Error: xhrFailed
         Page: https://myservername/resources/dojo/dojo.js
         Line: 106
         Browser name: Firefox
         Browser version: 58
         osName: Linux
         location: https://myserver/views.shtm
      

      I inspected the file /opt/mango/web/resources/dojo/dojo.js and found that it looks like a "normal" js file. I'm running Ubuntu 16.04.

      1 Reply Last reply Reply Quote 0
      • Jared WiltshireJ
        Jared Wiltshire
        last edited by Jared Wiltshire

        @Pedro Can you check the browser console for messages when this occurs please -
        https://help.infiniteautomation.com/reporting-bugs/

        dojo.js is where the error is occurring, not the file the XHR is failing on. We need more information.

        Developer at Radix IoT

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

          Hi Pedro,

          Hmm. An update to the NoSQL module wouldn't affect that. Your ma.log would indicate if anything else were updated. if you open your browser tools before you load the page, do you get information about the status code returned for the request to load dojo?

          I presume you've tried cache clearing and Mango/work/ folder deleting?

          1 Reply Last reply Reply Quote 0
          • P
            Pedro
            last edited by

            I agree that an update to the NoSQL module should not affect that. I just remembered that I had also disabled DGLux. If I remember correctly, I had disabled the dashboard prior to the previous restart, and it had restarted then with no problems. I had not been using the dashboard, but I was using DGLux. None of these issues should have affected this. Yesterday I upgraded from Ubuntu 14.04 to 16.04. I did have to run fsck when booting 16.04, but Mango restarted fine after the OS upgrade. It was the subsequent mango restart that broke things. That was simply a Mango restart, not a reboot.

            rm -r /opt/mango/work/jsp did not make any difference. I cleared the browser cache with control-F5, and that also made no difference.

            I'll email a screenshot of the web console.

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

              From your last email, I judge this to be caused by removing the dashboards module while you were evaluating the 3.3 upgrade. If you reinstall that module, it'll probably work again, and you'll need to remove it again when you actually do decide to upgrade.

              P 1 Reply Last reply Reply Quote 0
              • P
                Pedro @phildunlap
                last edited by Pedro

                @phildunlap I have never evaluated the 3.3 upgrade on this server. Where does the option "Do backup before download" backup to? What does it back up? Will the previous backup be overwritten if I have it checked when reinstalling the Dashboard module? Why would the removal of the Dashboard module screw up the loading of point_details.shtm? If I reinstall the Dashboard module, then how will I upgrade to 3.3 if upgrading requires me to remove the Dashboard module?

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

                  1. Do backup before download - this will do your regularly configured backup actions, which may include a JSON backup, SQL backup and NoSQL backup, probably into your Mango/backup directory.
                  2. Will the previous backup be overwritten if I have it checked when reinstalling the Dashboard module? - The backups are the same as a normal nightly backup, so it will remove the backup that is X copies old, where X is a system setting.
                  3. Why would the removal of the Dashboard module screw up the loading of point_details.shtm? - Perhaps the dependencies in that version aren't cleanly separated.
                  4. If I reinstall the Dashboard module, then how will I upgrade to 3.3 if upgrading requires me to remove the Dashboard module? - Simply finish the process of upgrading and you wouldn't have to install the Dashboards module. So to upgrade, uninstall it, then actually upgrade Mango.
                  P 1 Reply Last reply Reply Quote 0
                  • P
                    Pedro @phildunlap
                    last edited by

                    @phildunlap I though I had to remove the Dashboard module, then restart Mango, and then upgrade. Are you saying I should remove the Dashboard module at the same time that I upgrade to 3.3, without a restart in between?

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

                      You must restart to remove the module in a running Mango. You must not have the module installed to do the upgrade to 3.3

                      In 3.3 flagging a module for deletion is the same as actually deleting it in terms of upgrades, but in 2.8 yes you have to restart to actually remove the module if you flagged it for deletion on the modules page.

                      P 1 Reply Last reply Reply Quote 0
                      • P
                        Pedro @phildunlap
                        last edited by

                        @phildunlap Phillip, Thanks for your help. I added the Dashboard module via the Module menu, with restart selected. After a restart, I logged in and the graphical view and the point detail pages rendered properly. The graphical view did not show the point values at first. Mango is usually slow to render values after a restart. The values rendered after I deleted /opt/mango/work/jsp, but that may have been coincidence.

                        Since I had not used Dashboard, I never expected its removal to break those two views.

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