• 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 on Ubuntu 14.04

    Mango Automation Installation
    4
    21
    13.9k
    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.
    • JoelHaggarJ
      JoelHaggar
      last edited by

      Can you check the /opt/mango/lib folder I wonder if it is empty? If so there could have been a upgrade issue in which case you would want to download the core zip file again and copy all the contents of the lib folder. This is just another guess. If that doesn't resolve it contact us at support and we'll hop on a screen share with you to poke around directly.

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

        Definitely not empty - 156 jar files in there.

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

          Well, more information could be gained by modifying the bin/ma-init.sh script to echo relevant stuff during the bin/ma.sh launch

          Perhaps...
          echo $EXECJAVA
          ls -l $(echo $EXECJAVA | sed -e 's/java$//') | grep java
          ... around line 27 of bin/ma-init.sh

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

            OK, that did the trick thanks Phil. Even though sudo echo $PATH didn't suggest that the path was being reset, adding those lines into the init script showed that it actually was being reset. Launching with sudo -E ./ma.sh start worked correctly! :)

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

              We've been having a similar problem (not auto starting at boot) for months now. However, I'm not so Linux savvy as smith. Could one of you poke around and try to resolve this issue?

              PS, We're Sheridan Point Condominiums.

              D 1 Reply Last reply Reply Quote 0
              • D
                dmsmith @mihairosu
                last edited by

                @mihairosu
                Hi. What happens when you try to manually start Mango after boot? What process do you use to do that?

                Cheers,

                David

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

                  Hi Mihairosu,

                  Can you email us the log from your Mango? You can find these on the computer at /opt/mango/logs/ma.log or more easily by logging in to Mango as the admin, navigating to the logging console page (tree log icon), and clicking the 'email logs to Infinite Automation' button (I believe this is Core 2.7+)

                  Icon:
                  logging.png

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

                    Hi Mihairosu, I may already be able to look into it. I will conduct the rest by email.

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

                      Thanks for fixing it for us Phil, this is much nicer!

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

                        No problem! I wasn't sure why JAVA_HOME wasn't in the environment, but I sourced the environment from the service and exported JAVA_HOME, problem solved.

                        Added the lines...
                        . /etc/environment
                        export JAVA_HOME

                        to your Mango service file

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