• 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

    Mango Won't Start Stuck at Watchslists Loading

    User help
    4
    20
    5.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.
    • V
      vanguard
      last edited by

      Hello
      I have a problem. The software doesn't go further in the watchlists loading page after running ma.start.bat. I am using win10. No more errors given.

      INFO 2016-02-24 14:22:41,462 (com.serotonin.m2m2.Main.loadModules:417) - Loading module 'watchlists', v1.7.3 by Infinite Automation Software

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

        Did you see this video: http://infiniteautomation.com/wiki/doku.php?id=installation:windows It has some troubleshooting tips.

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

          I have the same problem under Linux: "Initializing Data Sources" is shown with the progress bar stuck at 75%. I was tailing ma.log during the upgrade and saw nothing unusual.

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

            I see this in my ma.log. has the "rejected" error in 2.7.4 essentially replaced the Timeout error from 2.7.2, or is this a symptom of Mango not starting?

            Core 2.7.2-2.7.3:

            2016-02-24 09:46:13,065 WARN  (com.serotonin.m2m2.rt.dataSource.PollingDataSource.scheduleTimeout:106) - Pavillion: poll at 2016/02/24 09:46:13 aborted because a previous poll started at 2016/02/24 09:46:11 is still running

            Core 2.7.4:

            2016-02-24 10:21:09,314 WARN  (com.serotonin.m2m2.rt.dataSource.PollingDataSource.rejected:233) - AcuDC: poll scheduled at 2016/02/24 10:21:09.314 aborted because Task Currently Running
            1 Reply Last reply Reply Quote 0
            • phildunlapP
              phildunlap
              last edited by

              Pedro, we reworked some aspects of the polling system, and you are correct that message replaced the old poll aborted.

              Does your instance start in SAFE mode?

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

                @vanguard

                Is this a new installation or recent upgrade? It sounds like something may have gone awry in the download of the module or some such, if you cannot get past loading that module. I would try removing watchlist from your module folder, or downloading a new copy of it.

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

                  The system started in SAFE mode, but I had to start a lot of datasources. I don't know what will happen when I restart with the datasources enabled. I increased "High priority maximum pool size" from 1000 to 5000, but am still unable to increase "Medium priority core pool size."

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

                    Hmm. Definitely worth an experiment. Can you check that "runtime.datasource.logStartupMetrics=true" in your env.properties? This will hopefully get more information during the startup of the data sources, provided com.serotonin.m2m2.rt or a parent (such as com.serotonin.m2m2) has logging enabled in your log4j configuration at either debug or info levels. It is at info level, by default.

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

                      Also, very troubling you cannot increase your medium priority pool. Do you have overridden jars or classes? Do you get a stack trace when it fails? Did you attempt to change that value before or after enabling your data sources? I am certainly able to edit that.

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

                        I just added

                        runtime.datasource.logStartupMetrics=true

                        To env.properties. However, I avoid startups because if they don't work then I'll be offline. Also, since restarts often don't work because they get stuck during a shutdown, I usually have to kill mango, which leaves tsdb dirty and adds at least another 10 minutes to the startup process, which further increases the downtime.

                        I will start a new thread to address the thread pool issue. I have no override jar or class files.

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

                          Hi Pedro,

                          It is fairly likely your shutdown will be much faster than it was on 2.7.2. We reworked the polling in part because this was related to some situations causing very long shutdowns and frequent aborted poll behavior.

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

                            That change was made only to the modbus module, correct?

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

                              No, it would affect everything. I believe the long shutdown was only in systems using the NoSQL database.

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

                                Pedro, what are you NoSQL batch write behind settings on your system settings page?

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

                                  The current settings below should be the same as the defaults, since I've never changed them:

                                  Batch write behind spawn threshold 	100000
Max batch write behind tasks 	10
Batch write behind inserts per task     100000

                                  For what it's worth, there are a number of points (perhaps more than a dozen) that are configured to log every second, with no cache. Is that an issue?

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

                                    It shouldn't be. Those are the defaults, so they're probably fine.

                                    The only way I've been able to replicate your situation (stalled at 75%) involved having far too many write behind threads and far too little data per thread (inverting those numbers, for instance). Still looking.

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

                                      Does the medium priority pool size affect this? Recall that in SAFE mode, my metadata sources were also disabled. I have a substantial number of metadata points, and for years I have frequently have problems where they stop updating for no known reason. My medium priority pool is set to the default of "3," and I get a DWR error whenever I try to save a larger number.

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

                                        I wouldn't think so, since by definition high priority tasks (like starting) would supersede other tasks. It's possible priority is inverting somewhere, but that's not an immediately fruitful line of inquiry.

                                        I don't know why your medium pool doesn't save. That's why I keep saying check overrides classes (I just discovered overrides/properties is also on the classpath and shouldn't have any extra .jar or .class files hanging around. Perhaps it's your browser cache? Perhaps you could export your system settings and see if something bizarre is in there...

                                        If you start a fresh Mango in a new folder, I sincerely doubt you will have that issue, which leads me to believe there is an override in overrides/classes (or properties or lib), duplicate jars in Mango/lib/ or your browser has cached the client side of the DWR code.

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

                                          I just emailed you my system settings. I deleted the work directory:
                                          $ sudo rm -r work/jsp
                                          I used Chromium in case the Firefox cache is an issue, and there are no jar or class files in overrides:
                                          $ find /opt/mango/overrides -type f
                                          /opt/mango/overrides/web/favicon.ico
                                          /opt/mango/overrides/web/MangoDailyScheduled.sh
                                          /opt/mango/overrides/web/images/favicon.ico
                                          /opt/mango/overrides/web/images/logo.png
                                          /opt/mango/overrides/web/images/Tides_icon.png
                                          /opt/mango/overrides/web/WEB-INF/tags/page.tag
                                          /opt/mango/overrides/web/WEB-INF/tags/html5/footer.tag
                                          /opt/mango/overrides/web/WEB-INF/tags/html5/footer.tag-orig
                                          /opt/mango/overrides/web/WEB-INF/tags/mobile-page.tag
                                          /opt/mango/overrides/properties/keystore.jks
                                          /opt/mango/overrides/properties/i18n.properties
                                          /opt/mango/overrides/properties/env.properties-derby~
                                          /opt/mango/overrides/properties/env.properties-mysql~
                                          /opt/mango/overrides/properties/env.properties
                                          /opt/mango/overrides/properties/env.properties.13Jan2015
                                          /opt/mango/overrides/__MACOSX/classes/..DS_Store
                                          /opt/mango/overrides/__MACOSX/classes/com/.                                          .DS_Store
                                          /opt/mango/overrides/__MACOSX/classes/com/serotonin/m2m2/..DS_Store
                                          /opt/mango/overrides/__MACOSX/classes/com/serotonin/m2m2/rt/.                                          .DS_Store
                                          /opt/mango/overrides/__MACOSX/classes/com/serotonin/._.DS_Store
                                          /opt/mango/overrides/classes/log4j.xml

                                          1 Reply Last reply Reply Quote 0
                                          • V
                                            vanguard
                                            last edited by

                                            Thanks for the replys.
                                            I had to reinstall everthing, clear browser cache and run in admin mode. Now it works, i will let anyone know if the problem exists after creating some watchlists and graphics.

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