Nextcloud 30 warnings after upgrade

[crimson]

Hello.

Yesterday I’ve upgraded to Nextcloud 30. I’m using the community docker image. Since the upgrade I’ve been getting caldav warning
(see screenshot).

Before the upgrade, on Nextcloud 29 I haven’t had this issue. There was also an issue (at least on GitHub) which was closed about caldav/carddav and a trailing / in the URL.

As far as I can see dav services are working on my phone, so the warning seems to not be correct?

I’ve also been getting integrity check errors regarding nextcloud-init-sync.lock. What’s weird is that the file is owned by root and it has 0 bytes. I’ve tried deleting it which works but sometimes after a container reboot it is back.

[Sanook]

@crimson

integrity check errors

Frequent Nextcloud 30 (Hub 9) update issues

Hi community, as Nextcloud 30 (Hub 9) has landed (see release intro) it’s time to bundle frequent issues into a WIKI post (everybody is welcome to add content) to help users to find solutions for frequent issues after update to NC30. This should avoid flooding forum with similar topics and help others identify and solve known issues. look at the topics with nc30 and setup_warning tags and both together Topics tagged nc30 & setup_warning …sometimes issues repeat/reoccur especially if you jump o…

[wwe]

@crimson

I’ve also been getting integrity check errors regarding nextcloud-init-sync.lock. What’s weird is that the file is owned by root and it has 0 bytes.

I’ve seen this in the past… AFAIR changing the owner to www-data resolves the problem.

[jason_marinaro]

Hey, all… I think that I have fixed some of the errors in the past by doing a manual upgrade ‘here’. It may be because of the permissions and ownership…Everything in nextcloud should belong to www-data. I hope this maybe helps. You don’t have to do the whole upgrade, but just do the permission and file octal checks…

[jtr]

@crimson

I’ve also been getting integrity check errors regarding nextcloud-init-sync.lock.

This is an interaction between a change in server and the way the Docker image locks the update process to prevent problems in environments with multiple app containers. It’s been fixed and will flow out when the v30.0.1 maintenance release is published. You can ignore that warning for the next couple weeks. It has no operational impact. The check has been adjusted to ignore that file once again.