Crossposted from : https://lemmy.ml/post/22319676

I just install a complete new Drupal install in a Debian VM inside proxmox, everything works as intended, but I cannot add content to it(it gives me a 500 error).

Apache logs show me that the memory is exhausted, search online, no real answer, tried a lot of thing in PHP.ini, .htaccess… At first the VM had 1 vcpu and 1GB of RAM, not working, I’ve put the PHP memory limit to 1GB, give 8GB to the vm, and 4vcpu. Not working, just “loading” the 500 longer.

Error got into /var/log/apache2/error.log : PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 262144 bytes)) in Unknown on line 0. This is why I give the vm 8GB and change php memory_limit to 1GB but it did nothing…

Have no solutions, as now. If you have one please let me know! thanks 🙂

EDIT: this is not the problem of drupal 11, tried to install it with drupal 10, same result, I think it has something to do with proxmox

  • krnl386@lemmy.ca
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    16 days ago

    Make a plain text file under Apache somewhere with .php extension and stick the following into it:

    
    <?php phpinfo(); ?>
    
    

    Ctrl+F the word “memory” and see if anything looks off.

  • undefined@lemmy.hogru.ch
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    16 days ago

    I’m a Ruby on Rails developer and it’s been a decade or two since I’ve used PHP, but why does it want so much memory? We host Drupal-based apps in Kubernetes at work and they need nowhere near that much memory.

    I would probably investigate what library or piece of code is requesting so much.

    • foremanguy@lemmy.mlOP
      link
      fedilink
      arrow-up
      2
      ·
      16 days ago

      I think that there is a memory leak somewhere, but don’t know really how to find it out

    • foremanguy@lemmy.mlOP
      link
      fedilink
      arrow-up
      1
      ·
      16 days ago

      Here you are (error got into /var/log/apache2/error.log) : PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 262144 bytes)

      This is why I give the vm 8GB and change php memory_limit to 1GB but it did nothing…

  • Rimu@piefed.social
    link
    fedilink
    English
    arrow-up
    3
    ·
    16 days ago

    I was a drupal dev for 10 years.

    There’s no way it should use that much ram. You probably have a contrib module installed that has a bug in it. Try a process of elimination till you find the module it is.

      • foremanguy@lemmy.mlOP
        link
        fedilink
        arrow-up
        1
        ·
        16 days ago

        Checked 90% of them, nothing changed. I only have the default modules, I think it is a proxmox-related issue do you have any idea?

        • Rimu@piefed.social
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          16 days ago

          So weird!

          Very unlikely to be a proxmox issue.

          134217728 bytes is only 138 MB so your php memory limit is set lower than you think. Your php config needs work. Restart Apache and php-fpm (if using) after changing php.ini and use phpinfo(); to check that your changes were applied successfully.

          A memory limit of 256 MB should be ok.

          • foremanguy@lemmy.mlOP
            link
            fedilink
            arrow-up
            1
            ·
            16 days ago

            Set the memory to 256MB, got this error : PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in Unknown on line 0

            • Rimu@piefed.social
              link
              fedilink
              English
              arrow-up
              2
              ·
              16 days ago

              Ok if trying a memory limit of 512MB doesn’t work then I’m out of ideas, sorry.

              • foremanguy@lemmy.mlOP
                link
                fedilink
                arrow-up
                1
                ·
                16 days ago

                Sorry but it doesn’t work, I’m going to try it on my localhost, not on my server, see if it’s the fault of proxmox

  • Rimu@piefed.social
    link
    fedilink
    English
    arrow-up
    2
    ·
    16 days ago

    Any interesting things in Reports -> Status? Sometimes there are warnings in there which point to config issues.