Settings-Log page in XO is empty

[manilx]

Installation went fine and all is running. The only thing I encounter is that I cannot check logs. The respective page in Settings-Logs is empty.

Running another instance of XO using another script (https://github.com/ronivay/XenOrchestraInstallerUpdater) shows the logs just fine.

Pls advise

[Jarli01]

Please fill out the questions that is provided in the issue template so that we can help you.

[manilx]

Hi. When I follow the issue template link on https://github.com/Jarli01/xenorchestra_installer/blob/master/TROUBLESHOOTING.md#submitting-a-support-request I just get the page with "Add a title" and "Add a description", which I did. So please tell me what you want to know in addition. Installed the script on Debian12....

[Jarli01]

Describe the bug A clear and concise description of what the trouble is.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop/Server details (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

Confirm XOCE services are running Please run systemctl status xo-server.service and paste the resulting output below.

Provide the output of journalctl logs Please run journalctl -u xo-server -f -n 50 and paste the resulting output below.

Provide answers to these questions:

• Is this a fresh install or an upgrade?
• Version of XOCE server and web interface you're running
• What OS is XOCE running on?
• A link to the ISO you've used as as the server (so we can verify/troubleshoot)
• What method did you use to install XOCE (xo_install.sh, manual installation, etc)
• What specific XOCE page you're on, and what specific element you're interacting with to trigger the error
• If a stacktrace is provided in the error, include that too.
• Any errors that appear in your browser's error console.
• Include what you've done so far in the installation, and if you got any error messages along the way.
• Indicate whether or not you've manually edited any data directly.

[manilx]

Describe the bug A clear and concise description of what the trouble is.

Installation went fine and all is running. The only thing I encounter is that I cannot check logs. The respective page in Settings-Logs is empty.

Running another instance of XO using another script (https://github.com/ronivay/XenOrchestraInstallerUpdater) shows the logs just fine.

To Reproduce Steps to reproduce the behavior:

Any error, which is encountered in XO and which generates the red error popup should be able to be checked under Settings-Logs. When opening that page no logs are shown at all.

Desktop/Server details (please complete the following information):

OS: Debian 12 Firefox

Confirm XOCE services are running Please run systemctl status xo-server.service and paste the resulting output below.

● xo-server.service - XO Server Loaded: loaded (/lib/systemd/system/xo-server.service; enabled; preset: enabled) Active: active (running) since Wed 2024-03-27 13:42:43 WET; 40min ago Main PID: 506 (node) Tasks: 11 (limit: 2340) Memory: 272.9M CPU: 9.065s CGroup: /system.slice/xo-server.service └─506 /usr/local/bin/node ./dist/cli.mjs

Mar 27 13:56:39 XenOrchestra xo-server[506]: at ServerResponse.emit (node:events:517:28) Mar 27 13:56:39 XenOrchestra xo-server[506]: at ServerResponse.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17) Mar 27 13:56:39 XenOrchestra xo-server[506]: at emitCloseNT (node:_http_server:1020:10) Mar 27 13:56:39 XenOrchestra xo-server[506]: at processTicksAndRejections (node:internal/process/task_queues:81:21) Mar 27 13:56:39 XenOrchestra xo-server[506]: at runNextTicks (node:internal/process/task_queues:64:3) Mar 27 13:56:39 XenOrchestra xo-server[506]: at processImmediate (node:internal/timers:447:9) Mar 27 13:56:39 XenOrchestra xo-server[506]: at process.callbackTrampoline (node:internal/async_hooks:128:17) { Mar 27 13:56:39 XenOrchestra xo-server[506]: code: 'UND_ERR_ABORTED' Mar 27 13:56:39 XenOrchestra xo-server[506]: } Mar 27 13:56:39 XenOrchestra xo-server[506]: }

Provide the output of journalctl logs Please run journalctl -u xo-server -f -n 50 and paste the resulting output below.

Mar 27 13:56:39 XenOrchestra xo-server[506]: _objectsFetched: [Promise [Object]], Mar 27 13:56:39 XenOrchestra xo-server[506]: _eventWatchers: [Object: null prototype] {}, Mar 27 13:56:39 XenOrchestra xo-server[506]: _taskWatchers: [Object: null prototype], Mar 27 13:56:39 XenOrchestra xo-server[506]: _watchedTypes: undefined, Mar 27 13:56:39 XenOrchestra xo-server[506]: _callRetryWhenTooManyPendingTasks: [Object], Mar 27 13:56:39 XenOrchestra xo-server[506]: _maxUncoalescedVdis: 1, Mar 27 13:56:39 XenOrchestra xo-server[506]: _preferNbd: false, Mar 27 13:56:39 XenOrchestra xo-server[506]: _nbdOptions: undefined, Mar 27 13:56:39 XenOrchestra xo-server[506]: _syncHookSecret: undefined, Mar 27 13:56:39 XenOrchestra xo-server[506]: _syncHookTimeout: undefined, Mar 27 13:56:39 XenOrchestra xo-server[506]: _vdiDestroyRetryWhenInUse: [Object], Mar 27 13:56:39 XenOrchestra xo-server[506]: _genericWatchers: Set(0) {}, Mar 27 13:56:39 XenOrchestra xo-server[506]: _objectWatchers: [Object: null prototype] {}, Mar 27 13:56:39 XenOrchestra xo-server[506]: _guessVhdSizeOnImport: true, Mar 27 13:56:39 XenOrchestra xo-server[506]: _restartHostTimeout: 1200000, Mar 27 13:56:39 XenOrchestra xo-server[506]: _vmEvacuationConcurrency: 3, Mar 27 13:56:39 XenOrchestra xo-server[506]: VDI_exportContent: [Function (anonymous)], Mar 27 13:56:39 XenOrchestra xo-server[506]: VM_export: [Function (anonymous)], Mar 27 13:56:39 XenOrchestra xo-server[506]: _migrateVmWithStorageMotion: [Function (anonymous)], Mar 27 13:56:39 XenOrchestra xo-server[506]: VM_snapshot: [Function (anonymous)], Mar 27 13:56:39 XenOrchestra xo-server[506]: getObject: [Function (anonymous)], Mar 27 13:56:39 XenOrchestra xo-server[506]: _resolveDisconnected: [Function (anonymous)], Mar 27 13:56:39 XenOrchestra xo-server[506]: _types: [Array], Mar 27 13:56:39 XenOrchestra xo-server[506]: _lcToTypes: [Object: null prototype], Mar 27 13:56:39 XenOrchestra xo-server[506]: xo: [Object], Mar 27 13:56:39 XenOrchestra xo-server[506]: _nTasks: 1, Mar 27 13:56:39 XenOrchestra xo-server[506]: [Symbol(kCapture)]: false Mar 27 13:56:39 XenOrchestra xo-server[506]: }, Mar 27 13:56:39 XenOrchestra xo-server[506]: vmRef: 'OpaqueRef:9a4a034c-3c90-aeb5-c61a-b45f6f10039a', Mar 27 13:56:39 XenOrchestra xo-server[506]: compress: false, Mar 27 13:56:39 XenOrchestra xo-server[506]: format: 'xva' Mar 27 13:56:39 XenOrchestra xo-server[506]: }, Mar 27 13:56:39 XenOrchestra xo-server[506]: error: TypeError: Cannot set properties of undefined (setting 'content-disposition') Mar 27 13:56:39 XenOrchestra xo-server[506]: at Xo.handleExport (file:///opt/xen-orchestra/packages/xo-server/src/api/vm.mjs:1219:40), Mar 27 13:56:39 XenOrchestra xo-server[506]: fn: 'handleExport' Mar 27 13:56:39 XenOrchestra xo-server[506]: } Mar 27 13:56:39 XenOrchestra xo-server[506]: 2024-03-27T13:56:39.201Z xo:xo-server ERROR unhandled error event { Mar 27 13:56:39 XenOrchestra xo-server[506]: error: RequestAbortedError [AbortError]: Request aborted Mar 27 13:56:39 XenOrchestra xo-server[506]: at BodyReadable.destroy (/opt/xen-orchestra/node_modules/undici/lib/api/readable.js:48:13) Mar 27 13:56:39 XenOrchestra xo-server[506]: at ServerResponse. (file:///opt/xen-orchestra/packages/xo-server/src/api/vm.mjs:1217:32) Mar 27 13:56:39 XenOrchestra xo-server[506]: at ServerResponse.emit (node:events:517:28) Mar 27 13:56:39 XenOrchestra xo-server[506]: at ServerResponse.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17) Mar 27 13:56:39 XenOrchestra xo-server[506]: at emitCloseNT (node:_http_server:1020:10) Mar 27 13:56:39 XenOrchestra xo-server[506]: at processTicksAndRejections (node:internal/process/task_queues:81:21) Mar 27 13:56:39 XenOrchestra xo-server[506]: at runNextTicks (node:internal/process/task_queues:64:3) Mar 27 13:56:39 XenOrchestra xo-server[506]: at processImmediate (node:internal/timers:447:9) Mar 27 13:56:39 XenOrchestra xo-server[506]: at process.callbackTrampoline (node:internal/async_hooks:128:17) { Mar 27 13:56:39 XenOrchestra xo-server[506]: code: 'UND_ERR_ABORTED' Mar 27 13:56:39 XenOrchestra xo-server[506]: } Mar 27 13:56:39 XenOrchestra xo-server[506]: }

Provide answers to these questions:

* Is this a fresh install or an upgrade?

Fresh install

* Version of XOCE server and web interface you're running

Xen Orchestra, commit [88dd9] Master, commit [88dd9]

* What OS is XOCE running on?

Debian 12

* What method did you use to install XOCE (xo_install.sh, manual installation, etc)

install script: https://github.com/Jarli01/xenorchestra_installer/blob/master/xo_install.sh

* Include what you've done so far in the installation, and if you got any error messages along the way.

* Indicate whether or not you've manually edited any data directly.

Nothing done, just the script.

[manilx]

[manilx]

Should be:

[Jarli01]

What build version is installed from ronivoy?

[manilx]

Latest from today.

-- Manfred Ell

On 27 Mar 2024 at 14:26 +0000, Dustin B @.***>, wrote:

What build version is installed from ronivoy? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

[Jarli01]

So the XO from ronivoy's script is also running 88dd9?

[Jarli01]

The reason I'm asking this, is that this repo, installs the latest version provided from source, and makes no changes to the source.

I can attempt the install myself to validate the issue you're experiencing, the solution would be provided from the source material, once an issue can be pinpointed.

[manilx]

Correct. Both are running the same builds.

[manilx]

[Jarli01]

Debian 12.5.1 correct?

[manilx]

Debian GNU/Linux 12 (bookworm) x86_64

[manilx]

[Jarli01]

I'm testing on my side and will report back.

The most recent release that I see is "88dd987" so I'm not certain what is going on, let me validate and report back shortly.

[manilx]

Thx!

[manilx]

I just updated the ronivay XO and the other using your update script. Both now on

Issue remains

[manilx]

There were a few warning messages on the update, don't know if normal:

[Jarli01]

Warnings can be safely ignored, Errors would need attention.

[manilx]

As a test I just installed a fresh VM using Ubuntu Jammy Jellyfish 22.04. Enabled root. Run your script. Imported settings. All OK. But issue persists. So you can take the OS out of the equation.

[Jarli01]

So on Debian only you had this issue? Interesting, my system is still building now. So I can't validate one way or the other yet.

[manilx]

Yes, only issue I have encountered. The error I'm causing and which should show on the log (shows in ronivay) is trying to export a VM. Doesn't work in selfbuild XO. Works in XOA. Wanted to report that in the forum but wanted to test your build first. The error happens on both (so it is caused by build from sources) but here I encountered the issue I reported

[Jarli01]

Yeah there have been some issues with exporting recently from the source docs as well and its on the XO forums. I'm going to be stepping away shortly for a break, but should be able to validate if I encounter the same issue using debian bookworm 12.5.0 on my system here when I get back.

[Jarli01]

Interesting I was able to reproduce as well, though my version is now the latest. Still checking on it

[manilx]

Great and thx for checking  Something is broken… guess another bug they introduced. Seems to be frequent lately.

-- Manfred Ell

On 28 Mar 2024 at 00:23 +0000, Dustin B @.***>, wrote:

Interesting I was able to reproduce as well, though my version is now the latest. Still checking on it — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

[manilx]

Just found another issue with this build: trying to export config doesn't do anything.

[Danp2]

FWIW, my VM doesn't have any issues with Settings > Logs or exporting a config file.

[manilx]

FWIW, my VM doesn't have any issues with Settings > Logs or exporting a config file.

Any chance of sharing an export of it??

[Jarli01]

FWIW, my VM doesn't have any issues with Settings > Logs or exporting a config file.

On a new build you had no issues? I encountered this twice myself (Debian and Ubuntu), I've not had a chance to follow up to source where the issue may be coming from.

[manilx]

Here I tried both fresh Debian12 and Ubuntu2204 and script. Both had the issues described.

[Danp2]

On a new build you had no issues?

No, it was my existing deployment updated to the latest sources.

Any chance of sharing an export of it??

I don't see how that would be beneficial here.

[Jarli01]

Got it, on new deployments it appears that the Settings > Log page is simply not present as @manilx showed in his screenshot. I tested on both Debian and Ubuntu.

Updating isn't impacted.

[RuKeBo]

I just happened to install this new on an Ubuntu 22.4 VM and I get a Settings > Log page. I was having trouble updating my older version so I just made a fresh install.

[Jarli01]

Can you show us your about page?

[manilx]

Just tried it again now

on Debian12 (I have a ready made template from a fresh install a couple of days ago I just have to clone and run the script): Issues remain. No config export and no logs.

Same test on Ubuntu 22.04 (fresh install from yesterday) template: same issues

[RuKeBo]

Out of date already.

[Danp2]

I just deployed a new VM and installed XO. The tab appears empty until it has something to display --

[Jarli01]

I just deployed a new VM and installed XO. The tab appears empty until it has something to display --

That's definitely an improvement, before the Logs tab wouldn't even load, building a new one myself as a test.

[manilx]

I just deployed a new VM and installed XO. The tab appears empty until it has something to display -- !

Can you give me a quick command to create a log? Deploying new install at the moment.

[Danp2]

That's definitely an improvement, before the Logs tab wouldn't even load, building a new one myself as a test.

Are you sure it wasn't working correctly before? I think it was, but there wasn't anything to display. 🤔

Can you give me a quick command to create a log? Deploying new install at the moment.

That tab pretty much only logs errors, so do something stupid like try to add an NFS SR by pointing it to your XCP server. 😆

[Jarli01]

That's definitely an improvement, before the Logs tab wouldn't even load, building a new one myself as a test.

Are you sure it wasn't working correctly before? I think it was, but there wasn't anything to display. 🤔

Can you give me a quick command to create a log? Deploying new install at the moment.

That tab pretty much only logs errors, so do something stupid like try to add an NFS SR by pointing it to your XCP server. 😆

That is a fair point, I think the other issue that was brought up was (untested by myself) that he couldn't export the configuration.

The interesting point that I noticed was that the Tab headers within Logs wasn't presented, which definitely feels odd.

[manilx]

Just created new Debian12 install. Did the dumb thing you suggested and I got the log entry :) BUT the previous install from when I reported this issue definitely didn't log the errors because I had various (backups and stuff).

But the issue with not being able to export config remains.

[Danp2]

@Jarli01 I don't know if that behavior is new or not since it's been forever since I've had an empty error log. 😆

@manilx Config exports are working fine for me, so maybe PEBCAK? 😉 What happens when you attempt to export a config?

[manilx]

@Jarli01 I don't know if that behavior is new or not since it's been forever since I've had an empty error log. 😆

@manilx Config exports are working fine for me, so maybe PEBCAK? 😉 What happens when you attempt to export a config?

Nothing happens at all after I acknowledge the export dialogue. No error no export.

[manilx]

I just run the update script and got this:

[manilx]

BUT the config exported!

[manilx]

What should I input for "root of the repo to migrate"

[Jarli01]

/opt/xen-orchestra is where we install into, I've not seen that error before though

[manilx]

Got error:

Easier to redeploy I guess