Desktop client 3.4.4, Nextcloud 23.0.3 and 22.2.6 are out, bringing a series of bug fixes and improvements

📰 News
3

Thanks for pointing out the broken link @LogsCon. It’s fixed now :slight_smile:

4

thankyou! updated fine here 23.0.2->23.0.3 so far so good!

5

whoops, fixed. Made a mess though, first thinking the 23.0.3 was wrong and it should be 23.0.4 :sob:
But I think all is now :sun_with_face: :sunflower:

1 Like
6

It seems server 23.0.4 is not out yet.
The server download URL returns a 404.

1 Like
7

the release is 23.0.3, the .4 was a mistake in the changelog generation that confused, well, everyone including me :wink:

1 Like
8

I installed the 3.5.0 RC1 desktop client on my Debian Notebook (compiled from source) and it seems to run fine. No issues so far.

9

I’m encountering the following error upgrading to 22.2.6

$ ./occ upgrade          
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Setting log level to debug
Updating database schema
Updated database
An unhandled exception has been thrown:
Error: Call to undefined function GuzzleHttp\Psr7\modify_request() in /var/www/labfoto.it/nextcloud/3rdparty/php-opencloud/openstack/src/Common/Auth/AuthHandler.php:56
Stack trace:
#0 /var/www/labfoto.it/nextcloud/3rdparty/guzzlehttp/guzzle/src/PrepareBodyMiddleware.php(35): OpenStack\Common\Auth\AuthHandler->__invoke()
#1 /var/www/labfoto.it/nextcloud/3rdparty/php-opencloud/openstack/src/Common/Transport/Middleware.php(22): GuzzleHttp\PrepareBodyMiddleware->__invoke()
#2 /var/www/labfoto.it/nextcloud/3rdparty/guzzlehttp/guzzle/src/HandlerStack.php(75): OpenStack\Common\Transport\Middleware::OpenStack\Common\Transport\{closure}()
#3 /var/www/labfoto.it/nextcloud/3rdparty/guzzlehttp/guzzle/src/Client.php(331): GuzzleHttp\HandlerStack->__invoke()
#4 /var/www/labfoto.it/nextcloud/3rdparty/guzzlehttp/guzzle/src/Client.php(168): GuzzleHttp\Client->transfer()
#5 /var/www/labfoto.it/nextcloud/3rdparty/guzzlehttp/guzzle/src/Client.php(187): GuzzleHttp\Client->requestAsync()
#6 /var/www/labfoto.it/nextcloud/3rdparty/php-opencloud/openstack/src/Common/Api/OperatorTrait.php(115): GuzzleHttp\Client->request()
#7 /var/www/labfoto.it/nextcloud/3rdparty/php-opencloud/openstack/src/Common/Api/OperatorTrait.php(123): OpenStack\Common\Resource\OperatorResource->sendRequest()
#8 /var/www/labfoto.it/nextcloud/3rdparty/php-opencloud/openstack/src/Common/Resource/OperatorResource.php(55): OpenStack\Common\Resource\OperatorResource->execute()
#9 /var/www/labfoto.it/nextcloud/3rdparty/php-opencloud/openstack/src/ObjectStore/v1/Models/Container.php(142): OpenStack\Common\Resource\OperatorResource->executeWithState()
#10 /var/www/labfoto.it/nextcloud/lib/private/Files/ObjectStore/SwiftFactory.php(266): OpenStack\ObjectStore\v1\Models\Container->getMetadata()
#11 /var/www/labfoto.it/nextcloud/lib/private/Files/ObjectStore/SwiftFactory.php(247): OC\Files\ObjectStore\SwiftFactory->createContainer()
#12 /var/www/labfoto.it/nextcloud/lib/private/Files/ObjectStore/Swift.php(62): OC\Files\ObjectStore\SwiftFactory->getContainer()
#13 /var/www/labfoto.it/nextcloud/lib/private/Files/ObjectStore/Swift.php(105): OC\Files\ObjectStore\Swift->getContainer()
#14 /var/www/labfoto.it/nextcloud/lib/private/Files/ObjectStore/ObjectStoreStorage.php(312): OC\Files\ObjectStore\Swift->readObject()
#15 /var/www/labfoto.it/nextcloud/lib/private/Files/Storage/Common.php(196): OC\Files\ObjectStore\ObjectStoreStorage->fopen()
#16 /var/www/labfoto.it/nextcloud/lib/private/Files/Storage/Wrapper/Wrapper.php(247): OC\Files\Storage\Common->file_get_contents()
#17 /var/www/labfoto.it/nextcloud/lib/private/Files/Storage/Wrapper/Availability.php(264): OC\Files\Storage\Wrapper\Wrapper->file_get_contents()
#18 /var/www/labfoto.it/nextcloud/lib/private/Files/Storage/Wrapper/Wrapper.php(247): OC\Files\Storage\Wrapper\Availability->file_get_contents()
#19 /var/www/labfoto.it/nextcloud/lib/private/Files/View.php(1171): OC\Files\Storage\Wrapper\Wrapper->file_get_contents()
#20 /var/www/labfoto.it/nextcloud/lib/private/Files/View.php(601): OC\Files\View->basicOperation()
#21 /var/www/labfoto.it/nextcloud/lib/private/Files/Node/File.php(56): OC\Files\View->file_get_contents()
#22 /var/www/labfoto.it/nextcloud/lib/private/Files/SimpleFS/SimpleFile.php(90): OC\Files\Node\File->getContent()
#23 /var/www/labfoto.it/nextcloud/lib/private/App/AppStore/Fetcher/Fetcher.php(154): OC\Files\SimpleFS\SimpleFile->getContent()
#24 /var/www/labfoto.it/nextcloud/lib/private/Installer.php(432): OC\App\AppStore\Fetcher\Fetcher->get()
#25 /var/www/labfoto.it/nextcloud/lib/private/Updater.php(427): OC\Installer->isUpdateAvailable()
#26 /var/www/labfoto.it/nextcloud/lib/private/Updater.php(273): OC\Updater->upgradeAppStoreApps()
#27 /var/www/labfoto.it/nextcloud/lib/private/Updater.php(132): OC\Updater->doUpgrade()
#28 /var/www/labfoto.it/nextcloud/core/Command/Upgrade.php(235): OC\Updater->upgrade()
#29 /var/www/labfoto.it/nextcloud/3rdparty/symfony/console/Command/Command.php(255): OC\Core\Command\Upgrade->execute()
#30 /var/www/labfoto.it/nextcloud/3rdparty/symfony/console/Application.php(1009): Symfony\Component\Console\Command\Command->run()
#31 /var/www/labfoto.it/nextcloud/3rdparty/symfony/console/Application.php(273): Symfony\Component\Console\Application->doRunCommand()
#32 /var/www/labfoto.it/nextcloud/3rdparty/symfony/console/Application.php(149): Symfony\Component\Console\Application->doRun()
#33 /var/www/labfoto.it/nextcloud/lib/private/Console/Application.php(209): Symfony\Component\Console\Application->run()
#34 /var/www/labfoto.it/nextcloud/console.php(99): OC\Console\Application->run()
#35 /var/www/labfoto.it/nextcloud/occ(11): require_once('...')
#36 {main}%
10

@lrkwz

Please open a new thread in the support section and use the issue template. This thread is a news item and not the appropriate place to ask for technical support. Also we would need more info to be able to help. That’s where the issue template comes into play
 :wink: If I had to guess, I would say it’s probably a third party app that is causing the issue


11

ok, thank you and sorry. Thread is Error upgrading to 22.2.6

12

I have an uncertainty I was wanting to clear up, with respect to an upgrade from NC 23.0.2 to NC 23.0.3 here.

If anyone is familiar with the behaviour of NC’s “updater.phar” CLI utility, I would greatly appreciate your input.

13

Please look at the OPcache warnings problems.
OPcache is created per PHP version on the server. The cache is by default not user based.
So one can set these values to extremes and stil get warnings.
Why is OPcache needed next to Redis that is user based? This config is in the manual.

1 Like
14

Same problem here.
The provider support for my webserver sais (german):
dieses Problem tauchte mit der aktuellen Version von Nextcloud auf, wir haben die “Fehlermeldung” Intern geprĂŒft und das gleiche Ergebnis erhalten wie Sie.

GrundsĂ€tzlich haben weitere PrĂŒfungen ergeben das diese Meldung bis auf das sie angezeigt wird und das als störend empfunden werden kann, keinerlei Auswirkungen auf die Funktionsweise der Nextcloud hat.

15

Aber ziemlich sicher auf die Performance. :wink:

But most likely on the performance. :wink:

If you want to have full control, web hosting packages are rather suboptimal and often limited in terms of tuning options. But basically the hosting provider is right: Warnings are not error messages and can be ignored with Nextcloud still working. Whether you need or want to have the feature or the optimization that a particular warning message suggests, is of course another story


16

Good to hear!!

17

When the server is used by multiple clients, this warning should be given by all installed applications that use the same PHP version. So it does not concern NC only.
The warning states it is a ‘configuration error’. But that is not the case. It is default behavior of OPcache. This type of cache is on server level, not per user in default installations. That is why you can ‘upgrade’ all vars, untill you have reached max server memory and alle files.
The OPcache situation that is evaluated by NC script can only be archieved as successfull when the server PHP version only serves one NC installation and perhaps a simple website. Those are my findings.
In my opinion this is not a configuration error, but just ‘information’ that should not lead to a missing V in the results. There could be just this info below that. It is not an error, nor a security problem.

18

Maybe there are some implications that even you or your hosting company doesn’t know about, that are important enough for the Nextcloud devs to implemet this warning. And for this purpose, they used the already integrated messaging system and do not want to program a hole new system. You can always argue about the wording and of course you can always make things better. In the end, it comes down to priorities and the amount of work involved. Feel free to open an issue or a pull request on GitHub, with your suggestions


19

Maybe, but we’re not perfect either of course. Maybe it is a little over the top. But if you, as admin, are sure that it is OK, then I guess you can deal with a single red issue getting reported, I hope.

And of course - a well argued pull request to improve things (like, downgrade to yellow warning, or perhaps some detection method of how bad things are) would be super welcome - @Hendrik might know enough to do that!

1 Like
20

We host our own server for multiple clients. And our server is fine and up-to-date. I know after investigation that these warnings are not relevant. But clients get confused since they always got a green V after this configuration control.
I’d suggest a config option Y/N for this control item. There are just two small blocks of code that need an If 
 before executing.

The Opcache check is done in /settings/lib/CheckSetupControler.php
Line 506 says: // Recommend to raise value, if more than 90% of max value is reached
Disable the If block below that line to disable this warning.
After this there is a memory check If block that is OK.
Below that block is the " if (
empty($status[‘interned_strings_usage’][‘free_memory’]) || "
That needs also to be disabled.
I’ve put /* 
 */ around those checks.

Perhaps NC can find a nice option to make these checks only done when a result can be expected. In our situation even 32G memory gave these warnings after some time.
And, in fact this Opcache problem is not a NC problem, but with the design of Opcache behavior.

21

I’m guessing you clients pay you for your time, so perhaps spend some of that paid time on creating a pull request
 or pay somebody to do it. Like you, most people like to help out a fellow volunteer, or get paid to help somebody else who is paid. That seems fair, right? It’s either business, or it’s not.

22

I do not know how I should make a pull request.
In the past I have informed NC about things that I found, and they repaired those in the next release. That is why I have explained what is going wrong, why and where.

I do not fine our clients for those things and the research I do. That is my contribution as volonteer to the NC org. Most clients that use NC with us are local organisations, groups and local political parties. They have all small budgets and we respect that. For other business clients we have Synology NAS systems that we manage.