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. Paperless-ngx
  3. High cpu utilization since update 1.25.1

High cpu utilization since update 1.25.1

Scheduled Pinned Locked Moved Unsolved Paperless-ngx
42 Posts 14 Posters 3.6k Views 17 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.
  • W Offline
    W Offline
    wheez
    wrote on last edited by
    #29

    Do we know by now what is causing this problem? I have had it for the second time today. Last time about a Month ago. The fix worked in both cases but I guess it would still be interesting to know why this is happening.

    1 Reply Last reply
    2
    • humptydumptyH Offline
      humptydumptyH Offline
      humptydumpty
      wrote on last edited by humptydumpty
      #30

      It's going nuts again after it updated to 1.27 then 1.28 today.

      image.png

      edit: This time I had to delete the celery file and restart the app twice for the fix to work.

      1 Reply Last reply
      2
      • nebulonN nebulon referenced this topic on
      • humptydumptyH Offline
        humptydumptyH Offline
        humptydumpty
        wrote on last edited by
        #31

        Just an FYI, it's still recurring on v.1.3.2.

        1 Reply Last reply
        0
        • F Offline
          F Offline
          flwd
          wrote on last edited by
          #32

          Same issue for me. I ran cloudron as a VM on unraid and on proxmox, on 2 different hosts and with and without a CIFS mount as consume folder. The issue recurred in every constellation.

          J 1 Reply Last reply
          0
          • F flwd

            Same issue for me. I ran cloudron as a VM on unraid and on proxmox, on 2 different hosts and with and without a CIFS mount as consume folder. The issue recurred in every constellation.

            J Offline
            J Offline
            joseph
            Staff
            wrote on last edited by
            #33

            @flwd said in High cpu utilization since update 1.25.1:

            The issue recurred in every constellation

            What does this mean?

            jdaviescoatesJ F 2 Replies Last reply
            0
            • J joseph

              @flwd said in High cpu utilization since update 1.25.1:

              The issue recurred in every constellation

              What does this mean?

              jdaviescoatesJ Offline
              jdaviescoatesJ Offline
              jdaviescoates
              wrote on last edited by
              #34

              @joseph installation typo would be my guess 🙂

              I use Cloudron with Gandi & Hetzner

              1 Reply Last reply
              1
              • J joseph

                @flwd said in High cpu utilization since update 1.25.1:

                The issue recurred in every constellation

                What does this mean?

                F Offline
                F Offline
                flwd
                wrote on last edited by
                #35

                @joseph it occured in every installation variant i tried, independant of the CIFS mount and config.

                J 1 Reply Last reply
                1
                • F flwd

                  @joseph it occured in every installation variant i tried, independant of the CIFS mount and config.

                  J Offline
                  J Offline
                  joseph
                  Staff
                  wrote on last edited by
                  #36

                  @flwd thanks for the clarification. I think the original issue atleast was narrowed down to celery database going corrupt and it's not related to volume type. Have you tried deleting that database pointed out earlier in the thread?

                  F 1 Reply Last reply
                  0
                  • J joseph

                    @flwd thanks for the clarification. I think the original issue atleast was narrowed down to celery database going corrupt and it's not related to volume type. Have you tried deleting that database pointed out earlier in the thread?

                    F Offline
                    F Offline
                    flwd
                    wrote on last edited by
                    #37

                    @joseph yes, deleting the database fixes the problem temporarily.

                    1 Reply Last reply
                    0
                    • lukasgabrielL Offline
                      lukasgabrielL Offline
                      lukasgabriel
                      wrote on last edited by
                      #38

                      Same problem still happening...

                      humptydumptyH 1 Reply Last reply
                      0
                      • lukasgabrielL lukasgabriel

                        Same problem still happening...

                        humptydumptyH Offline
                        humptydumptyH Offline
                        humptydumpty
                        wrote on last edited by
                        #39

                        @lukasgabriel at this point consider it a feature rather than a bug

                        1 Reply Last reply
                        0
                        • perelinP Offline
                          perelinP Offline
                          perelin
                          wrote on last edited by
                          #40

                          Also just run into this issue. Deleted the .db.db file which fixed it (for now) com.paperlessng.cloudronapp@1.35.0

                          1 Reply Last reply
                          0
                          • humptydumptyH Offline
                            humptydumptyH Offline
                            humptydumpty
                            wrote on last edited by
                            #41

                            It was going crazy over the weekend for me too and of course, it happened the only time when I didn't check it (been monitoring it daily nowadays). I'll stick to using the Quickscan app on iOS which has OCR and will have it upload to my Nextcloud directly. Adios papersh*t.

                            1 Reply Last reply
                            0
                            • perelinP Offline
                              perelinP Offline
                              perelin
                              wrote on last edited by
                              #42

                              Yup, its up again. Took 1 day. Maybe cron/automating the deletion of the .db.db file is something that I will 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