• 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 4 Documentation Website Mango 5 Documentation Website Radix IoT LinkedIn

    Auto Start Mango under Linux

    Scheduled Pinned Locked Moved Mango Automation Installation
    3 Posts 2 Posters 3.5k Views 1 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.
    • V Offline
      v8dave
      last edited by

      I have deployed Mango onto a GoDaddy virtual server running CentOS 6 and I can log into the server via Putty and start mango.

      If I then disconnect Putty, Mango continues to run but after a few days it stops.

      How can I configure the system to auto run Mango on boot up?

      There is no desktop on this system, only a command line interface and cpanel.

      1 Reply Last reply Reply Quote 0
      • Woody BeverleyW Offline
        Woody Beverley
        last edited by

        1. The usual way to have Mango automatically run when the server boots is to install a service. Probably your best bet is to contact GoDaddy tech support and have them assist you. Depending on your hosting GoDaddy may not allow you to install services. If allowed, the process will be similar to the one we describe in our wiki for installing services in Debian Linux. See Installation Services in our wiki.

        2. You need to find out why Mango is terminating. Check the Mango in <mango_root_dir>/logs/ma.log. Most common cause is running a premium module in unlicensed mode. For example: NoSQL. If this is the case it will be noted in your logfile.

        -WoodyB

        1 Reply Last reply Reply Quote 0
        • V Offline
          v8dave
          last edited by

          Thanks. That worked just fine.

          The service is now running.

          I'll now sort out the service starting on any reboot of the server and I will check the log if the system stops working.

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • First post
            Last post