• Lorenzo Sintoni :fedora:@mastodon.uno
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    @beppi

    I had the same issue last week (was my first installation)

    I managed reinstalling it after a purge, and now it works good. The only difference is now i did not activate server side crypt module. I’m running NcAIO on Debian 11.

    @selfhosted

  • Krafting@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I’ve never heard of Nextclouf AIO, do you have links?

    For the RAM, the 200mb free and 7GB available, it’s because linux uses ram for caching things, but this ram used for cache can be freed right away when needed (this is the 7gb available)

    If i’m not mistaken docker will take all the ram it needs.

    In my personnal setup I use Portainer to manage things with a UI and Ive setup nextcloud with the Stacks functionnality of Portainer (it’s just multiple docker compose) and in the stack I have Nextcloud server and a Nextcloud mariadb database (and maybe something else ? I might be forgetting some things) have you tried setting up Newtcloud this way ? I suppose the AIO is bundled with the db and the server as one image?

  • nitrolife@rekabu.ru
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    Do I need to allow docker to use more than 6 GB?

    Check exactly how much RAM NextCloud daemons are used. How much CPU used?

    In general, it looks like an overload that occurs when NextCloud starts processing newly loaded files.

    • 🅱🅴🅿🅿🅸@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Whats the best way to check that?

      Running docker stats shows that when uploading around 500MB of vids, database spikes to 30%, nectcloud spikes to around 10%, and nginx proxy manager goes up and down a bit as i send through the files.

      RAM wise though nothing seems to be going above 5% of my 16GB RAM. Unless i upload larger files im sure

      • nitrolife@rekabu.ru
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Try running top and see the global cpu/mem statistics when loading images. Look at what a high-load process is. Check that docker is not installed via snap.

        • 🅱🅴🅿🅿🅸@sh.itjust.worksOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Will get back to you later on running top, but i installed it using apt so hopefully shouldnt be snap. Also, surely it shouldnt be using so much resources right? Its at the point now where i open Nextcloud Mobile, and a single image will never load. This cant be too much load on the server

  • Unquote0270@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I just upgraded to that version and it’s now seemingly borked.

    Docker compose down should stop them all as far as I know. Not sure about the timing out though, I think there may be some issues with this version of AIO.