I started the scan for my movie collection (roughly 140 movies) on my Raspberry Pi 3B. It has become unresponsive and I can’t ssh in now. It seems to be due to all the ffmpeg instances. I have two questions:

Should I wait for an hour or should I just reboot the server? Also, is there a way to disable the setting for chapter images from the web UI? I can’t find it in the setting.

    • emiellr
      link
      fedilink
      English
      arrow-up
      7
      ·
      edit-2
      2 months ago

      In case you ran it using a docker run command, read this. Otherwise if you use compose, try something similar to the following:

      services:
        service:
          image: nginx
          deploy:
            resources:
              limits:
                cpus: '3'
                memory: 512M
              reservations:
                cpus: '0.25'
                memory: 128M
          cpuset: "1"
          ports:
            - "80:80"
      

      source

        • emiellr
          link
          fedilink
          English
          arrow-up
          5
          ·
          2 months ago

          I have no idea what your experience level is, so I’m saying this just to make sure: DON’T copy this verbatim. The resources bit is what you’d need to adapt into your own compose file. If you have questions, feel free to ask 👍

      • FarraigePlaisteach@lemmy.worldOP
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        2 months ago

        It seems I’m out of luck on this kernel / hardware. After applying some limitations I get the following when I run the container:

        Your kernel does not support memory soft limit capabilities or the cgroup is not mounted. Limitation discarded.

        • emiellr
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          2 months ago

          Oh strange, a quick Google search doesn’t bring up much of anything either. With loads of people having Pi’s and presumably also having tried to limit the capabilities, you’d think someone else would’ve posted something about it. If it really bugs you, maybe try a fresh install of Raspbian Lite 64bit and see if things work? Otherwise I think it might just be a limitation of the Pi.

          • FarraigePlaisteach@lemmy.worldOP
            link
            fedilink
            arrow-up
            1
            ·
            2 months ago

            Someone suggested renicing the processes. Not sure how practical it would be but I’ll look into it. Besides that I think I’ll just return to using an SMB server. It was ugly but it was easy :) The Pi4 isn’t expensive these days either. Thanks again, I appreciate it!