• 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

    MangoES Logs Took up entire Drive space

    User help
    2
    3
    1.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.
    • M
      mihairosu
      last edited by

      There is a file /opt/mango/logs/processLog.PersistentPublisher-1.log which is 4.8 GB in size.

      We lost some data again due to full disk space. I used to think it was just because we kept data for too long, but the culprit are Mango's logs not automatically being purged properly.

      How can I fix this so it does not happen again?

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

        The vast majority of the logs in Mango have fixed maximum sizes and rotate files when they reach that size. It does appear this hasn't been done for the persistent publisher, yet. The easiest fix that occurs to me is turning the logging on your persistent TCP publishers off (log level: none) or to the WARN/ERROR level (each persistent publisher has a select box for log level), but I'll raise the concern of limiting this file.

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

          That's good to hear! I don't want to have to worry about this, or eventually forget and get caught off guard.

          In the meantime I changed Log level from debug to Error in the persistent publisher for now.

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