• 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

    MangoESV3 refused to connect after upgrade 3.34

    Mango Automation Installation
    2
    10
    3.1k
    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.
    • D
      Desmond
      last edited by

      Hi Support,

      After upgrade to 3.3.4, the mangoES refused to connect. This error page "This site cant be reached" after restart. This is the first attempt to do upgrade as it is a new purchased unit.

      I have tried the IP address in the URL and do a restart again but no success. What could be wrong during the upgrade process?

      Any suggestion or help is appreciated.
      Thank you in advanced

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

        Might you have manually upgraded it and done some step as the root user, while ls -l /opt/mango reveals files owned by 'mango'? Fix by chown -R mango:mango /opt/mango

        Have you tried to see what happens if you attempt to launch Mango at the command line with

        cd /opt/mango/bin; ./ma.sh start

        ?

        1 Reply Last reply Reply Quote 0
        • D
          Desmond
          last edited by

          @phildunlap
          I have managed to see the directory of mango now. For your information running the command cd /opt/mango/bin; ./ma.sh start give the result as per photo.
          0_1524467011328_error1.jpg

          I tried to login locally via the url give the result as per photo.
          0_1524467450565_error2.jpg.
          The IP address 192.168.1.12 response with the ping command and I can login the wed server.

          This is the new purchased unit on feb2018 and I have not done nothing else other than upgrading the web admin and mangoES. It used to be login without issue before upgrade.

          Pls help as I am not familiar with administering the web server. I cant figure out what need to be done.

          Thank you in advance.

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

            Hi Desmond,

            It looks like something is wrong in the advanced components module that you have installed. Consider removing it,

            rm -r /opt/mango/web/modules/advancedComponents

            And trying to start again. You can reinstall it on the module page.

            1 Reply Last reply Reply Quote 0
            • D
              Desmond
              last edited by

              @phildunlap

              I have removed the advancedComponents module as per your comment. Then I run ma-start command or url://IP address, it does not launch the login page in chrome as per expected.

              Below i have attached the ma and ma-script file for your action.

              [shareable link](https://drive.google.com/file/d/12T4HlRaWmeiX5cFB7JBxGrYm47GODaiu/view?usp=sharing
              https://drive.google.com/file/d/166ladCzcLizSWdM57FTOBXjA37mF2dhF/view?usp=sharing)

              Hope you can look into it and give me guidance to resolve it.

              Thank you in advance.

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

                Something is amiss. Did you update / install Java?

                I would try downloading the enterprise bundle of 3.3.4 from https://store.infiniteautomation.com/core, renaming it to m2m2-core-3.3.4.zip, place it in /opt/mango/ and attempt to start it again. This will let the scripts perform the upgrade and ensure there are no duplicate jars.

                1 Reply Last reply Reply Quote 0
                • D
                  Desmond
                  last edited by

                  @phildunlap
                  I have followed your instruction steps to perform the upload enterprise bundle and restart but it does not resolve the startup issue.

                  part of console screen terminal:
                  [mango@mangoES3508 ~]# cd /opt/mango/bin; ./ma.sh start
                  MA_HOME is /opt/mango
                  Archive: /opt/mango/m2m2-core-3.4.4.zip
                  ........
                  Total output of 1.03 MB was truncated at 97.66 kB.
                  [mango@mangoES3508 bin]# cd /opt/mango/bin; ./ma.sh start
                  MA_HOME is /opt/mango
                  MA already running with Process ID: 1015
                  ma-start: MA done

                  Below is the console screen terminal for the java version :

                  [mango@mangoES3508 bin]# cd /opt/mango/bin; ./ma.sh start
                  MA_HOME is /opt/mango
                  MA already running with Process ID: 1015
                  ma-start: MA done
                  [mango@mangoES3508 bin]# java -version
                  java version "1.8.0_131"
                  Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
                  Java HotSpot(TM) Client VM (build 25.131-b11, mixed mode)
                  [mango@mangoES3508 bin]#

                  Pls note that I have been troubled with this issue since the purchased on the feb2018. Currently I am using trial version to do the application development.
                  I need your support to look into it as I am about to due for a presentation with the new MangoES.

                  Thank you in advance.

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

                    Hmm. It sounds like one or more modules has a module.properties file that is most likely 0 bytes long. I saw this on someone's system after an update. Perhaps try removing all your modules, and then using the /modules.shtm page to install the modules you need.

                    1 Reply Last reply Reply Quote 0
                    • D
                      Desmond
                      last edited by

                      @phildunlap
                      After several unsuccessful attempts, may I request that Mango to investigate into the root cause? I am willing to send you the details to access into the web server remotely.

                      My main concern is that I do not wish to make it worse by doing something wrongly to the system or if other errors occurred, it is difficult to isolate the problem. Besides, I am under pressure to start setting up of this MangoES unit for a demo presentation.

                      Let me know your comments.

                      Thanks

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

                        Upon investigation, I found Mango online and accessible. I updated it from 3.4.1 to 3.4.3

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