Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Unexpected Large Log Files in /home/yellowtent/platformdata/logs/mongodb

Unexpected Large Log Files in /home/yellowtent/platformdata/logs/mongodb

Scheduled Pinned Locked Moved Unsolved Support
mongodbbloatdisk spacedisk usagedisk-usage
6 Posts 2 Posters 61 Views 2 Watching
  • 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.
  • alex-a-sotoA Offline
    alex-a-sotoA Offline
    alex-a-soto
    wrote last edited by alex-a-soto
    #1

    Hi Cloudron Team,

    I hope you're doing well. I noticed unusually large log files in the directory below:

    /home/yellowtent/platformdata/logs/mongodb
     
    app.log       → 24GB
    app.log.1     → 12GB
    
    1. Is there a known issue or misconfiguration that could cause these files to grow to this size?
    2. If these are app-specific logs, what controls their retention and rotation?

    Would appreciate guidance on how to clean these up and prevent future bloating safely.

    Thank you for your time and support.

    Best,
    Alex

    1 Reply Last reply
    1
    • jamesJ Offline
      jamesJ Offline
      james
      Staff
      wrote last edited by
      #2

      Hello @alex-a-soto

      @alex-a-soto said in Unexpected Large Log Files in /home/yellowtent/platformdata/logs/mongodb:

      Is there a known issue or misconfiguration that could cause these files to grow to this size?

      No.
      There is/was this issue https://forum.cloudron.io/topic/13361/after-ubuntu-22-24-upgrade-syslog-getting-spammed-and-grows-way-to-much-clogging-up-the-diskspace might be also the case here.
      Needs to be validated.

      @alex-a-soto said in Unexpected Large Log Files in /home/yellowtent/platformdata/logs/mongodb:

      If these are app-specific logs, what controls their retention and rotation?

      Since this is about the /home/yellowtent/platformdata/logs/mongodb log file, it could be that one of your apps that uses MongoDB is running an absurd amount of querys.
      What apps are you using?

      1 Reply Last reply
      1
      • alex-a-sotoA Offline
        alex-a-sotoA Offline
        alex-a-soto
        wrote last edited by alex-a-soto
        #3

        Hi @james, thank you for your support.

        There is/was this issue https://forum.cloudron.io/topic/13361/after-ubuntu-22-24-upgrade-syslog-getting-spammed-and-grows-way-to-much-clogging-up-the-diskspace might be also the case here.

        Needs to be validated.

        I'll check to see if it's related to the Ubuntu upgrade.

        I ran head -n 1 app.log and got a MongoDB log entry noting a find query by _id, labeled as a "slow query" even though it completed instantly (0ms).

        What apps are you using?

        n8n, Cal.com Nextcloud, Baserow, HedgeDoc, SOGo, Wekan

        I started noticing this after installing Wekan.

        1 Reply Last reply
        0
        • jamesJ Offline
          jamesJ Offline
          james
          Staff
          wrote last edited by
          #4

          Hello @alex-a-soto

          It might be a good idea to clear the MongoDB logs, disable wekan to confirm if this is the issue.

          alex-a-sotoA 1 Reply Last reply
          0
          • jamesJ james

            Hello @alex-a-soto

            It might be a good idea to clear the MongoDB logs, disable wekan to confirm if this is the issue.

            alex-a-sotoA Offline
            alex-a-sotoA Offline
            alex-a-soto
            wrote last edited by
            #5

            @james said in Unexpected Large Log Files in /home/yellowtent/platformdata/logs/mongodb:

            Hello @alex-a-soto

            It might be a good idea to clear the MongoDB logs, disable wekan to confirm if this is the issue.

            Hi @james, I cleared the MongoDB logs, disabled Wekan, waited for about 10 minutes, and checked app.log and app.log.1, the file size stayed the same during that time.

            I restarted Wekan and noticed that both log files began increasing in size again by about 1.0 MB in minutes.

            The logs show repeated hello commands from Wekan to MongoDB that time out or wait for responses.

            2025-06-10T19:04:51.245+00:00 - "Error while waiting for hello response"
            2025-06-10T19:04:51.245+00:00 - "Slow query"
            2025-06-10T19:04:51.245+00:00 - "Waiting for a hello response from a topology change or until deadline"
            
            jamesJ 1 Reply Last reply
            0
            • alex-a-sotoA alex-a-soto

              @james said in Unexpected Large Log Files in /home/yellowtent/platformdata/logs/mongodb:

              Hello @alex-a-soto

              It might be a good idea to clear the MongoDB logs, disable wekan to confirm if this is the issue.

              Hi @james, I cleared the MongoDB logs, disabled Wekan, waited for about 10 minutes, and checked app.log and app.log.1, the file size stayed the same during that time.

              I restarted Wekan and noticed that both log files began increasing in size again by about 1.0 MB in minutes.

              The logs show repeated hello commands from Wekan to MongoDB that time out or wait for responses.

              2025-06-10T19:04:51.245+00:00 - "Error while waiting for hello response"
              2025-06-10T19:04:51.245+00:00 - "Slow query"
              2025-06-10T19:04:51.245+00:00 - "Waiting for a hello response from a topology change or until deadline"
              
              jamesJ Offline
              jamesJ Offline
              james
              Staff
              wrote last edited by
              #6

              @alex-a-soto so maybe you need to also increase the RAM of wekan. Worth a try.

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Bookmarks
              • Search