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. "Platform data" and "Other" disk usage

"Platform data" and "Other" disk usage

Scheduled Pinned Locked Moved Solved Support
cloudrondisk usagelogs
26 Posts 10 Posters 4.2k Views 10 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.
  • girishG Offline
    girishG Offline
    girish
    Staff
    wrote on last edited by girish
    #21

    Found out why. If a log file is > 20M at rotation time, then it's never truncated. Looks like this is just how logrotate works.

    1 Reply Last reply
    0
    • necrevistonnezrN Offline
      necrevistonnezrN Offline
      necrevistonnezr
      wrote on last edited by
      #22

      https://paste.cloudron.io/upozogutut.sql
      For me it adds up to 699 MB

      Is there a way to clean up those logs in between?

      1 Reply Last reply
      0
      • girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #23

        @necrevistonnezr If you go into /home/yellowtent/platformdata/logrotate, do you see 07e4e251-ed90-42ca-9ba3-e015b108f1e6 and c5c137fa-0221-4d42-b418-10e544cebad1 there? If not, go those apps (you can figure this out either by looking at the logs a bit or in the dashboard's URL) and start recovery mode and end recovery mode. This will generate the logrotate configs for them.

        Once, the configs are in place, future logs will get rotated. But this does not help the current logs. You can just truncate them like:

        truncate -s0 /home/yellowtent/platformdata/logs/07e4e251-ed90-42ca-9ba3-e015b108f1e6/app.log
        
        necrevistonnezrN 1 Reply Last reply
        0
        • girishG girish

          @necrevistonnezr If you go into /home/yellowtent/platformdata/logrotate, do you see 07e4e251-ed90-42ca-9ba3-e015b108f1e6 and c5c137fa-0221-4d42-b418-10e544cebad1 there? If not, go those apps (you can figure this out either by looking at the logs a bit or in the dashboard's URL) and start recovery mode and end recovery mode. This will generate the logrotate configs for them.

          Once, the configs are in place, future logs will get rotated. But this does not help the current logs. You can just truncate them like:

          truncate -s0 /home/yellowtent/platformdata/logs/07e4e251-ed90-42ca-9ba3-e015b108f1e6/app.log
          
          necrevistonnezrN Offline
          necrevistonnezrN Offline
          necrevistonnezr
          wrote on last edited by
          #24

          @girish Thanks, worked!

          1 Reply Last reply
          0
          • foliovisionF Offline
            foliovisionF Offline
            foliovision
            wrote on last edited by
            #25

            Hi Girish,

            We've run into issues with reclaimable space as well. Here's where we stand now.

            # docker system df
            TYPE            TOTAL     ACTIVE    SIZE      RECLAIMABLE
            Images          18        18        15.99GB   4.727GB (29%)
            Containers      19        19        95.79kB   0B (0%)
            Local Volumes   62        58        623.4MB   3.582kB (0%)
            Build Cache     0         0         0B        0B
            

            This is after running docker image prune -a which removed 19 Images (saved 4 GB), 3 Containers, 324 Local Volumes (saved 2.2 GB). We have also already ran We tried docker volume prune and docker system prune too. These only saved about 100 MB each.

            How do we reclaim the last 4.727GB of reclaimable space?

            Thanks in advance for your good advice, Alec

            PS. I've posted on this older thread as it's also about reclaimable space, to avoid too many duplicate threads on the forum.

            1 Reply Last reply
            1
            • girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #26

              @foliovision you can also try docker system prune -a --volumes but generally I have never succeeded in making that reclaimable space be less than 2GB in any server using docker (even without Cloudron).

              1 Reply Last reply
              2
              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