[Bug]: Upgrade 23.0.3 to 23.0.4 docker Server does not migrate #1742

Y0ngg4n · 2022-05-01T12:57:12Z

⚠️ This issue respects the following points: ⚠️

This is a bug, not a question or a configuration/webserver/proxy issue.
This issue is not already reported on Github (I've searched it).
Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
I agree to follow Nextcloud's Code of Conduct.

Bug description

If i want to update my docker Nextcloud installation i get the following issue, that it is waiting forever. But there is no other process running nextcloud.

Configuring Redis as session handler
Initializing nextcloud 23.0.4.1 ...
Upgrading nextcloud from 23.0.3.2 ...
Another process is initializing Nextcloud. Waiting 10 seconds...
Another process is initializing Nextcloud. Waiting 20 seconds...
Another process is initializing Nextcloud. Waiting 30 seconds...
Another process is initializing Nextcloud. Waiting 40 seconds...
Another process is initializing Nextcloud. Waiting 50 seconds...
Another process is initializing Nextcloud. Waiting 60 seconds...
Another process is initializing Nextcloud. Waiting 70 seconds...
Another process is initializing Nextcloud. Waiting 80 seconds...

Steps to reproduce

Upgrade docker install from 23.0.3.2 to 23.0.4

Expected behavior

Just upgrade it

Installation method

Official Docker image

Operating system

Debian/Ubuntu

PHP engine version

No response

Web server

No response

Database engine version

PostgreSQL

Is this bug present after an update or on a fresh install?

Updated from a minor version (ex. 22.2.3 to 22.2.4)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?

Default user-backend (database)
LDAP/ Active Directory
SSO - SAML
Other

Configuration report

No response

List of activated Apps

accessibility  cloud_federation_api  dav                   files             files_sharing      firstrunwizard           notifications    privacy           settings       systemtags             updatenotification  weather_status
activity       comments              encryption            files_external    files_trashbin     logreader                oauth2           provisioning_api  sharebymail    text                   user_ldap           workflowengine
admin_audit    contactsinteraction   federatedfilesharing  files_pdfviewer   files_versions     lookup_server_connector  password_policy  recommendations   support        theming                user_status
circles        dashboard             federation            files_rightclick  files_videoplayer  nextcloud_announcements  photos           serverinfo        survey_client  twofactor_backupcodes  viewer

Nextcloud Signing status

No response

Nextcloud Logs

Log is empty

Additional info

No response

The text was updated successfully, but these errors were encountered:

Mape6 · 2022-05-03T09:26:28Z

I have the exact the same problem. Updated from 23.0.3 to 23.0.4 with same log entries.
I reverted to old image and nextcloud is running again.

Y0ngg4n · 2022-05-03T10:39:44Z

I did the same. I will stick with the older version until this Bug gets fixed.

skjnldsv · 2022-05-04T08:24:06Z

Thanks for reporting. Let's investigate

skjnldsv · 2022-05-04T09:01:21Z

Can anyone here share their setup? How many containers are you running? Are you sharing the html volume between those?
What are you using to run docker? An orchestrator? Pure command line? Compose? Swarm?

Mape6 · 2022-05-04T09:32:45Z

I have docker running on a raspberry pi and manage my containers via docker compose.
I have only one postgres and one nextcloud and one redis container running.

here is my docker compose file content:

volumes:
  data:
  db:

networks:
  frontend:
    name: nc_frontend
  backend:
    name: nc_backend
  reverse-proxy:
    external: true

services:
  postgres:
    container_name: nc_postgres
    image: postgres
    hostname: nc_postgres
    restart: unless-stopped
    command: --transaction-isolation="read committed"
    volumes:
      - db:/var/lib/postgresql/data
    environment:
      - POSTGRES_DB=nextcloud
      - POSTGRES_USER=nextcloud
      - POSTGRES_PASSWORD=xxx
    networks:
      backend:

  redis:
    container_name: nc_redis
    image: redis
    restart: unless-stopped
    networks:
      backend:

  nextcloud:
    container_name: nextcloud
    image: nextcloud
    depends_on:
      - postgres
      - redis
    restart: unless-stopped
    expose:
      - 80
    volumes:
      - data:/var/www/html
    environment:
      POSTGRES_HOST: nc_postgres
      POSTGRES_DB: nextcloud
      POSTGRES_USER: nextcloud
      POSTGRES_PASSWORD: xxx
      NEXTCLOUD_TRUSTED_DOMAINS: xxx
      NEXTCLOUD_TRUSTED_PROXIES: 172.29.0.0/16
      DEFAULT_LANGUAGE: de
      DEFAULT_LOCALE: de
      REDIS_HOST: redis
      MEMCACHE.LOCAL: \OC\Memcache\Redis
      MEMCACHE.LOCKING: \OC\Memcache\Redis
    networks:
      frontend:
      backend:
      reverse-proxy:
    labels:
      - traefik.enable=true
      - traefik.docker.network=reverse-proxy
      # http
      - traefik.http.routers.nextcloud.rule=Host(`xxx`)
      - traefik.http.routers.nextcloud.entrypoints=web
      - traefik.http.routers.nextcloud.middlewares=nextcloud-https-redirect,hsts-header
      # https
      - traefik.http.routers.nextcloud-https.rule=Host(`xxx`)
      - traefik.http.routers.nextcloud-https.entrypoints=websecure
      - traefik.http.routers.nextcloud-https.tls=true
      - traefik.http.routers.nextcloud-https.tls.certresolver=myresolver
      - traefik.http.routers.nextcloud-https.tls.options=default2@file
      - traefik.http.routers.nextcloud-https.middlewares=hsts-header
      # https redirect
      - traefik.http.middlewares.nextcloud-https-redirect.redirectscheme.scheme=https
      - traefik.http.middlewares.nextcloud-https-redirect.redirectscheme.permanent=true
      # hsts
      - traefik.http.middlewares.hsts-header.headers.stsSeconds=31536000
      - traefik.http.middlewares.hsts-header.headers.stsIncludeSubdomains=true
      - traefik.http.middlewares.hsts-header.headers.stsPreload=true
      - traefik.http.middlewares.hsts-header.headers.forceSTSHeader=true
      
      - flame.type=application
      - flame.name=Nextcloud
      - flame.url=https://xxx
      - flame.icon=nextcloud

wivaku · 2022-05-04T14:12:53Z

docker-compose.yaml

version: '2'

services:
  db:
    image: mariadb
    container_name: nextcloud-db
    restart: unless-stopped
    command: --transaction-isolation=READ-COMMITTED --binlog-format=ROW
    volumes:
      - ./db:/var/lib/mysql
    environment:
      - MYSQL_ROOT_PASSWORD=${MYSQL_ROOT_PASSWORD}
      - MYSQL_PASSWORD=${MYSQL_PASSWORD}
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud

  app:
    build: .
    # image: nextcloud
    container_name: nextcloud
    restart: unless-stopped
    ports:
      - 1100:80
    links:
      - db
    volumes:
      - ./web:/var/www/html
      - ./data:/var/www/data
    environment:
      - MYSQL_PASSWORD=${MYSQL_PASSWORD}
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MYSQL_HOST=db
      # ---
      - NEXTCLOUD_DATA_DIR=/var/www/data
      - NEXTCLOUD_TRUSTED_DOMAINS=${NEXTCLOUD_TRUSTED_DOMAINS}
      #- TRUSTED_PROXIES=${TRUSTED_PROXIES}
      - OVERWRITEHOST=${OVERWRITEHOST}
      - OVERWRITEPROTOCOL=https
      # ---
      - SMTP_HOST=${SMTP_HOST}
      - SMTP_SECURE=${SMTP_SECURE}
      - SMTP_PORT=${SMTP_PORT}
      - SMTP_NAME=${SMTP_NAME}
      - SMTP_PASSWORD=${SMTP_PASSWORD}
      - MAIL_FROM_ADDRESS=${MAIL_FROM_ADDRESS}

Dockerfile

FROM nextcloud:apache

RUN apt-get update && apt-get install -y \
	supervisor \
	procps smbclient \
	imagemagick \
	ocrmypdf \
	tesseract-ocr \
	tesseract-ocr-eng \ 
	&& apt-get clean \
	&& rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/* /usr/share/doc/* \
	&& mkdir /var/log/supervisord /var/run/supervisord

COPY build/supervisord.conf /

ENV NEXTCLOUD_UPDATE=1

CMD ["/usr/bin/supervisord", "-c", "/supervisord.conf"]

scrummie02 · 2022-05-04T15:02:14Z

same here, upgrade breaks on 23. Can't specify a lower version in the 23 branch, my installation is completely down.

fdalvi · 2022-05-04T15:50:14Z

same here, upgrade breaks on 23. Can't specify a lower version in the 23 branch, my installation is completely down.

@scrummie02 Hope this helps: Locally, docker image nextcloud:23.0.3 is available to pull and works fine while latest does not

scrummie02 · 2022-05-04T17:51:54Z

nextcloud:23.0.3

 [core:crit] [pid 1] (13)Permission denied: AH00078: alloc_listener: failed to get a socket for (null)
AH00526: Syntax error on line 5 of /etc/apache2/ports.conf:
Listen setup failed

I'm getting this now.

scrummie02 · 2022-05-04T18:37:27Z

Can't even get into the docker container at all now, says it's not started even though it shows up. What a disaster

jokay · 2022-05-05T06:00:26Z

I can confirm this problem for the update to 24.0.0.12 as well.

Configuring Redis as session handler
Initializing nextcloud 24.0.0.12 ...
Upgrading nextcloud from 23.0.3.2 ...
Another process is initializing Nextcloud. Waiting 10 seconds...
Another process is initializing Nextcloud. Waiting 20 seconds...
Another process is initializing Nextcloud. Waiting 30 seconds...
Another process is initializing Nextcloud. Waiting 40 seconds...
Another process is initializing Nextcloud. Waiting 50 seconds...
Another process is initializing Nextcloud. Waiting 60 seconds...

skjnldsv · 2022-05-05T06:56:33Z

Can anyone try to manually remove the lock file in your html directory and try again?
/var/www/html/nextcloud-init-sync.lock

I have no idea why this file would be created and not deleted after initialization.
Maybe something got wrong in your compose start process and you killed it?

One this file is deleted, the process will start again ending the Another process is initializing Nextcloud. Waiting xxx seconds... loop

jokay · 2022-05-05T07:52:00Z

@skjnldsv thx, this did work 👍🏼

Configuring Redis as session handler
Initializing nextcloud 24.0.0.12 ...
Upgrading nextcloud from 23.0.3.2 ...
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
Turned on maintenance mode
Updating database schema
Updated database
Disabled incompatible app: twofactor_totp
Updating <lookup_server_connector> ...
Updated <lookup_server_connector> to 1.12.0
Updating <oauth2> ...
Updated <oauth2> to 1.12.0
Updating <files> ...
Updated <files> to 1.19.0
Updating <cloud_federation_api> ...
Updated <cloud_federation_api> to 1.7.0
Updating <dav> ...
Fix broken values of calendar objects

 Starting ...

Clean up old calendar subscriptions from deleted users that were not cleaned-up

    0/0 [>---------------------------]   0% Starting ...

Updated <dav> to 1.22.0
Updating <workflowengine> ...
Updated <workflowengine> to 2.6.0
Updating <federatedfilesharing> ...
Updated <federatedfilesharing> to 1.14.0
Updating <provisioning_api> ...
Updated <provisioning_api> to 1.14.0
Updating <settings> ...
Updated <settings> to 1.6.0
Updating <twofactor_backupcodes> ...
Updated <twofactor_backupcodes> to 1.13.0
Updating <viewer> ...
Updated <viewer> to 1.8.0
Update app twofactor_totp from App Store
Starting code integrity check...
Finished code integrity check
Update successful
Turned off maintenance mode
Resetting log level
The following apps have been disabled:
Initializing finished

skjnldsv · 2022-05-05T10:08:08Z

So, this is the issue with a lockfile, I don't think we can really detect if it has been created by accident or if the process that was using it, is actually still running? Anyone have ideas?
I would like to understand why it actually got created for any of you, but not deleted. Aside from killing the process, I cannot see why 🤔

scrummie02 · 2022-05-05T12:14:42Z

Can anyone try to manually remove the lock file in your html directory and try again? /var/www/html/nextcloud-init-sync.lock

I have no idea why this file would be created and not deleted after initialization. Maybe something got wrong in your compose start process and you killed it?

One this file is deleted, the process will start again ending the Another process is initializing Nextcloud. Waiting xxx seconds... loop

I'll try

scrummie02 · 2022-05-05T12:17:21Z

So, this is the issue with a lockfile, I don't think we can really detect if it has been created by accident or if the process that was using it, is actually still running? Anyone have ideas? I would like to understand why it actually got created for any of you, but not deleted. Aside from killing the process, I cannot see why 🤔

didn't work for me...it comes back.

skjnldsv · 2022-05-05T12:37:42Z

So, this is the issue with a lockfile, I don't think we can really detect if it has been created by accident or if the process that was using it, is actually still running? Anyone have ideas? I would like to understand why it actually got created for any of you, but not deleted. Aside from killing the process, I cannot see why thinking

didn't work for me...it comes back.

I comes back if you have another container starting with the same shared html

scrummie02 · 2022-05-05T12:44:09Z

Initializing nextcloud 23.0.4.1 ... Upgrading nextcloud from 23.0.3.2 ... su: System error rsync: [sender] pipe: Permission denied (13) rsync error: error in IPC code (code 14) at pipe.c(121) [sender=3.2.3] Configuring Redis as session handler Initializing nextcloud 23.0.4.1 ... Upgrading nextcloud from 23.0.3.2 ... su: System error Another process is initializing Nextcloud. Waiting 10 seconds...

scrummie02 · 2022-05-05T12:46:18Z

So, this is the issue with a lockfile, I don't think we can really detect if it has been created by accident or if the process that was using it, is actually still running? Anyone have ideas? I would like to understand why it actually got created for any of you, but not deleted. Aside from killing the process, I cannot see why thinking

didn't work for me...it comes back.

I comes back if you have another container starting with the same shared html

Thanks for replying...Here is my compose:

version: '3.3'

networks:
 nextcloud:

services:
  nextcloud:
    image: nextcloud:latest
    container_name: nextcloud-app
    #labels:
     # - "com.centurylinklabs.watchtower.enable=true"
    networks:
      - nextcloud
    ports:
      - "8080:80"
    volumes:
      - /data/Docker/nextcloud/html:/var/www/html
      - /data/Docker/nextcloud/data:/srv/nextcloud/data
    depends_on:
      - mariadb
      - redis
      - av
    environment:
      - NEXTCLOUD_TRUSTED_DOMAINS='${NEXTCLOUD_FQDN}'
      - NEXTCLOUD_DATA_DIR=/srv/nextcloud/data
      - MYSQL_DATABASE=xxx
      - MYSQL_USER=xxxx
      - MYSQL_PASSWORD=${MYSQL_PASSWORD}
      - MYSQL_HOST=nextcloud-mariadb
      - REDIS_HOST=nextcloud-redis
    restart: unless-stopped

  mariadb:
    image: mariadb:10.5
    container_name: nextcloud-mariadb
    restart: unless-stopped
    volumes:
      - /data/Docker/nextcloud/mariadb:/var/lib/mysql
    environment:
      - MYSQL_ROOT_PASSWORD=${MYSQL_ROOT_PASSWORD}
      - MYSQL_PASSWORD=${MYSQL_PASSWORD}
      - MYSQL_DATABASE=xxxx
      - MYSQL_USER=xxxx
    networks:
      - nextcloud

  redis:
    image: redis:6.2-alpine
    container_name: nextcloud-redis
    networks:
      - nextcloud
    restart: unless-stopped
      
  av:
    #debian: image: mkodockx/docker-clamav
    image: mkodockx/docker-clamav:alpine
    container_name: nextcloud-av
    restart: unless-stopped
    labels:
      - "com.centurylinklabs.watchtower.enable=true"
    networks:
      - nextcloud
    ports:
      - "3310:3310"
    volumes:
      - clamav:/var/lib/clamav

What do you mean shared HTML?

skjnldsv · 2022-05-05T12:56:16Z

What do you mean shared HTML?

/data/Docker/nextcloud/html:

stop the nextcloud app service
delete the file
and run the nextcloud app service up again.

It will be created, but it is fine. What is not fine is if the file already exists before the container starts

wivaku · 2022-05-05T13:05:51Z

Removing the lock file worked, thanks @skjnldsv!

scrummie02 · 2022-05-05T13:07:31Z

What do you mean shared HTML?

/data/Docker/nextcloud/html:

stop the nextcloud app service

delete the file

and run the nextcloud app service up again.

It will be created, but it is fine. What is not fine is if the file already exists before the container starts

it's a host directory so remove all the contents?

scrummie02 · 2022-05-05T13:13:58Z

okay stopped the container and deleted the lockfile; restarted it.

Then this:

Initializing nextcloud 23.0.4.1 ...
Upgrading nextcloud from 23.0.3.2 ...
su: System error
Another process is initializing Nextcloud. Waiting 10 seconds...

This too when lock is deleted
rsync: [sender] pipe: Permission denied (13) rsync error: error in IPC code (code 14) at pipe.c(121) [sender=3.2.3] Configuring Redis as session handler Initializing nextcloud 23.0.4.1 ... Upgrading nextcloud from 23.0.3.2 ... su: System error Another process is initializing Nextcloud. Waiting 10 seconds...

Apache logs:
Starting Apache httpd web server: apache2 failed! The apache2 configtest failed. ... (warning). Output of config test was: [Thu May 05 13:32:57.280837 2022] [core:crit] [pid 88] (13)Permission denied: AH00078: alloc_listener: failed to get a socket for (null) AH00526: Syntax error on line 5 of /etc/apache2/ports.conf: Listen setup failed Action 'configtest' failed. The Apache error log may have more information.

skjnldsv · 2022-05-05T14:24:23Z

Seems like you are facing another unrelated issue 🤔

scrummie02 · 2022-05-05T14:32:09Z

Seems like you are facing another unrelated issue 🤔

When I do delete it, it comes back and the same error.

florentls · 2022-05-06T20:44:35Z

I did get the same, upgrade from 22.2.7 to 23.0.4 and I get the issue.
Downgrade to 23.0.3 fix the issue.

Mape6 · 2022-05-08T10:36:49Z

I removed the lock file and recreated the container with image of 23.0.4 and got the following log output:

Configuring Redis as session handler
Upgrading nextcloud from 23.0.3.2 ...
Initializing nextcloud 23.0.4.1 ...
touch: setting times of '/var/www/html/nextcloud-init-sync.lock': Operation not permitted

The new lock file was created:

-rw-r--r-- 1 root root 0 May  8 10:35 nextcloud-init-sync.lock

Any hints to solve that problem?

protree · 2022-05-21T13:20:52Z

Hi,

had the same problem updating from 22.2.7.1 to 22.2.8.1. The "nextcloud-init-sync.lock" on my system was created during the previous update according to its timestamp. This previous update failed because of the "Allowed memory size of xxx bytes exhausted" and I had to run "occ upgrade" manually.

After removing the "nextcloud-init-sync.lock" file the update went smooth.

meonkeys · 2022-05-21T20:08:38Z

Related discussion: https://help.nextcloud.com/t/upgrade-locking-nextcloud-init-sync-lock-another-process-is-initializing-ephemeral-vs-persistent-lock/139412

meonkeys · 2022-05-21T20:22:33Z

Maybe we can avoid having to manually delete nextcloud-init-sync.lock if an upgrade fails halfway.

Please see #1756

Feedback appreciated!

Mape6 · 2022-05-22T07:42:17Z

I did another investigation and deleted the lock file many times.
After some time I found out that if I run the nextcloud container as priviliged, the error touch: setting times of '/var/www/html/nextcloud-init-sync.lock': Operation not permitted does not happen again and I could upgrade to 23.0.4.

Mape6 · 2022-05-22T08:16:19Z

Regarding docker-entrypoint.sh The command runs as root not as www-data. I'm not really sure but wouldn't it be better if it is executed with runs_as 'touch $lock'

apjyotirmay · 2022-05-23T17:58:36Z

Facing the same issue, tried upgrading from 23.0.5 to 24.0.1

docker-compose.yml

version: '2'

volumes:
  redis:
    driver: local

services:
  app:
    build:
      context: ./
      dockerfile: Dockerfile.nextcloud
    restart: always
    container_name: nc_app
    working_dir: /var/www/html
    depends_on:
      - redis
      - db
    networks:
      - nextcloud
    volumes:
      - <redacted>
    environment:
      - MYSQL_PASSWORD=<redacted>
      - MYSQL_DATABASE=<redacted>
      - MYSQL_USER=<redacted>
      - MYSQL_HOST=db
      - REDIS_HOST=redis

  db:
    build:
      context: ./
      dockerfile: Dockerfile.mariadb
    container_name: nc_db
    restart: always
    command: --transaction-isolation=READ-COMMITTED --binlog-format=ROW
    networks:
      - nextcloud
    volumes:
      - ./db:/var/lib/mysql
    environment:
      - MYSQL_ROOT_PASSWORD=<redacted>
      - MYSQL_PASSWORD=<redacted>
      - MYSQL_DATABASE=<redacted>
      - MYSQL_USER=<redacted>

  redis:
    image: redis:6.2-alpine
    container_name: nc_redis
    restart: always
    networks:
      - nextcloud

  nginx:
    image: nginx:1.21.5-alpine
    container_name: nc_web
    restart: unless-stopped
    working_dir: /var/www/html
    networks:
      - nextcloud
    ports:
      - 8080:80
    depends_on:
      - app
    volumes:
      - ./nginx:/etc/nginx/conf.d:ro
    volumes_from:
      - app

networks:
  nextcloud:
    external: true

Dockerfile.nextcloud

FROM nextcloud:24.0.1-fpm-alpine
RUN apk --no-cache add shadow && \
    groupmod --gid 1001 www-data && \
    usermod --uid 1000 www-data

Dockerfile.mariadb

FROM mariadb:10.7
RUN groupmod --gid 1001 mysql && \
    usermod --uid 1000 mysql

fuomag9 · 2022-05-23T19:20:33Z

I had to delete the nextcloud-init-sync.lock file in order to fix this

meonkeys · 2022-05-24T23:02:44Z

@skjnldsv would you mind taking a peek at my patch? #1757

ferdiga · 2022-05-27T10:55:00Z

docker

24.0.0 works
24.0.1 NOT !! - "Another process is initializing Nextcloud. Waiting 10 seconds..."

TechieAndroid · 2022-06-02T12:48:55Z

How do I roll back the update?
Every time I delete the new docker image and load the previous one it just auto pulls down the update and breaks my configs.

ferdiga · 2022-06-02T12:51:39Z

image=Nextcloud:24.0.0 works for me

TechieAndroid · 2022-06-02T13:13:15Z

image=Nextcloud:24.0.0 works for me

I don't know how to specify that version in docker-compose so maybe that's my issue, docker-compose is pulling from nextcloud and that's going to be the latest package on docker hub. I need a way to limit the version it's pulling in my compose file.

ferdiga · 2022-06-02T13:25:31Z

add the version number to nextcloud as mentioned above

TechieAndroid · 2022-06-02T14:18:20Z

I had to delete all my data in nextcloud/apps,data,mariadb,config,html and start fresh because everytime I tried to start the previous image it gave me a generic server error as long as I had my data in nextcloud/.

Maybe when it pulled the new version and started up it overwrote some of my data from 24.0.0 making it impossible to roll back keeping my data in tact.

skjnldsv · 2022-06-02T15:27:45Z

For anyone willing to help, please review #1760

meonkeys · 2022-06-07T12:04:16Z

For anyone willing to help, please review #1760

MrEAlderson · 2022-09-19T16:22:13Z

Got a clean installation on a Raspberry Pi 4 and the issue is still present.
I tried nextcloud:latest, nextcloud:production, nextcloud:stable, nextcloud:24.0, nextcloud:24 and nextcloud:23, and it all did not work.

My logs show the following:

Initializing nextcloud 24.0.5.1 ...
touch: setting times of '/var/www/html/nextcloud-init-sync.lock': Operation not permitted
Initializing nextcloud 24.0.5.1 ...
touch: setting times of '/var/www/html/nextcloud-init-sync.lock': Operation not permitted
Initializing nextcloud 24.0.5.1 ...
touch: setting times of '/var/www/html/nextcloud-init-sync.lock': Operation not permitted
Initializing nextcloud 24.0.5.1 ...
touch: setting times of '/var/www/html/nextcloud-init-sync.lock': Operation not permitted
Initializing nextcloud 24.0.5.1 ...

Deleting the file, trying to mess with permissions and everything didn't seem to help.

hardwareadictos · 2022-10-11T10:29:43Z

Having the same issue upgrading from 24.0.4.0 to 24.0.5/6.0 :

Nextcloud-PRO | Configuring Redis as session handler
Nextcloud-PRO | Initializing nextcloud 24.0.6.1 ...
Nextcloud-PRO | Upgrading nextcloud from 24.0.4.1 ...
Nextcloud-PRO | ls: can't open '/var/www/html/data/': Permission denied
Nextcloud-PRO | rsync: [generator] chgrp "/var/www/html/data" failed: Operation not permitted (1)
Nextcloud-PRO | rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1327) [sender=3.2.5]

That's a disaster, not upgrading even deleting the lock file :(

Permissions weren't even touched/changed.

MrEAlderson · 2022-10-14T20:19:16Z

Got a clean installation on a Raspberry Pi 4 and the issue is still present. I tried nextcloud:latest, nextcloud:production, nextcloud:stable, nextcloud:24.0, nextcloud:24 and nextcloud:23, and it all did not work.

My logs show the following:
Initializing nextcloud 24.0.5.1 ...
touch: setting times of '/var/www/html/nextcloud-init-sync.lock': Operation not permitted
Initializing nextcloud 24.0.5.1 ...
touch: setting times of '/var/www/html/nextcloud-init-sync.lock': Operation not permitted
Initializing nextcloud 24.0.5.1 ...
touch: setting times of '/var/www/html/nextcloud-init-sync.lock': Operation not permitted
Initializing nextcloud 24.0.5.1 ...
touch: setting times of '/var/www/html/nextcloud-init-sync.lock': Operation not permitted
Initializing nextcloud 24.0.5.1 ...
Deleting the file, trying to mess with permissions and everything didn't seem to help.

This was only present with the 32bit os. It worked just fine after I reinstalled it with 64bit

fuomag9 · 2022-10-14T20:25:02Z

This was only present with the 32bit os. It worked just fine after I reinstalled it with 64bit

Bug is arch-independent, managed to reproduce this on 64-bit as well

hardwareadictos · 2022-10-20T16:07:16Z

Got a clean installation on a Raspberry Pi 4 and the issue is still present. I tried nextcloud:latest, nextcloud:production, nextcloud:stable, nextcloud:24.0, nextcloud:24 and nextcloud:23, and it all did not work.
My logs show the following:
Initializing nextcloud 24.0.5.1 ...
touch: setting times of '/var/www/html/nextcloud-init-sync.lock': Operation not permitted
Initializing nextcloud 24.0.5.1 ...
touch: setting times of '/var/www/html/nextcloud-init-sync.lock': Operation not permitted
Initializing nextcloud 24.0.5.1 ...
touch: setting times of '/var/www/html/nextcloud-init-sync.lock': Operation not permitted
Initializing nextcloud 24.0.5.1 ...
touch: setting times of '/var/www/html/nextcloud-init-sync.lock': Operation not permitted
Initializing nextcloud 24.0.5.1 ...
Deleting the file, trying to mess with permissions and everything didn't seem to help.
This was only present with the 32bit os. It worked just fine after I reinstalled it with 64bit

And i'm not running it on a Raspi, i'm doing on a Debian 64 bit VM and docker

SeeYou1st · 2022-12-06T14:17:50Z

Found a solution for me. I guess a reason for this error is this:
https://docs.linuxserver.io/faq#my-host-is-incompatible-with-images-based-on-ubuntu-focal

and a solution for my docker-comose file was to add 'seccomp:unconfined'. see here:
https://stackoverflow.com/questions/46053672/set-secomp-to-unconfined-in-docker-compose

update is now running...

but I'am not a docker/nextcloud expert. don't know if that's a good solution.

imightbelosthere · 2023-03-24T11:20:50Z

And another one to the pile... Simple upgrade on Docker Container to version 25.0.4 and guess what....

`flock: 9: No locks available

Another process is initializing Nextcloud. Waiting...`

Cycling on that since... ever...
Tried all the solutions here, none of them worked... :(

imightbelosthere · 2023-03-24T12:24:06Z

Found out that apparently we can't use NFS mounted volumes for Nextcloud configuration it seems... Somehow it breaks the process.
moved the data locally to the docker host and it worked without any issue then.

aaronnad · 2023-04-12T15:24:36Z

@imightbelosthere you are absoultely 100% correct for this.
I've been prying about for hours trying to figure this out.
The main /var/www/html directory cannot be on an NFS mount. I suspect this is due to the integration of FLOCK for file locking, which is now used in place of NEXTCLOUD_INIT_LOCK instead.

Apparently flock can be used with NFS, but it needs to be implemented in a specific way.

Starting nextcloud installation

An unhandled exception has been thrown:

Exception: Could not acquire a shared lock on the config file /var/www/html/config/apache-pretty-urls.config.php in /var/www/html/lib/private/Config.php:229

Stack trace:

You also need to ensure the specific /var/www/html/config is also on a non NFS mount as well

custom_apps and data appear to support NFS mounts at present still

Y0ngg4n added 0. Needs triage bug labels May 1, 2022

szaimen transferred this issue from nextcloud/server May 1, 2022

e-caste mentioned this issue May 28, 2022

Upgrade 24.0.0->24.0.1 gets stuck at initialization #1759

Closed

skjnldsv mentioned this issue May 31, 2022

Add NEXTCLOUD_INIT_LOCK to enable shared html volume update #1760

Merged

skjnldsv closed this as completed in #1760 Jun 7, 2022

remram44 mentioned this issue Jan 27, 2023

Use flock for the upgrade lock #1903

Closed

J0WI unpinned this issue Jan 15, 2024

[Bug]: Upgrade 23.0.3 to 23.0.4 docker Server does not migrate #1742

[Bug]: Upgrade 23.0.3 to 23.0.4 docker Server does not migrate #1742

Comments

Y0ngg4n commented May 1, 2022

⚠️ This issue respects the following points: ⚠️

Bug description

Steps to reproduce

Expected behavior

Installation method

Operating system

PHP engine version

Web server

Database engine version

Is this bug present after an update or on a fresh install?

Are you using the Nextcloud Server Encryption module?

What user-backends are you using?

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

Mape6 commented May 3, 2022

Y0ngg4n commented May 3, 2022

skjnldsv commented May 4, 2022

skjnldsv commented May 4, 2022 • edited Loading

Mape6 commented May 4, 2022

wivaku commented May 4, 2022 • edited Loading

scrummie02 commented May 4, 2022

fdalvi commented May 4, 2022

scrummie02 commented May 4, 2022

scrummie02 commented May 4, 2022

jokay commented May 5, 2022 • edited Loading

skjnldsv commented May 5, 2022 • edited Loading

jokay commented May 5, 2022

skjnldsv commented May 5, 2022

scrummie02 commented May 5, 2022

scrummie02 commented May 5, 2022

skjnldsv commented May 5, 2022

scrummie02 commented May 5, 2022

scrummie02 commented May 5, 2022 • edited Loading

skjnldsv commented May 5, 2022 • edited Loading

wivaku commented May 5, 2022

scrummie02 commented May 5, 2022

scrummie02 commented May 5, 2022 • edited Loading

skjnldsv commented May 5, 2022

scrummie02 commented May 5, 2022

florentls commented May 6, 2022

Mape6 commented May 8, 2022 • edited Loading

protree commented May 21, 2022

meonkeys commented May 21, 2022

meonkeys commented May 21, 2022 • edited Loading

Mape6 commented May 22, 2022

Mape6 commented May 22, 2022

apjyotirmay commented May 23, 2022

fuomag9 commented May 23, 2022

meonkeys commented May 24, 2022

ferdiga commented May 27, 2022

TechieAndroid commented Jun 2, 2022

ferdiga commented Jun 2, 2022

TechieAndroid commented Jun 2, 2022

ferdiga commented Jun 2, 2022

TechieAndroid commented Jun 2, 2022

skjnldsv commented Jun 2, 2022

meonkeys commented Jun 7, 2022

MrEAlderson commented Sep 19, 2022

hardwareadictos commented Oct 11, 2022

MrEAlderson commented Oct 14, 2022

fuomag9 commented Oct 14, 2022

hardwareadictos commented Oct 20, 2022

SeeYou1st commented Dec 6, 2022

imightbelosthere commented Mar 24, 2023

imightbelosthere commented Mar 24, 2023

aaronnad commented Apr 12, 2023

skjnldsv commented May 4, 2022 •

edited

Loading

wivaku commented May 4, 2022 •

edited

Loading

jokay commented May 5, 2022 •

edited

Loading

skjnldsv commented May 5, 2022 •

edited

Loading

scrummie02 commented May 5, 2022 •

edited

Loading

skjnldsv commented May 5, 2022 •

edited

Loading

scrummie02 commented May 5, 2022 •

edited

Loading

Mape6 commented May 8, 2022 •

edited

Loading

meonkeys commented May 21, 2022 •

edited

Loading