bunker Alf06 Hi, I'm so sorry to not understand to everything is said here. Not sure I know how to proceed. reverted the files update with the still available copy in community.old/20230125/openSUSE_Leap_15.3/ Where can i get there?? adjust download-source, How can I do that ?? and revert zypper in -f grommunio-files-10.9.1 i go to wait for a later update.
Alf06 bunker Hi bunker, if you start yast Software - Software repositories you should see source of grommunio-community Edit this entry and modify the url to : https://download.grommunio.com/community.old/20230125/openSUSE_Leap_15.3/ save and exit revert the files update with: zypper in -f grommunio-files-10.9.1 once reverted optional: zypper addlock grommunio-files to prevent updates then return in Software repository to url = https://download.grommunio.com/community/openSUSE_Leap_15.3/
WalterH Update to SuSE 15.4: https://community.grommunio.com/d/792-update-form-open-suse-153-to-154 , my system is on SuSE 15.4 and works.
bunker Ok so now the solution is to upgrade completly. Why do you break previous system with bad updates then ? This is very disapointing.. I'm ok to upgrade. But does it works this time? Is it ready now? Does poeple that liked WalterH comment means that the upgrade works for you? Was it a smooth upgrade?
WalterH bunker I am not a grommunio employ. I support my grommunio customers. So I get some experience with Linux and grommunio. For me the update was easy and smooth. PHP 7 is outdated, the switch vom OC to NC was done because OC do not support PHP8 bit SuSE 15.4 only supplies PHP8.
THE_FRICKLER WalterH my Update today was also without any error. Primary installed late 2021, now on 15.4! Simply used "CORE" in the Suse Based APP as VM
bunker Thanks Alf06. That's did the trick for files. Files is now functional. 🙂 Still no luck with webmail. Not my first choice but I will now look to upgrade to fix webmail issue.. Thank's all !
Alf06 bunker Hi bunker, did you already purged the opcache stuff? is your gromox up to date? rpm -qi gromox = gromox-2.5.11.7e2fe81 or 2.5.40.4036388 ? if not - then do: zypper in gromox and select to clean opcache or as written in an answer above: rpm -e php7-opcache oder rpm -e php8-opcache (je nach aktuellem Stand), danach systemctl restart php-fpm
liske We ran in the same issue on Debian bullseye. Uninstalling php7.4-opcache is no option since it is a hard dependency for grommunio. As a workaround we just disabled the module:
jengelh liske Uninstalling php7.4-opcache is no option since it is a hard dependency for grommunio. The current set of packages does not require opcache (this was already changed on 2023-02-27; ISO description edited today).
liske jengelh oh so on Debian it seems to be a dependency of php itself: # apt-cache rdepends --installed php7.4-opcache php7.4-opcache Reverse Depends: php7.4-fpm php7.4-cli php7.4-fpm php7.4-cli
WalterH liske this is an endless discussion, you find threads in this forum where this behavior was already explained. This is a dependency for PHP on Debian. No need to waste time to pop up the same behavior again and again.