Posts made by fred974

@florent said in Unable to connect to backblaze b2:

could you try to connect with the cli aws

I can try, can you please point me to some documentation? I've never done that before

Here is the latest error when saving my settings

remote.test
{
  "id": "5c043aa8-8a08-4dcd-bbfb-c2aa214c34d5"
}
{
  "name": "AccessDenied",
  "$fault": "client",
  "$metadata": {
    "httpStatusCode": 403,
    "requestId": "3d7883ea3ba87dc5",
    "extendedRequestId": "aYwU3EzAZOX84u2YJYrNlIWYMMqgz7zNU",
    "attempts": 1,
    "totalRetryDelay": 0
  },
  "Code": "AccessDenied",
  "message": "not entitled",
  "stack": "AccessDenied: not entitled
    at throwDefaultError (/opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@smithy/smithy-client/dist-cjs/default-error-handler.js:8:22)
    at /opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@smithy/smithy-client/dist-cjs/default-error-handler.js:18:39
    at de_GetObjectLockConfigurationCommandError (/opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@aws-sdk/client-s3/dist-cjs/protocols/Aws_restXml.js:4476:12)
    at /opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@smithy/middleware-serde/dist-cjs/deserializerMiddleware.js:7:24
    at /opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@aws-sdk/middleware-signing/dist-cjs/awsAuthMiddleware.js:14:20
    at /opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@smithy/middleware-retry/dist-cjs/retryMiddleware.js:27:46
    at /opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/region-redirect-endpoint-middleware.js:14:24
    at /opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/region-redirect-middleware.js:9:20
    at /opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@aws-sdk/middleware-logger/dist-cjs/loggerMiddleware.js:7:26
    at S3Handler._sync (/opt/xo/xo-builds/xen-orchestra-202311151203/@xen-orchestra/fs/src/s3.js:452:19)"
}

@olivierlambert said in Unable to connect to backblaze b2:

Have you asked Backblaze first?

After 9 days of back and forth, I am now back to my starting point...

Backblaze is saying that there is no problem at their end so check xcp-ng...

I just woke up one morning to see that the remote was no longer working.. It has been working perfectly for almost a year... I updated Xen Orchestra community in case it was a bug but I am still not able to connect...

I am running Xen Orchestra, commit af7aa with Master, commit 03de8

Could anyone please help me?

Thank you

@olivierlambert said in Unable to connect to backblaze b2:

Have you asked Backblaze first?

No but I will.

Hi,

I logged a forum entry saying that I wasn't able to restore from backup and it was pointed to me that my backup remote was offline.
I tried to recoonect my Backblaze S3 remote and I keep getting this error message:

remote.test
{
  "id": "5c043aa8-8a08-4dcd-bbfb-c2aa214c34d5"
}
{
  "name": "AccessDenied",
  "$fault": "client",
  "$metadata": {
    "httpStatusCode": 403,
    "requestId": "c6fc8c7e4f7a82ab",
    "extendedRequestId": "aYyE3pDBGOcM4fGauYlRl+GaiMpQz5TPd",
    "attempts": 1,
    "totalRetryDelay": 0
  },
  "Code": "AccessDenied",
  "message": "not entitled",
  "stack": "AccessDenied: not entitled
    at throwDefaultError (/opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@smithy/smithy-client/dist-cjs/default-error-handler.js:8:22)
    at /opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@smithy/smithy-client/dist-cjs/default-error-handler.js:18:39
    at de_GetObjectLockConfigurationCommandError (/opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@aws-sdk/client-s3/dist-cjs/protocols/Aws_restXml.js:4476:12)
    at /opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@smithy/middleware-serde/dist-cjs/deserializerMiddleware.js:7:24
    at /opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@aws-sdk/middleware-signing/dist-cjs/awsAuthMiddleware.js:14:20
    at /opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@smithy/middleware-retry/dist-cjs/retryMiddleware.js:27:46
    at /opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/region-redirect-endpoint-middleware.js:14:24
    at /opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/region-redirect-middleware.js:9:20
    at /opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@aws-sdk/middleware-logger/dist-cjs/loggerMiddleware.js:7:26
    at S3Handler._sync (/opt/xo/xo-builds/xen-orchestra-202311071630/@xen-orchestra/fs/src/s3.js:452:19)"
}

I know for sure that the credental are correct but in doubt, I then created a new API credential and even with that the detrails, I keep getting the same message: "not entitled"

I am running Xen Orchestra community Xen Orchestra, commit 9dea5
Master, commit 9dea5

Could anyone please assist me ?

Thank you

@olivierlambert said in No back available to restore:

Then make sure your backup repository is correctly connected.

Bingo. All my backblaze credential seem to have disappeared

@olivierlambert said in No back available to restore:

Click on "Refresh backup list".

I did that and nothing happened

Hi,

I have set a Delta backup a while ago and just realised that the last few weeks backup failed when trying to restore a VM. I decided to go to the last successful back as per screenshot bellow but the backup doesn't appear in the backup list

Could anyone please help me understand why my backups are not showing the the restore tab?

Thank you

Solution here:
https://xcp-ng.org/forum/topic/3430/ssh-management

Hi,

I found an old blog post saying that we can add/remove our ssh key in the user area but I cannot see this option on my screen. Could anyone please tell me where to go to delete existing keys from Xen Orchestra?

Thank you
Fred

@olivierlambert said in Resource monitoring with perf-alert:

On the screenshot I can see your host is really outdated. So I would update/reboot and see the situation after that.

I tried to update the patches but I get this error:

pool.rollingUpdate
{
  "pool": "68d0a3f2-ff33-8711-f8b3-bcd85507881b"
}
{
  "code": "-1",
  "params": [
    "Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1",
    "",
    "Traceback (most recent call last):
  File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 119, in wrapper
    return func(*args, **kwds)
  File \"/etc/xapi.d/plugins/updater.py\", line 96, in decorator
    return func(*args, **kwargs)
  File \"/etc/xapi.d/plugins/updater.py\", line 157, in update
    raise error
CalledProcessError: Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1
"
  ],
  "call": {
    "method": "host.call_plugin",
    "params": [
      "OpaqueRef:b48630d1-f865-4315-9bac-21c94ad68369",
      "updater.py",
      "update",
      {}
    ]
  },
  "message": "-1(Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1, , Traceback (most recent call last):
  File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 119, in wrapper
    return func(*args, **kwds)
  File \"/etc/xapi.d/plugins/updater.py\", line 96, in decorator
    return func(*args, **kwargs)
  File \"/etc/xapi.d/plugins/updater.py\", line 157, in update
    raise error
CalledProcessError: Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1
)",
  "name": "XapiError",
  "stack": "XapiError: -1(Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1, , Traceback (most recent call last):
  File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 119, in wrapper
    return func(*args, **kwds)
  File \"/etc/xapi.d/plugins/updater.py\", line 96, in decorator
    return func(*args, **kwargs)
  File \"/etc/xapi.d/plugins/updater.py\", line 157, in update
    raise error
CalledProcessError: Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1
)
    at Function.wrap (/opt/xo/xo-builds/xen-orchestra-202306071622/packages/xen-api/src/_XapiError.js:16:12)
    at /opt/xo/xo-builds/xen-orchestra-202306071622/packages/xen-api/src/transports/json-rpc.js:35:21
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:447:9)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}

Could anyone please help me resolve this issue?

Thank you

@olivierlambert said in Resource monitoring with perf-alert:

On the screenshot I can see your host is really outdated. So I would update/reboot and see the situation after that

Do you mean the patch or xcp-ng is outdated?

@olivierlambert said in Resource monitoring with perf-alert:

check your Dom0.

I am right to say Dom0 is the hypervisor itself?
I just had another cpu spike on the host and when I looked at the host resources via htop, I cannot see any cpu spike at all.

Am I looking at the wrong place?

Hi,

I just enable perf-alert on Xen Orchestra community edition and I have been flooded with CPU alert. I left all the plugin settings as default for now.

Here is the email

ALERT: host CPU usage > 40%
uk-dc1-prod-hv2: 50.2%
Description
Raises an alarm when the average usage of any CPU is higher/lower than the threshold

Sent from Xen Orchestra perf-alert plugin

When I look at the host I can see this:

The Host only has 1 VM running on it and I cannot see any spike in CPU

I have 2 questions:

1. why is the default warning threshold set to 40%? This seem very low to be but before I start poking, I'll like to know if the default is there for a reason

2. Why do I keep getting CPU warning when the VM isn't doing anything? What do I need to investigated here?

The Host is the primary in a cluster of 4x hosts.
XCP-ng 8.2.1
xo-server 5.116.3
xo-web 5.119.1

Thank you all in advance

@florent Thank you for the update

@olivierlambert I am using Xen Orchestra community.
Debian 11
Xen Orchestra, commit d7ce6
xo-server 5.114.2
xo-web 5.117.1

Hi,

I have a backup that I started on 23rd may 2023 that is still showing in progress with no error in Xen Orchestra. On the S3 storage I can see that on 41.60GB of the 250GB I am expecting has been received.

Here is the details

How do I know if the process is still in progress or if it crashed?
Thank you

@planedrop The speed on the Storj was when a backup was running. I am just reading the values I see in XO

Hi,

I tough I would share what speed I see for the various S3 remote that I use for backup...

Backblaze B2 :
Region: s3.us-west
Write: 2.99 MiB/s
Read: 5.53 MiB/s

Wasabi Hot Cloud Storage
Region: s3.uk-1
Write: 1.02 MiB/s
Read: 2.34 MiB/s

Stroj
Region: EU
Write: 6.39 MiB/s
Read: 6.21 MiB/s

Nothing scientific here, just sharing what I get if anyone want to know who's faster

@Danp yes I can. It prompt for login details but I cannot login as it seem to be via ssh key only.