https://bugs.koozali.org/show_bug.cgi?id=12298
--- Comment #20 from Jean-Philippe Pialasse <[email protected]> ---
(In reply to Gary Douglas from comment #19)
> one thought, I updated 2x NC to ver 27 with custom-templates a couple of
> months ago and never had segfault opcache.so issues with them. thank you for
> this;
> > I can make it stop by simply
> > rm -rf /var/lib/php/nextcloud/opcache/*
> > systemctl restart php81-php-fpm.service
not that long since updating but issue started after last update.
what I think is creating the issue is the file cache that is used in place of
the in memory when it restarts. this cache is not deleted upon restart.
looking at few reports this is its purpose to allow fast restart, but might
create issue if not valid or for another reason to be determined. a lot of
reports about that either related to nextcloud either directly between
apc/opcache and php8.1
https://github.com/php/php-src/issues/8149
https://github.com/php/php-src/issues/9968
https://stackoverflow.com/questions/66446842/what-is-causing-a-segfault-when-opcache-file-cache-is-enabled-in-a-symlink-deplo
https://bugs.php.net/bug.php?id=81607
also a note here apcu could be optimized
apc.enabled=1
apc.shm_size=256M
apc.ttl=7200
apc.enable_cli=1
apc.gc_ttl=3600
apc.entries_hint=4096
apc.slam_defense=1
apc.serializer=php
--
You are receiving this mail because:
You are the QA Contact for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/
