[NC 21] OCC Update error: allowed memory size exhausted #25742

onny · 2021-02-22T11:21:42Z

How to use GitHub

Please use the 👍 reaction to show that you are affected by the same issue.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.

Steps to reproduce

Upgrading to Nextcloud 21
Run php ./occ in Nextcloud root directory
./occ crashes

Expected behaviour

Occ should work normally, for example printing available commands

Actual behaviour

Occ crashes with the following error:

$ sudo -u http ./occ update
PHP Warning: Module “gd” is already loaded in Unknown on line 0
PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /usr/share/webapps/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php on line 133

To be more precise, this also happens running php cli against other files of Nextcloud, for example index.php or console.php.
Surprisingly Nextcloud is running fine through php-fpm and web server. It was even able to perform the upgrade to v21 just fine.

Another user commented on the ArchLinux bug tracker:

If it could help, I added a trace in /usr/share/webapps/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php on line 133, and I get in an infinite loop the following messages:

Could not resolve OC\User\Manager!
Could not resolve OC\Security\CSRF\CsrfTokenManager!

As if it was unable to locate its lib/private/ folder.
If I set memory_limit to -1, it fill completely memory and hit OOMkiller.
(tried with both php7 and php8, with nextcloud-21.0.0-7)

Possibly not only related to ArchLinux setups. An other user reported the exact issue here, which was triggered on a Ubuntu installation.

Server configuration

Operating system: Archlinux x64

Web server: Caddy 2

Database: Mysql

PHP version: 8.0.2

Nextcloud version: (see Nextcloud admin page) 21.0.0

Updated from an older Nextcloud/ownCloud or fresh install: Yes

Where did you install Nextcloud from: Package repository

Signing status:

Signing status

Unable to access for now

List of activated apps:

App list

accessibility/         drawio/                files_trashbin/           nextcloud_announcements/  settings/               twofactor_gateway/
activity/              encryption/            files_versions/           notes/                    sharebymail/            updatenotification/
admin_audit/           extract/               files_videoplayer/        notifications/            spreed/                 user_ldap/
apporder/              federatedfilesharing/  firstrunwizard/           oauth2/                   support/                user_status/
calendar/              federation/            integration_discourse/    password_policy/          survey_client/          viewer/
cloud_federation_api/  files/                 integration_github/       photos/                   suspicious_login/       weather_status/
comments/              files_ebookreader/     integration_reddit/       polls/                    systemtags/             workflowengine/
contacts/              files_external/        integration_twitter/      privacy/                  tasks/
contactsinteraction/   files_pdfviewer/       keeweb/                   provisioning_api/         text/
dashboard/             files_rightclick/      logreader/                recommendations/          theming/
dav/                   files_sharing/         lookup_server_connector/  serverinfo/               twofactor_backupcodes/

Nextcloud configuration:

Config report

<?php
$CONFIG = array (
  'instanceid' => '****',
  'datadirectory' => '/var/lib/nextcloud/data',
  'dbtype' => 'mysql',
  'version' => '21.0.0.18',
  'dbname' => 'nextcloud',
  'dbhost' => 'mysql.pi',
  'mysql.utf8mb4' => true,
  'dbuser' => 'nextcloud',
  'dbpassword' => '****',
  'installed' => true,
  'maintenance' => false,
  'loglevel' => 0,
  'cron_log' => true,
  'maxZipInputSize' => 5145728000,
  'allowZipDownload' => true,
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'allow_local_remote_servers' => true,
  'trusted_domains' => 
  array (
    0 => 'nextcloud.****.org',
  ),
  'passwordsalt' => '***',
  'secret' => '****',
  'mail_domain' => '******.org',
  'mail_smtpmode' => 'php',
  'mail_from_address' => 'nextcloud',
  'trashbin_retention_obligation' => 'auto',
  'updatechecker' => false,
  'app.mail.verify-tls-peer' => false,
  'overwrite.cli.url' => 'https://nextcloud.***.org',
  'default_phone_region' => 'DE',
);

Are you using external storage, if yes which one: None, had configured SFTP mount point

Are you using encryption: No

Are you using an external user-backend, if yes which one: No

Client configuration

Browser: Latest Firefox

Operating system: NixOS

Nextcloud log (data/nextcloud.log)

Nothing exceptional here, also no error logs

Nextcloud log

[...]
{"reqId":"pti6pSFymOb7PvbzzzmM","level":0,"time":"2021-02-21T18:08:04+00:00","remoteAddr":"2****","user":"--","app":"files_sharing","method":"GET","url":"/cron.php","message":"/appinfo/app.php is deprecated, use \\OCP\\AppFramework\\Bootstrap\\IBootstrap on the application class instead.","userAgent":"Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0","version":"21.0.0.18"}
{"reqId":"pti6pSFymOb7PvbzzzmM","level":0,"time":"2021-02-21T18:08:04+00:00","remoteAddr":"*****","user":"--","app":"keeweb","method":"GET","url":"/cron.php","message":"/appinfo/app.php is deprecated, use \\OCP\\AppFramework\\Bootstrap\\IBootstrap on the application class instead.","userAgent":"Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0","version":"21.0.0.18"}
{"reqId":"pti6pSFymOb7PvbzzzmM","level":0,"time":"2021-02-21T18:08:04+00:00","remoteAddr":"*****","user":"--","app":"onlyoffice","method":"GET","url":"/cron.php","message":"/appinfo/app.php is deprecated, use \\OCP\\AppFramework\\Bootstrap\\IBootstrap on the application class instead.","userAgent":"Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0","version":"21.0.0.18"}

The text was updated successfully, but these errors were encountered:

dschrempf · 2021-02-22T12:13:34Z

I am also affected by this. I run Arch Linux. I even tried a fresh install (but old data directory). The web interface works as expected.

kde35 · 2021-02-22T16:02:05Z

I also run Arch Linux, and in the web interface, of O go to the page admin/overview, it says, among other things
Last background job execution ran 9 days ago. Something seems wrong. Check the background job settings
And if go to settings/admin#backgroundjobs I see that the choice "cron" is checked, and if try to check webcron or ajax, and leave the page to come back, cron is still checked. So even the webinterface doesn't work correctly.

tbasilici · 2021-02-22T16:17:05Z

debian 10 here, same issue: tried with php 7.0 7.3 and 8.0 no joy, this is a nextcloud issue not an operative system one...

I upgraded from 21.0.0 RC2 to 21.0.0 and the issue presented itself on the upgrade at the end of the update process (that is the first time occ is run AFTER the files changed from rc2 to stable), this suggests me the problem might be somewhere in the changelog between the rc2 and the production ?

kde35 · 2021-02-22T16:23:35Z

As a matter of fact, there are whole bunch of things that don't work with web interface. I can't update, enable, disable, remove or download applications.

onny · 2021-02-22T17:29:39Z

As it might be relevant, here is some info about the php cli configuration:

php -i

st3iny · 2021-02-22T17:49:58Z

I can reproduce this bug with Nextcloud stable21 and php v7.4 on Arch Linux.

Another finding: The occ command works fine if the instance is not yet installed. After installing (e.g. using web installer or occ install command) it becomes unusable.

onny · 2021-02-22T20:14:55Z

Currently I suspect the upgrade process somehow corrupted the Mysql database?
I get following erros from the mysql/mariadb daemon:

InnoDB: Page [...] log sequence number [...] is in the future!

Feb 22 17:42:03 mysql mariadbd[327]: 2021-02-22 17:42:03 254850 [ERROR] InnoDB: Page [page id: space=2026, page number=45620] log sequence number 352586303314 is in the future! Current system log sequence number 320954826491.
Feb 22 17:42:03 mysql mariadbd[327]: 2021-02-22 17:42:03 254850 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.

If I stop the database, occ runs until connection timeout to Mysql server. So my guess is Occ crashes after connecting to the database ...

onny · 2021-02-22T20:37:39Z

Okay maybe it is something different. Nevertheless I put this at line 133 in lib/private/AppFramework/Utility/SimpleContainer.php:

echo "<pre>".print_r(debug_backtrace(),true)."</pre>";

Which is giving me this stack trace showing some kind of iteration with arrays including the PHP environment and configuration array?! https://onny.project-insanity.org/files/stacktrace_short.txt

Information which might be useful in this case:

Config file is located in /etc/webapps/nextcloud/config/config.php. /usr/share/webapps/nextcloud/config is a symlink to the config folder located in /etc/webapps-folder
After upgrading via web frontend I had to change the data directory according to the new packaging guidlines in Archlinux. It is now stored in /var/lib/nextcloud/data

onny · 2021-02-22T21:06:23Z

This is what I get from logging mysql queries:

210222 21:05:09      6 Connect  nextcloud@http.pi on nextcloud using TCP/IP
                     6 Query    SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED
                     6 Query    SET SESSION AUTOCOMMIT=1
                     6 Query    SELECT * FROM `oc_appconfig`

Nothing more ...

Edit: oc_appconfig has a lot of keys so I don't know where to look at. In case some value in there is causing the issue ...

Temtaime · 2021-02-22T21:08:09Z

I hit OOM when upgrading to latest nextcloud by running occ upgrade.
Is there any workaround or fix?

st3iny · 2021-02-22T21:57:03Z

I upgraded from 21.0.0 RC2 to 21.0.0 and the issue presented itself on the upgrade at the end of the update process (that is the first time occ is run AFTER the files changed from rc2 to stable), this suggests me the problem might be somewhere in the changelog between the rc2 and the production ?

I second this. I have been testing using the stable21 branch last week and it worked fine until a couple days ago. The regression was introduced recently.

Maybe bisecting from 21RC2 to the current version is a good starting point.

Xiretza · 2021-02-22T22:12:02Z

Same issue here. Arch Linux ARM, but with Postgres backend, so it might not be related to mysql at all.

occ attempts to allocate a lot more memory on startup than usual on 21.0.0, I tried increasing memory_limit in php.ini but that just causes it to get oomkilled at some point.

Disabling all extensions except for pgsql and pdo_pgsql (without these two occ just crashes) still results in the same behaviour.

php -i

yapbreak · 2021-02-22T22:22:06Z

Even with memory_limit set to -1 (so no limit at all), occ will fail and trigger OOMKiller on my server with 32GiB RAM and 32GiB Swap…

tflidd · 2021-02-22T22:35:05Z

Same problem on FreeBSD 12.2, php 7.3.

Upgrades to NC 21 RC 1 and NC 21 RC 2 went through without problems. Now it's just the main release NC 21.0.0:

PHP Fatal error:  Allowed memory size of 8489271296 bytes exhausted (tried to allocate 20480 bytes) in /usr/local/www/nextcloud-test/lib/private/AppFramework/Utility/SimpleContainer.php on line 133

Fatal error: Allowed memory size of 8489271296 bytes exhausted (tried to allocate 20480 bytes) in /usr/local/www/nextcloud-test/lib/private/AppFramework/Utility/SimpleContainer.php on line 133

and a few more reports on the forum:
https://help.nextcloud.com/t/occ-command-php-fatal-error-allowed-memory-size-of-xxx-bytes-exhausted/108521

madpilot78 · 2021-02-22T22:53:15Z

Also having this problem on FreeBSD 12.2, with php 7.4.

Downgrading (using FreeBSD binary packages built myself) restores functionality, the DB looks unmodified by the botched update.

RealSnoopyDog · 2021-02-22T23:40:31Z

I had exactly the same issue after I upgraded from NC 20.0.7 to 21.0.0 release. The cron.php also did not run.

CentOS 7 - postgreSQL 13 - php 7.4 or 8.0 (did not matter)

I "solved" the problem by downgrading to NC 21.0.0 RC2

andreaslutsch · 2021-02-23T00:10:41Z

@onny Try to enable apc.enable_cli=1 in /etc/php/8.0/cli/conf.d/20-apcu.ini. After I added that line to the file occ worked and the memory didn't get filled anymore.
Also see the warning here in the manual.

nextcloud486153 · 2021-02-23T00:20:08Z

@andreaslutsch your solution worked for me (21.0.0, ArchLinux). For reference for others, you can enable the option by adding the parameter --define apc.enable_cli=1 to your php cli call (e.g. php --define apc.enable_cli=1 occ [...]).

waja · 2021-02-23T07:11:18Z

@onny Do you think, this issue is fixed? For me it is a regression and thus a bug when software changes it behavior and is crashing, when there is something missing in the environment. At least this should be documented, if apc is a hard requirement (and checked by the application when starting and throwing an error message). Enabling apc is in this case just a "workaround".
So can you please reopen the issue so it can be fixed?

jowi24 · 2021-02-23T07:23:50Z

The apc.enable_cli workaround does not work here (21.0.0, Alpine Linux 3.13, PHP 7.4.15).

tflidd · 2021-02-23T07:40:51Z

@waja it looks like a regression for me because it worked without this option before and it's only recommended for the cronjob.

fds-code · 2021-02-23T09:06:15Z

Similar issue here on Ubuntu server 20.10, php 7.4, MariaDB 10.3, whatever amount of memory I allocate to my Nextcloud instance gets exhausted.
I tried the apc_enable_cli workaround but it didn't change anything it still ends up being OOM-killed
the command I'm being asked to run is php occ db:add-missing-indices.
Also, no Cron jobs can complete, they also run out of memory.

Thanks for your help

s644 · 2021-02-23T09:17:17Z

I tried the apc_enable_cli workaround but it didn't change anything it still ends up being OOM-killed

Just in case: it is apc.enable_cli with a dot. It's working for me with the changed config file. Maybe also check, if you are using the correct php version and try running it with explicit version command e.g. php7.4 -f /var/www/nc/cron.php.

Edit: added version info

OMV 5.6.0-1/Debian GNU/Linux 10 (buster)
PHP 8.0.2 (cli)

st3iny · 2021-02-23T10:05:24Z

I ran git bisect and the commit a745d58 seems to be introducing this regression.

fds-code · 2021-02-23T10:10:39Z

I tried the apc_enable_cli workaround but it didn't change anything it still ends up being OOM-killed

Just in case: it is apc.enable_cli with a dot. It's working for me with the changed config file. Maybe also check, if you are using the correct php version and try running it with explicit version command e.g. php7.4 -f /var/www/nc/cron.php.

Thanks for your reply.
sorry I did use apc.enable_cli, I typed it above rather than copy/paste.
I also tried both php and php7.4

EDIT: my mistake it worked with apc.enable_cli=1

Anrock · 2021-04-15T11:19:49Z

Was there any comments from maintainers about fixing this or apcu is mandatory now?

WNYmathGuy · 2021-04-15T14:13:17Z

I can't enable accessibility no more, though. Not sure what that app does anyway, so it's fine if nobody notices.

It's the start of special needs tweaks for the system, like a dyslexia-friendly font.

cyberpower678 · 2021-04-15T15:09:12Z

Was there any comments from maintainers about fixing this or apcu is mandatory now?

Set your log_level to 2 in you config. That’s all in need to do.

PascalReintjens · 2021-04-18T11:08:15Z

In my case, the system started allowing so much memory that it would make the machine inaccessible. I'm going to lower the maximum amount of memory allowed to PHP... I almost lost a drive with the 3 reboots I had to do because of this, a filesystem got corrupt.
I'm very worried about upcoming updates.

allowing PHP to use more memory than you have or filesystem corruption are both not issues related to nextcloud, these are issues for themselves.

That may be so, but a bug that is so dramatic that it has the potential to tear down not quite cleanly set up servers is still a huge problem in my eyes. On servers that are not only running nextcloud, this can have far-reaching consequences for other services. This will happen to many and in my opinion is so critical that it should block the further rollout of Nextcloud 21 until the problem is fixed.

RealSnoopyDog · 2021-04-24T13:22:18Z

The changeset which has caused this issue is known. Someone made a critical modification after the testing of the last release candidate 2 for Nextcloud 21 was finished short before Nextcloud 21.0.0 was released. This is not a good strategy. If you install Nextcloud 21RC2 then you don't have this bug.

TheRaven500 · 2021-04-24T14:36:47Z

The changeset which has caused this issue is known. Someone made a critical modification after the testing of the last release candidate 2 for Nextcloud 21 was finished short before Nextcloud 21.0.0 was released. This is not a good strategy. If you install Nextcloud 21RC2 then you don't have this bug.

This is not true, i reported this bug during the beta phase and again after RC1 was released.
Here: #26154

RealSnoopyDog · 2021-04-27T17:30:48Z

TheRaven500:
You are confusing things!

You are talking about NC21.0.1 RC1
I was talking about NC21.0.0 RC2 (the version BEFORE NC21.0.1 that you refer to)

NC21.0.0 RC 2 does NOT have this bug. NC21.0.0 Release introduced it.

Your report (26154) you are linking to was created on 16. March 2021 and is a duplicate of this one which was added on 22. Februar 2021.

The bug was introduced short BEFORE NC21.0.0 was released and AFTER NC21.0.0 RC2 was out for testing.
All this (including the changeset which introduced the problem) was written here some lines above.

I am still using Nextcloud 21.0.0 RC2 and I don't have this bug.

ghost · 2021-04-27T21:12:28Z

Just updated to NC 21.0.1. Managed to consume 24 GB RAM and then 24 GB of SWAP. Caught it just in time to stop the server crashing. PHP is limited to 18 GB on my system, APCu is already enabled, log level is already at 2.

Considering the comments reporting this issue, and just how crippling it is, I don't understand why it's still available for people to run the update.

TheRaven500 · 2021-04-29T06:04:02Z

@RealSnoopyDog:
You may be right, but it doesn't really matter who is right. It is a serious bug and should be fixed as soon as possible!

RealSnoopyDog · 2021-04-29T07:48:05Z

Yes. But not "may". Talking about software and bugs is not guessing, it is based on facts. And everything was written here already (not by me, I only repeated what was found by others).

GLLM · 2021-05-04T18:37:09Z

Hi

Ubuntu 20.04.2 LTS here. I had the crash as well,
changing from ‘loglevel’ => 0, to ‘loglevel’ => 2, worked for me.
Just FYI
GLLM

ghost · 2021-05-25T09:46:43Z

I'm getting a notification that 21.0.2 is available for upgrade.

Can I assume that as this bug is still open, it's likely to try and cripple my server all over again?

hrsto · 2021-05-25T18:12:45Z

I'm getting a notification that 21.0.2 is available for upgrade.

Can I assume that as this bug is still open, it's likely to try and cripple my server all over again?

In my particular case it eats all memory and forces me to kill the php process. I did disable the accessibility app and set loglevel to 2, but when i start the update process again, it resets loglevel back to 0 and screws up again.

makuser · 2021-05-25T18:39:28Z

I'm getting a notification that 21.0.2 is available for upgrade.
Can I assume that as this bug is still open, it's likely to try and cripple my server all over again?

In my particular case it eats all memory and forces me to kill the php process. I did disable the accessibility app and set loglevel to 2, but when i start the update process again, it resets loglevel back to 0 and screws up again.

Have you checked your APC/Redis cache setting, libraries and server?

hrsto · 2021-05-25T18:50:05Z

I'm getting a notification that 21.0.2 is available for upgrade.
Can I assume that as this bug is still open, it's likely to try and cripple my server all over again?

In my particular case it eats all memory and forces me to kill the php process. I did disable the accessibility app and set loglevel to 2, but when i start the update process again, it resets loglevel back to 0 and screws up again.

Have you checked your APC/Redis cache setting, libraries and server?

nextcloud instance itself runs in its own container by itself. Redis and the database are in a different container. The nextcloud container is the one that has the memory leak. Haven't checked libraries - do you have any specific ones in mind (fyi, i'm not experienced with php)?

Since it's a personal cloud server that i've already backed up, i tried this workaround #25742 (comment) and so far everything seems to be in order.

makuser · 2021-05-25T18:58:01Z

I'm getting a notification that 21.0.2 is available for upgrade.
Can I assume that as this bug is still open, it's likely to try and cripple my server all over again?

In my particular case it eats all memory and forces me to kill the php process. I did disable the accessibility app and set loglevel to 2, but when i start the update process again, it resets loglevel back to 0 and screws up again.

Have you checked your APC/Redis cache setting, libraries and server?

nextcloud instance itself runs in its own container by itself. Redis and the database are in a different container. The nextcloud container is the one that has the memory leak. Haven't checked libraries - do you have any specific ones in mind (fyi, i'm not experienced with php)?

In my case changing the nextcloud loglevel absolutely nothing. I removed the php-redis package/library by mistake, which led to nextcloud being unable to use said caching service. Reinstalling that library fixed it. Removing it broke it again. Switching to memcache by installing the daemon and php libraries and changing the nextcloud config appropriately fixed it, removing the libraries/package broke it again.
So in my case it was all dependent on the nextcloud cache interface.

And sure, it's nextcloud that blows up, not any other service. So it absolutely makes sense that the nexcloud container is the one that dies, if you are using a containerized setup.

That is why I recommended to check your cache settings and your installed php libraries in your nextcloud container.

KoganeNoKenshi · 2021-05-27T08:25:57Z

Installing php7.4-xml and php8.0-xml fixed it for me.

RealSnoopyDog · 2021-05-27T08:34:44Z

This is not a fix for the real problem, it is a workaround (like all other hints)

- fixes 'allowed memory size exhausted' during nextcloud upgrades/occ execution - nextcloud/server#25742 - nextcloud/server#25770

lars-becker · 2021-06-04T10:40:35Z

I haven't had this problem until NC 22 Beta 3. Now I have the same error. Removing solves APCu resolves the problem but is not in line with the recommendations in the adminstration manual.

…rades/occ execution: - enable acpu cache/accelerator for php CLI - disable accessibility app - nextcloud/server#25742 - nextcloud/server#25770

chriscroome · 2022-02-15T17:01:03Z

Posting this here in case it helps anyone else...

You can check the PHP memory limit using the command line like this:

php -r "phpinfo();" | grep memory_limit
memory_limit => 128M => 128M

With the above defaults I was unable to upgrade Nextcloud:

php updater/updater.phar --no-backup
...
PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 167968632 bytes) in phar:///home/cloud/sites/nextcloud/updater/updater.phar/lib/Updater.php on line 637

However after creating a ~/.php.ini file containing:

memory_limit = -1

And then running the update using this ini file:

php --php-ini ~/.php.ini updater/updater.phar --no-backup

There isn't a problem with the updater.

As far as I can tell you don't need to enable the OPCache or APCu for the CLI, the upgrade works for me with these settings:

php -r "phpinfo();" | grep enable_cli
apc.enable_cli => Off => Off
opcache.enable_cli => Off => Off

lionants02 · 2022-02-21T10:23:00Z

I'm using PHP CLI param -d memory_limit=4096M
Work for me.
Nextcloud version 21.0.3
I'm docker.

How to
STEP 1

config.php is set 'loglevel' => 2,
run command wait 1 hour and CTRL+C.

STEP 2 run command wow!!

STEP 1

STEP 2

AlfaVila · 2023-02-07T20:09:52Z

sudo --u www-data php --define memory_limit=512M /var/www/html/occ files:scan --all

onny added 0. Needs triage Pending check for reproducibility or if it fits our roadmap bug labels Feb 22, 2021

hoellen mentioned this issue Feb 22, 2021

Upgrade to Nextcloud 21.0 fails hoellen/dockerfiles#47

Closed

onny closed this as completed Feb 23, 2021

tflidd reopened this Feb 23, 2021

kesselb mentioned this issue Apr 15, 2021

Internal Server Error after Upgrade from 20.0.6 to 21.0.1 - no login possible anymore #26573

Closed

blizzz closed this as completed in #25770 May 27, 2021

nodiscc added a commit to nodiscc/xsrv that referenced this issue May 29, 2021

apache/php: enable acpu cache/accelerator for php CLI

67499e7

- fixes 'allowed memory size exhausted' during nextcloud upgrades/occ execution - nextcloud/server#25742 - nextcloud/server#25770

kesselb mentioned this issue Jun 2, 2021

OCC command returns an exit code without any message #27321

Closed

jgelauff mentioned this issue Jun 7, 2021

Nextcloud 21.0.2 NethServer/dev#6506

Closed

jospoortvliet mentioned this issue Jun 22, 2021

OPcache recommendation wrong (opcache.enable_cli=1) nextcloud/documentation#1439

Closed

[NC 21] OCC Update error: allowed memory size exhausted #25742

[NC 21] OCC Update error: allowed memory size exhausted #25742

Comments

onny commented Feb 22, 2021 • edited Loading

How to use GitHub

Steps to reproduce

Expected behaviour

Actual behaviour

Server configuration

Client configuration

Nextcloud log (data/nextcloud.log)

dschrempf commented Feb 22, 2021

kde35 commented Feb 22, 2021

tbasilici commented Feb 22, 2021

kde35 commented Feb 22, 2021

onny commented Feb 22, 2021 • edited by caugner Loading

st3iny commented Feb 22, 2021

onny commented Feb 22, 2021

onny commented Feb 22, 2021 • edited Loading

onny commented Feb 22, 2021 • edited Loading

Temtaime commented Feb 22, 2021 • edited Loading

st3iny commented Feb 22, 2021

Xiretza commented Feb 22, 2021 • edited Loading

yapbreak commented Feb 22, 2021

tflidd commented Feb 22, 2021 • edited Loading

madpilot78 commented Feb 22, 2021

RealSnoopyDog commented Feb 22, 2021

andreaslutsch commented Feb 23, 2021 • edited Loading

nextcloud486153 commented Feb 23, 2021

waja commented Feb 23, 2021

jowi24 commented Feb 23, 2021 • edited Loading

tflidd commented Feb 23, 2021

fds-code commented Feb 23, 2021

s644 commented Feb 23, 2021 • edited Loading

st3iny commented Feb 23, 2021

fds-code commented Feb 23, 2021 • edited Loading

Anrock commented Apr 15, 2021

WNYmathGuy commented Apr 15, 2021

It's the start of special needs tweaks for the system, like a dyslexia-friendly font.

cyberpower678 commented Apr 15, 2021

PascalReintjens commented Apr 18, 2021 • edited Loading

RealSnoopyDog commented Apr 24, 2021

TheRaven500 commented Apr 24, 2021

RealSnoopyDog commented Apr 27, 2021

ghost commented Apr 27, 2021

TheRaven500 commented Apr 29, 2021

RealSnoopyDog commented Apr 29, 2021

GLLM commented May 4, 2021

ghost commented May 25, 2021

hrsto commented May 25, 2021

makuser commented May 25, 2021

hrsto commented May 25, 2021

makuser commented May 25, 2021 • edited Loading

KoganeNoKenshi commented May 27, 2021

RealSnoopyDog commented May 27, 2021

lars-becker commented Jun 4, 2021

chriscroome commented Feb 15, 2022

lionants02 commented Feb 21, 2022 • edited Loading

STEP 1

STEP 2

AlfaVila commented Feb 7, 2023

onny commented Feb 22, 2021 •

edited

Loading

onny commented Feb 22, 2021 •

edited by caugner

Loading

onny commented Feb 22, 2021 •

edited

Loading

onny commented Feb 22, 2021 •

edited

Loading

Temtaime commented Feb 22, 2021 •

edited

Loading

Xiretza commented Feb 22, 2021 •

edited

Loading

tflidd commented Feb 22, 2021 •

edited

Loading

andreaslutsch commented Feb 23, 2021 •

edited

Loading

jowi24 commented Feb 23, 2021 •

edited

Loading

s644 commented Feb 23, 2021 •

edited

Loading

fds-code commented Feb 23, 2021 •

edited

Loading

PascalReintjens commented Apr 18, 2021 •

edited

Loading

makuser commented May 25, 2021 •

edited

Loading

lionants02 commented Feb 21, 2022 •

edited

Loading