nextcloud / nextcloud/nextcloudpi

ncp-update 1.51.0 to 1.52.0 not working

Open
#1,779 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

has-updates
Dominant language
Shell
Stars
2.9k
Forks
318
PR merge metrics
No merged PRs in 30d

Description

Hi there, i am trying to update my NCP on my Rpi4 by using sudo ncp-config.

 Update to v1.52.0?                                                 │
                                          │                                                                    │
                                          │ *   [tag: v1.52.0] Merge pull request #1771 from nextcloud/devel   │
                                          │ * | | | | [tag: v1.51.3] Merge branch 'devel'                      │
                                          │ * | [tag: v1.51.2] publish-image.yml: Fix condition for publishing │
                                          │ images                                                             │
                                          │ | [v1.51.2-rc3] publish-image.yml: Retry updating release          │
                                          │ description with random delays to avoid race conditions       

by saying yes it starts, and afterwards it stays for over 20 minutes like this:

Downloading updates
Performing updates
Fixing NCP logo if missing...

there is nothing to find in the ncp.log
I've tried it by changing the ncp logo via occ:

sudo -u www-data php /var/www/nextcloud/occ theming:config -- logo /var/www/nextcloud/core/img/logo/logo.svg
Updated logoMime to image/svg+xml

this doesn't change anything.
i'm seeing in htop a chown -R www-data:www-data /media/XYZ/ncdata/data/appdata_XYZXYZXYZ staying there for the whole time, maybe thats a hint for the problem?

Any solution for this, i haven't found this problem here or in the helpdesk.

Cheers Fisher

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the update through sudo ncp-config and observe the process at “Fixing NCP logo if missing...”. Check ncp.log and the reported chown process on /media/XYZ/ncdata/data/appdata_XYZXYZXYZ; done means identifying why the update stalls and documenting or validating a resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
raspberry-pi, shell
Domain
cli, operating-systems, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.