-
Notifications
You must be signed in to change notification settings - Fork 257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.3.0 Beta 3: cron.php: Allowed memory size of 134217728 bytes exhausted #2855
Comments
Is your Settings > Administration > System reporting the correct numbers under PHP? This may be useful if the numbers don't appear correct: https://docs.nextcloud.com/server/13.0.0/admin_manual/configuration_files/big_file_upload_configuration.html |
How do you invoke cron? Web? System cron? How large are your mailboxes in that account? |
Hi again... After manually upgrading to v1.3.0 Beta 3, I set up 128M in Plesk. This is stated as default value. But error is still alive. Mostly I get this error in this file / line:
@republicus : @ChristophWurst : Don't know how to determine IMAP mailbox size. Do you have a hint? |
Open the account with another client and check the number of messages in your inbox and any other mailbox/folder. |
Nextcloud Account 1: Nextcloud Account 2: |
That doesn't tell me anything.
|
Could you please take a look at #2873? I think I fixed these issues. You can download a patch from https://patch-diff.githubusercontent.com/raw/nextcloud/mail/pull/2873.patch. To reset your message cache (to trigger a full resync) you may use
As always, run your backup routine before patching the system or running the DB queries |
@ChristophWurst : Thanks for trying to fix the issue. If you want me to try this patch. I have to say sorry, but this beyond my knowledge. Don't know how to apply or test this patch. (I'm a Git newbie) |
You don't need git. Just a tool to apply a patch. Your basic linux distro tools should do that and there is tons of guides on this. You can also just replace the three changed files from my pull request by downloading them from https://github.com/nextcloud/mail/tree/enhancement/initial-sync-low-mem/lib. |
@ChristophWurst : I applied the patch with
I enabled logging level 1 Docs » Nextcloud configuration » Logging. Trying to catch more infos. |
Thanks. Let's hope this helps 🙏 I guess we should at least get a better hint of where it fails. |
Answering #2855 (comment) would still help a lot. And you may upgrade to the RC1 :) |
Expected behavior
I use NextCloud 18.0.3 on a hosted webspace (bitpalast.net) with cron support. (https://docs.nextcloud.com/server/18/admin_manual/configuration_server/background_jobs_configuration.html#cron). The month before testing Mail v1.3.0 Beta 2 there were no cron.php errors.
After testing Mail v1.3.0 Beta 2, I received random daily errors from executing cron.php. All errors referring to nextcloud/apps/mail/vendor/pear-pear.horde.org/Horde_Imap_Client/Horde/Imap/Client/.
Before testing 1.3.0 I've got no errors from executing cron.php.
After receiving the errors, I tried to play with folloging settings in Plesk:
Actual behavior
All erros till today:
Mail app
Mail app version: 1.3.0 (Beta 3)
Mailserver or service: IMAP from Googlemail and IMAP from hosted webserver on same machine.
Server configuration
Operating system: Linux lech 3.10.0-957.1.3.el7.x86_64/hosted with Plesk
Web server: Apache / nginx (tried Plesk config: 1) FPM by Apache 2) FPM by nginx https://docs.plesk.com/de-DE/onyx/customer-guide/websites-und-domains/hostingeinstellungen/einstellungen-f%C3%BCr-webskripting/phpeinstellungen.70742/) before was FPM by nginx
Database: MariaDB Version 10.3 (or newer)
PHP version: 7.3.16
Nextcloud Version: (see admin page, e.g. 13.0.2)
Client configuration
Browser: N/A
Operating system: N/A
The text was updated successfully, but these errors were encountered: