Chiming in as I am repeatedly having an out of memory issue as well. I have tried the sudo snap set nextcloud php.memory-limit=512M and the restart command repeatedly and the issue persists.
If I view the php.ini file, it is still showing the memory limit at 128MB, and the file says that it is read-only if I try to change it to 512MB and save.
Is there another configuration file that I can modify somewhere?
This definitely seems to be related to something with photos and thumbnails as my nextcloud runs fine until I open a folder full of photos. Then the out of memory error occurs and I have to reboot.
FYI I am using Digital Ocean Ubuntu 18 with 1GB RAM. Used the snap package to install Nextcloud.
I’m at my wit’s end here. I cannot make this thing work and I’m about give up on the entire thing. I am not proficient at all and therefore I cannot run this without using snap. I just don’t have the knowledge to configure and maintain everything without using a snap.
Really need some help to make this change from 128 to 512 and get it to actually save!
of course you should adapt the values to fit your need.
afterwards restart your php fpm service and your web server service:
e.g.: sudo service php7.2-fpm restart && sudo service ngxin restart
yesterday, I saw many LDAP related errors which vanished after raising the memory_limit in the CLI version of the PHP config. Obviously the cron job had issues.
Hello
I have php 7.3 and the command sudo -u www-data php7.3 -i | grep memory_limit
returns memory_limit => -1 => -1 NO LIMIT ! but I still have the message"The PHP memory…" BUG? or did I miss something?
Since one can set a priority, this as well assures that any other or future drop-in config cannot override this setting. php.ini settings are always overridden by any drop-in config or mod.
I do not want to increase PHP memory for all users.
Adding this line to user.ini worked fine in NC 15:
memory_limit = 512M
But now this file get’s an error while the checksum is incorrect.
And even worse, after each update this file is overwritten by the update.
So there should be an alternative way to set this option per NC installation, without loosing this setting each update and without getting a checksum failure notification.