• 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

    UpgradeCheck Invalid response code 302 causing Mango to die at startup

    Scheduled Pinned Locked Moved User help
    2 Posts 1 Posters 940 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.
    • AldoRamosA Offline
      AldoRamos
      last edited by

      Mango is suddenly crashing at startup, with the following log message:

      ERROR 2020-09-30T14:06:03,185 (com.serotonin.m2m2.rt.maint.UpgradeCheck.run:65) - Invalid response code 302, reason=Found:
org.apache.http.HttpException: Invalid response code 302, reason=Found:
        at com.serotonin.web.http.HttpUtils4.getTextContent(HttpUtils4.java:136) ~[mango-3.6.6.jar:?]
        at com.serotonin.m2m2.web.dwr.ModulesDwr.getAvailableUpgrades(ModulesDwr.java:420) ~[mango-3.6.6.jar:?]
        at com.serotonin.m2m2.web.dwr.ModulesDwr.upgradesAvailable(ModulesDwr.java:298) ~[mango-3.6.6.jar:?]
        at com.serotonin.m2m2.rt.maint.UpgradeCheck.run(UpgradeCheck.java:53) ~[mango-3.6.6.jar:?]
        at com.serotonin.timer.Task.runTask(Task.java:179) ~[mango-3.6.6.jar:?]
        at com.serotonin.timer.TaskWrapper.run(TaskWrapper.java:23) ~[mango-3.6.6.jar:?]
        at com.serotonin.timer.OrderedThreadPoolExecutor$OrderedTaskCollection.run(OrderedThreadPoolExecutor.java:336) ~[mango-3.6.6.jar:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[?:1.8.0_131]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[?:1.8.0_131]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]

      This is running version 3.6.6 and was running fine on Monday. Is it that unhappy about a 302?

      Thanks in advance,

      Aldo

      AldoRamosA 1 Reply Last reply Reply Quote 0
      • AldoRamosA Offline
        AldoRamos @AldoRamos
        last edited by

        I purged the work directory, and the 302 error went away. Turns out the fact that it was the last message didn't connect it to the cause of the crash.

        I have sent the database and log files separately. Hopefully we can learn what's going on.

        Aldo

        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