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. Paperwork
  3. Can't export notes from Paperwork, memory issue

Can't export notes from Paperwork, memory issue

Scheduled Pinned Locked Moved Paperwork
paperwork
6 Posts 3 Posters 1.3k Views 3 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.
  • scookeS Offline
    scookeS Offline
    scooke
    wrote on last edited by girish
    #1

    Hi!
    When I try to export the notes from Paperwork I receive the following error below. I've increased the apps memory ALOT but even almost maxed out it fails. I figured out how to dump the db to try to rebuild it elsewhere, but if I could figure out why the proper in-app export notes process fails that would be ideal. Much thanks.

    Symfony \ Component \ Debug \ Exception \ FatalErrorException (E_UNKNOWN)
    HELP
    Allowed memory size of 67108864 bytes exhausted (tried to allocate 33305664 bytes)
    

    A life lived in fear is a life half-lived

    1 Reply Last reply
    0
    • nebulonN Away
      nebulonN Away
      nebulon
      Staff
      wrote on last edited by
      #2

      This appears to be the php memory limit, not the whole app container limit. Unfortunately that is fixed within the app image at the moment and since the upstream app development has stalled for that app, we don't really intend to update it further 😕

      scookeS 1 Reply Last reply
      0
      • nebulonN nebulon

        This appears to be the php memory limit, not the whole app container limit. Unfortunately that is fixed within the app image at the moment and since the upstream app development has stalled for that app, we don't really intend to update it further 😕

        scookeS Offline
        scookeS Offline
        scooke
        wrote on last edited by
        #3

        @nebulon No problem. When you say within the app image is this something I can edit myself?

        A life lived in fear is a life half-lived

        1 Reply Last reply
        0
        • nebulonN Away
          nebulonN Away
          nebulon
          Staff
          wrote on last edited by
          #4

          Unfortunately this is not possible easily currently, I will think about how this can be done.

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

            A workaround for now is to use the CLI tool:

            $ cloudron debug --app <paperwork.domain.com>
            $ cloudron exec
            # crudini --set /etc/php/7.0/apache2/php.ini PHP memory_limit 256M
            # /app/code/start.sh
            

            the last line start.sh will start the app. now you can hopefully export. After you are done, you can do cloudron debug --disable.

            scookeS 1 Reply Last reply
            1
            • girishG girish

              A workaround for now is to use the CLI tool:

              $ cloudron debug --app <paperwork.domain.com>
              $ cloudron exec
              # crudini --set /etc/php/7.0/apache2/php.ini PHP memory_limit 256M
              # /app/code/start.sh
              

              the last line start.sh will start the app. now you can hopefully export. After you are done, you can do cloudron debug --disable.

              scookeS Offline
              scookeS Offline
              scooke
              wrote on last edited by
              #6

              @girish Thank you for trying. It still was not working, similar message as before. i tried boosting the ram to 4096MB even but it still failed. Oh well.

              A life lived in fear is a life half-lived

              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