Backup Error: "302 Found"

DustinB

I too am experiencing this same issue, XO from Source, latest commit aefcc, XCP 8.2.1

Move the VM, change the target etc.

backupNg.runJob
{
  "id": "ed0deefb-2942-4bc0-8061-ac4ef5f62f46",
  "schedule": "8c3312f2-025a-40b6-8eb4-ec565b5c4b19"
}
{
  "originalUrl": "https://localhost/jsonrpc",
  "url": "https://localhost/signin",
  "call": {
    "method": "session.login_with_password",
    "params": "* obfuscated *"
  }
}

Danp

Huh? Please provide detailed explanation because right now I have no idea what you are trying to say here.

DustinB

@Danp said in Backup Error: "302 Found":

Huh? Please provide detailed explanation because right now I have no idea what you are trying to say here.

Sorry, I also made a GH ticket, found here https://github.com/vatesfr/xen-orchestra/issues/7403

Summary is that when taking a backup of any VM, I'm getting a "302 Found" error message.

@julien-f mentioned localhost in the URL makes me think that the host address was not correctly set in the URL, don't know why though.

Jarli01 created this issue in vatesfr/xen-orchestra

closed Backup job failed #7403

Danp

Is there something different / unusual about this backup job or the VM being backed up? Does this error occur on all delta backups? Are you able to reproduce at will?

FWIW, my delta backups are still working on the latest sources.

DustinB

@Danp said in Backup Error: "302 Found":

Is there something different / unusual about this backup job or the VM being backed up? Does this error occur on all delta backups? Are you able to reproduce at will?

FWIW, my delta backups are still working on the latest sources.

No difference with any of the jobs, new fulls or delta's also have the same issue.

I can reproduce it at any time, by clicking the "Run now' or "Force retry failed"

Danp

@DustinB You could try the same backup job using XOA. If that works correctly, then that would eliminate some of the environmental causes.

DustinB

@Danp said in Backup Error: "302 Found":

@DustinB You could try the same backup job using XOA. If that works correctly, then that would eliminate some of the environmental causes.

Got it sorted out, and addressed a speed issue I was experiencing.

The advanced options of the pool, I had set ETH1 as the backup network, which for some reason keeps falling back to 10FDx and is generally just bad.

Undid that change as well as moved my XO over to a different vNIC which appears to have addressed the issues.