Nextcloud 28 Upgrade - Works but Admin Overview fails to see 'sodium' module?
All, Nextcloud server was updated to 28. The upgrade went well, but with a slight nit in the Admin -> Overview check. It lists: <quote> This instance is missing some recommended PHP modules. For improved performance and better compatibility it is highly recommended to install them: sodium. For more details see the documentation ↗. </quote> It is complaining that php-legacy-sodium wasn't installed, so we installed in and enabled the module in /etc/webapps/nextcloud/php.ini, (with a "systemctl reload httpd" in between each test) still not seen by nextcloud, so we enabled in it /etc/php-legacy/php-fpm.ini, still not seen by nextcloud, so we enabled it in the main /etc/php-legacy/php.ini -- still not seen by nextcloud -- but it is happily enabled: # php-legacy -m | grep -i sodium sodium No errors in /var/log/httpd/error.log No new errors in /var/log/nextcloud/nextcloud.log, just the nagging warning that has been there forever: "message":"Module \"apcu\" is already loaded at Unknown#0" Anybody know why nextcloud 28 Admin->Overview tells you it wants sodium, but then doesn't see it once it is installed. -- David C. Rankin, J.D.,P.E.
On Friday, 12 January 2024 at 21:35 (-0600), David C. Rankin wrote:
Nextcloud server was updated to 28. The upgrade went well, but with a slight nit in the Admin -> Overview check. It lists:
<quote>
This instance is missing some recommended PHP modules. For improved performance and better compatibility it is highly recommended to install them: sodium. For more details see the documentation ↗.
</quote>
It is complaining that php-legacy-sodium wasn't installed, so we installed in and enabled the module in /etc/webapps/nextcloud/php.ini, (with a "systemctl reload httpd" in between each test) still not seen by nextcloud, so we enabled in it /etc/php-legacy/php-fpm.ini, still not seen by nextcloud, so we enabled it in the main /etc/php-legacy/php.ini -- still not seen by nextcloud -- but it is happily enabled:
# php-legacy -m | grep -i sodium sodium
No errors in /var/log/httpd/error.log
No new errors in /var/log/nextcloud/nextcloud.log, just the nagging warning that has been there forever:
"message":"Module \"apcu\" is already loaded at Unknown#0"
Anybody know why nextcloud 28 Admin->Overview tells you it wants sodium, but then doesn't see it once it is installed.
I had the same warning after upgrading Nextcloud, I made the same steps (installed and enabled sodium in php.ini, restarted php-fpm), and after a minute or so the warning vanished from the Nextcloud admin page. One big difference, however, is that I'm using php and not php-legacy. Jaron
On 1/13/24 01:17, Jaron Kent-Dobias wrote:
I had the same warning after upgrading Nextcloud, I made the same steps (installed and enabled sodium in php.ini, restarted php-fpm), and after a minute or so the warning vanished from the Nextcloud admin page. One big difference, however, is that I'm using php and not php-legacy.
Thank you, Yes, there may be a naming issue with it finding php-legacy-sodium. It's happily running. Checking the phpinfo page: sodium sodium support enabled libsodium headers version 1.0.19 libsodium library version 1.0.19 The warning does not go away with the install on php-legacy. I'm surprised you have it running on php (8.2). The whole reason I installed php-legacy was the Arch wiki page said there were problems with using php and suggested the downgrade. Other than the annoying warning, everything is working fine, but the screen real estate issue got worse in Nextcloud 28 with fonts appearing bigger and sparse information per-page in each app. The upside is the page-load times switching apps (e.g. notes to calendar, etc...) are much improved. Not great, but definitely improved. -- David C. Rankin, J.D.,P.E.
Since nobody in this thread either reported the bug or edited the wiki, I've at least done the former. https://gitlab.archlinux.org/archlinux/packaging/packages/nextcloud/-/issues... Would be nice if someone else fixes the wiki up. Martin On Sun, Jan 14, 2024 at 3:06 AM David C. Rankin <drankinatty@gmail.com> wrote:
On 1/13/24 01:17, Jaron Kent-Dobias wrote:
I had the same warning after upgrading Nextcloud, I made the same steps (installed and enabled sodium in php.ini, restarted php-fpm), and after a minute or so the warning vanished from the Nextcloud admin page. One big difference, however, is that I'm using php and not php-legacy.
Thank you,
Yes, there may be a naming issue with it finding php-legacy-sodium. It's happily running. Checking the phpinfo page:
sodium sodium support enabled libsodium headers version 1.0.19 libsodium library version 1.0.19
The warning does not go away with the install on php-legacy. I'm surprised you have it running on php (8.2). The whole reason I installed php-legacy was the Arch wiki page said there were problems with using php and suggested the downgrade.
Other than the annoying warning, everything is working fine, but the screen real estate issue got worse in Nextcloud 28 with fonts appearing bigger and sparse information per-page in each app. The upside is the page-load times switching apps (e.g. notes to calendar, etc...) are much improved. Not great, but definitely improved.
-- David C. Rankin, J.D.,P.E.
On 1/14/24 07:13, Martin Rys wrote:
Since nobody in this thread either reported the bug or edited the wiki, I've at least done the former.
https://gitlab.archlinux.org/archlinux/packaging/packages/nextcloud/-/issues...
Would be nice if someone else fixes the wiki up.
Martin
I've tried, many times, but all my additions are rolled-back and reversed. So it's not worth the effort anymore... -- David C. Rankin, J.D.,P.E.
Please stop misleading users with your unjustified thoughts about ArchWiki. The last time (and the only time you complained about) your mainspace additions got reverted, you added information that was already available, significantly in the past, and blatantly against the wiki's style. You have not made any edits since then and have not attempted to add this information about nextcloud. Recipients interested on the situation may read https://lists.archlinux.org/hyperkitty/list/arch-general@lists.archlinux.org.... -- Cheers, Aᴀʀᴏɴ
I've only installed php-legacy-sodium and enabled sodium in /etc/webapps/nextcloud/php.ini and restart the webserver. The missing sodium message is still in the webcheck but "occ setupcheck" doesn't complain about missing sodium anymore. I'm also having the webcheck complaining about memcache while occ does not. For me the only NC28 issue is a broken cookbook now. -Andy
participants (5)
-
Aaron Liu
-
Andreas Radke
-
David C. Rankin
-
Jaron Kent-Dobias
-
Martin Rys