nextcloud / nextcloud/backup

The given affected user is invalid

Open
#197 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
272
Forks
37
PR merge metrics
No merged PRs in 30d

Description

Hi, I have been trying to get nextcloud backup to work.

Creating a restore point from the UI never works.
As it gets stuck at “the creation of a restoring point as been requested and will be initiated soon.” #160
So I did it from CLI.
And it stops with this error. Which i can't find any resource about its cause.

> maintenance mode: off

In Event.php line 148:
                                      
  The given affected user is invalid  
                                      

backup:point:create [--output [OUTPUT]] [--generate-log] [--differential] [--] [<comment>]

This issue happens with or without an external storage setup.

Related logs
[PHP] Error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 8388616 bytes) at /var/www/html/apps/backup/lib/Service/ChunkService.php#477

at 2022-02-27T04:25:15+00:00


[PHP] Error: fopen(/mnt/data-disk/appdata_ddbed8621e78c/text/documents/625363): Failed to open stream: No such file or directory at /var/www/html/apps/backup/lib/Service/ChunkService.php#483

at 2022-02-27T03:22:47+00:00

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 with the backup:point:create CLI command and inspect apps/backup/lib/Service/ChunkService.php at lines 477 and 483, using the supplied memory-exhaustion and missing-file logs as reproduction clues. Compare the CLI failure with the UI restore-point behavior and determine which condition produces the invalid affected-user error; done means the cause is identified and the affected flow has a verified fix or clear diagnostic.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.