@olivierlambert said in Get VM from <ID>.vhd from Storage-Record:
But why? What's the purpose? What do you want to achieve in the end?
I wanna know which Disk from which VM needs more space because we've an Disk-Alert on the SR in our Monitoring and I wanna know the exact VM.
But when I hover ofer the Disks from the VMs in XOA I can't find the respective VM.
@olivierlambert said in Get VM from <ID>.vhd from Storage-Record:
Hi,
It's unclear. What do you want to achieve exactly? Functionally speaking.
Hi!
I want to get the respective VM to an VHD (Disk) File. Hops that's clearer...
Hi there!
Our customer creates the Disc-Images of its VMs on the Local Storage Record under /run/sr-mount/<ID>/<ID_of_Disk_Image>.vhd. ...
This path is also mounted in XOA... Now I wanna get the specified VM for the matchig disk-Image. How can I get this with xe-commands?
I can't find the concerned VM to a spcial Disk-Image.
Thanks for your help.
@olivierlambert said in Alert: Control Domain Memory Usage:
In Xen Orchestra, restarting the toolstack is clicking on a button. This won't affect running VMs (except if you are in the middle of an hypervisor operation, like migrating/exporting). Restarting the toolstack won't fundamentally solve your issue.
Adding more memory into the dom0 is a good idea in general (depending on the total memory you have). 8GiB is a good start. This will require a host reboot in any case, to be taken into account.
Hi Olivier, thanks for your fast reply. We've identified on our systems that the Openvswitch needs a lot of memory and therefore we wanna restart it.
Is it possible to do this without restarting the hole host and without an downtime?
@dave said in Alert: Control Domain Memory Usage:
@olivierlambert said in Alert: Control Domain Memory Usage:
Netdata
Hello Oliver,
thanks for your quick Response.Yes, htop is much prettier, but it doen`t see more the top, at least in this case:
I think, Netdata will also just see those things?
Hi there! Hope it's okay that I answer regarding this topic....
We've also this Error and in 'Notifications' in the XCP-NG Center I can see the following:
Is there any possibility to resolve this error without restarting the hole host? How can I restart the toolstack? Can I do it without an interrupt of the business?
We've also raised up the Memory for the Controller Domain from 4 --> 8GB.....
Hi @olivierlambert !
Thanks for your help but we've noticed, that on all of ours CentOS-VMs we haven't start 'xe-linux-distribution.service'.
After doing an 'systemctl enable xe-linux-distribution.service' followed by an 'systemctl start xe-linux-distribution.service' it works fine in XOA.
Thanks a lot for your help.
Okay sorry, I've re-checked it and it seems that the Xen-Guest-Tools are installed on our CentOS-based-VMs:
[18:00:21][root@admin:~]$yum list installed | grep xen*
kexec-tools.x86_64 2.0.15-33.el7 @base
libXfixes.x86_64 5.0.3-1.el7 @base
xe-guest-utilities-latest.x86_64 7.17.0-2.el7 @epel
xe-guest-utilities-xenstore.x86_64 7.0.0-24 installed
[18:01:22][root@admin:~]$
It seems that we haven't installed the Xen-Tools in our CentOS-based VMs. It's like as you have discribed it here, right? --> https://xen-orchestra.com/blog/install-xenserver-tools-in-your-vm/
Is there a possibility to reinstall the Xen-Tools without an reboot of the VMs?
Hi there!
We've the problem, that the memory usage wouldn't be displayed on CentOS-VMs in XOA but on Debian and SLES11 based VM's it'll be displayed:
CentOS-VM:
SLES11-VM:
Under the 'Advanced Options' we can see that the 'Xen tools' aren't installed on the CentOS-VMs:
CentOS-VM:
SLES11-VM:
As it's discribed here (Xen-Orchestra Blog) it seems that only Debians Default-Kernel PVHVM Support.
Is it possible to enabled this also on CentOS-VMs to see the Memory-Usage in XOA?
Okay, we've done the Upgrade on every of our XCP-NG Nodes via 'yum update'. So we haven't done it via the ISO and I understood yours statement in the other topic, that the statistics should be on the XCP-NG Nodes anymore.
But is there also an possibility to get the statistics in XOA and to store it for the time 'after the reboot'?
Background is that our customer would like to have this in the XOA at the next update of the nodes, because he only has access to the XOA and not to XCP-NG Center.
Sorry, I thought it's better to ask this in an new Topic. Could you merge it to the old one or should I ask my question again in the old one and close this topic?
Hi there!
I've this Problem wanna find an solution to save the statistics from XOA over the time for rebooting the XCP-NG Nodes.
Is it possible to store the statistics 'for the time after rebooting the Nodes'?
@olivierlambert said in No Statistics in XOA after Rebooting our XCP-NG Nodes:
It's not RRD files directly that way. It's stored in the database if I remember correctly.
So this is something related to your XCP-ng nodes, not related to XO.
Hm, okay. But what do I have to configure in my XCP-NG nodes to get it working? Or is it better to open an Topic in Management or Installation for this task?
@olivierlambert said in No Statistics in XOA after Rebooting our XCP-NG Nodes:
If you did an upgrade via ISO, it probably wiped the RRD database on the host, so it's "normal" to lose the previous data.
Data isn't stored in XO but on the host.
Okay, I've looked on the host but I can't find any *.rrd-Files on the XOA Host nore on any XCP-NG Node.
We've installed the XOA-Version from vatesfr /
xen-orchestra and updated our XCP-NG Nodes lastly. Now we've the problem, that we can't see any Statistics from the time before the update of the Nodes.
When I do an 'journalctl -u xo-server -f -n 2000' on our XOA-Installation I can see the following:
[16:26:40][root@xoa-installation:~]$ journalctl -u xo-server -f -n 2000
-- Logs begin at Tue 2020-04-14 01:20:46 CEST. --
Apr 14 02:12:33 xoa-installation xo-server[657]: _watchEvents { Error: socket hang up
Apr 14 02:12:33 xoa-installation xo-server[657]: at createHangUpError (_http_client.js:332:15)
Apr 14 02:12:33 xoa-installation xo-server[657]: at TLSSocket.socketOnEnd (_http_client.js:435:23)
Apr 14 02:12:33 xoa-installation xo-server[657]: at TLSSocket.apply (events.js:203:15)
Apr 14 02:12:33 xoa-installation xo-server[657]: at TLSSocket.patchedEmit [as emit] (/home/xoa-build/xen-orchestra/@xen-orchestra/log/src/configure.js:95:17)
Apr 14 02:12:33 xoa-installation xo-server[657]: at endReadableNT (_stream_readable.js:1145:12)
Apr 14 02:12:33 xoa-installation xo-server[657]: at process._tickCallback (internal/process/next_tick.js:63:19)
Apr 14 02:12:33 xoa-installation xo-server[657]: code: 'ECONNRESET',
Apr 14 02:12:33 xoa-installation xo-server[657]: url: 'https://192.168.0.25/jsonrpc',
Apr 14 02:12:33 xoa-installation xo-server[657]: call:
Apr 14 02:12:33 xoa-installation xo-server[657]: { method: 'event.from',
Apr 14 02:12:33 xoa-installation xo-server[657]: params:
Apr 14 02:12:33 xoa-installation xo-server[657]: [ [Array], '00000000000302450462,00000000000302449388', 60.1 ] } }
Apr 14 02:13:51 xoa-installation xo-server[657]: _watchEvents { Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:13:51 xoa-installation xo-server[657]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14)
Apr 14 02:13:51 xoa-installation xo-server[657]: errno: 'EHOSTUNREACH',
Apr 14 02:13:51 xoa-installation xo-server[657]: code: 'EHOSTUNREACH',
Apr 14 02:13:51 xoa-installation xo-server[657]: syscall: 'connect',
Apr 14 02:13:51 xoa-installation xo-server[657]: address: '192.168.0.25',
Apr 14 02:13:51 xoa-installation xo-server[657]: port: 443,
Apr 14 02:13:51 xoa-installation xo-server[657]: url: 'https://192.168.0.25/jsonrpc',
Apr 14 02:13:51 xoa-installation xo-server[657]: call:
Apr 14 02:13:51 xoa-installation xo-server[657]: { method: 'event.from',
Apr 14 02:13:51 xoa-installation xo-server[657]: params:
Apr 14 02:13:51 xoa-installation xo-server[657]: [ [Array], '00000000000302450462,00000000000302449388', 60.1 ] } }
Apr 14 02:13:51 xoa-installation xo-server[657]: 2020-04-14T00:13:51.109Z xo:api WARN root | pool.listMissingPatches(...) [35s] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:13:51 xoa-installation xo-server[657]: 2020-04-14T00:13:51.110Z xo:api WARN root | pool.listMissingPatches(...) [33s] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:13:54 xoa-installation xo-server[657]: 2020-04-14T00:13:54.949Z xo:api WARN root | pool.listMissingPatches(...) [18s] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:13:54 xoa-installation xo-server[657]: 2020-04-14T00:13:54.949Z xo:api WARN root | pool.listMissingPatches(...) [32s] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:13:56 xoa-installation xo-server[657]: 2020-04-14T00:13:56.573Z xo:api WARN root | pool.listMissingPatches(...) [3ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:13:56 xoa-installation xo-server[657]: 2020-04-14T00:13:56.576Z xo:api WARN root | pool.listMissingPatches(...) [3ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:13:56 xoa-installation xo-server[657]: 2020-04-14T00:13:56.578Z xo:api WARN root | pool.listMissingPatches(...) [2ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:13:56 xoa-installation xo-server[657]: 2020-04-14T00:13:56.581Z xo:api WARN root | pool.listMissingPatches(...) [2ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:00 xoa-installation xo-server[657]: 2020-04-14T00:14:00.307Z xo:api WARN root | pool.listMissingPatches(...) [2ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:00 xoa-installation xo-server[657]: 2020-04-14T00:14:00.310Z xo:api WARN root | pool.listMissingPatches(...) [2ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:01 xoa-installation xo-server[657]: 2020-04-14T00:14:01.582Z xo:api WARN root | pool.listMissingPatches(...) [3ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:01 xoa-installation xo-server[657]: 2020-04-14T00:14:01.586Z xo:api WARN root | pool.listMissingPatches(...) [2ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:01 xoa-installation xo-server[657]: 2020-04-14T00:14:01.599Z xo:api WARN root | pool.listMissingPatches(...) [12ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:01 xoa-installation xo-server[657]: 2020-04-14T00:14:01.601Z xo:api WARN root | pool.listMissingPatches(...) [2ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:01 xoa-installation xo-server[657]: 2020-04-14T00:14:01.738Z xo:main INFO - WebSocket connection (::ffff:127.0.0.1)
Apr 14 02:14:01 xoa-installation xo-server[657]: 2020-04-14T00:14:01.762Z xo:main INFO + WebSocket connection (::ffff:127.0.0.1)
Apr 14 02:14:01 xoa-installation xo-server[657]: 2020-04-14T00:14:01.996Z xo:main INFO - WebSocket connection (::ffff:127.0.0.1)
Apr 14 02:14:02 xoa-installation xo-server[657]: 2020-04-14T00:14:02.809Z xo:main INFO + WebSocket connection (::ffff:127.0.0.1)
Apr 14 02:14:03 xoa-installation xo-server[657]: 2020-04-14T00:14:03.323Z xo:api WARN root | pool.listMissingPatches(...) [1ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:03 xoa-installation xo-server[657]: 2020-04-14T00:14:03.357Z xo:api WARN root | pool.listMissingPatches(...) [32ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:03 xoa-installation xo-server[657]: 2020-04-14T00:14:03.385Z xo:api WARN root | pool.listMissingPatches(...) [13ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:03 xoa-installation xo-server[657]: 2020-04-14T00:14:03.400Z xo:api WARN root | pool.listMissingPatches(...) [14ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:03 xoa-installation xo-server[657]: 2020-04-14T00:14:03.415Z xo:api WARN root | pool.listMissingPatches(...) [14ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:03 xoa-installation xo-server[657]: 2020-04-14T00:14:03.421Z xo:api WARN root | pool.listMissingPatches(...) [4ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:03 xoa-installation xo-server[657]: 2020-04-14T00:14:03.909Z xo:api WARN root | pool.listMissingPatches(...) [34s] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
.
.
.
Apr 14 02:14:48 xoa-installation xo-server[657]: 2020-04-14T00:14:48.987Z xo:api WARN root | pool.listMissingPatches(...) [2ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:50 xoa-installation xo-server[657]: 2020-04-14T00:14:50.997Z xo:api WARN root | pool.listMissingPatches(...) [2ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:51 xoa-installation xo-server[657]: 2020-04-14T00:14:51.988Z xo:api WARN root | pool.listMissingPatches(...) [2ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:52 xoa-installation xo-server[657]: 2020-04-14T00:14:52.990Z xo:api WARN root | pool.listMissingPatches(...) [3ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:52 xoa-installation xo-server[657]: 2020-04-14T00:14:52.993Z xo:api WARN root | pool.listMissingPatches(...) [2ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:53 xoa-installation xo-server[657]: 2020-04-14T00:14:53.002Z xo:api WARN root | pool.listMissingPatches(...) [8ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:53 xoa-installation xo-server[657]: 2020-04-14T00:14:53.004Z xo:api WARN root | pool.listMissingPatches(...) [2ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:53 xoa-installation xo-server[657]: 2020-04-14T00:14:53.007Z xo:api WARN root | pool.listMissingPatches(...) [2ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:54 xoa-installation xo-server[657]: _watchEvents { Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:54 xoa-installation xo-server[657]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14)
Apr 14 02:14:54 xoa-installation xo-server[657]: errno: 'EHOSTUNREACH',
Apr 14 02:14:54 xoa-installation xo-server[657]: code: 'EHOSTUNREACH',
Apr 14 02:14:54 xoa-installation xo-server[657]: syscall: 'connect',
Apr 14 02:14:54 xoa-installation xo-server[657]: address: '192.168.0.25',
Apr 14 02:14:54 xoa-installation xo-server[657]: port: 443,
Apr 14 02:14:54 xoa-installation xo-server[657]: url: 'https://192.168.0.25/jsonrpc',
Apr 14 02:14:54 xoa-installation xo-server[657]: call:
Apr 14 02:14:54 xoa-installation xo-server[657]: { method: 'event.from',
Apr 14 02:14:54 xoa-installation xo-server[657]: params:
Apr 14 02:14:54 xoa-installation xo-server[657]: [ [Array], '00000000000302450462,00000000000302449388', 60.1 ] } }
Apr 14 02:14:54 xoa-installation xo-server[657]: 2020-04-14T00:14:54.991Z xo:api WARN root | pool.listMissingPatches(...) [3ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:56 xoa-installation xo-server[657]: 2020-04-14T00:14:56.998Z xo:api WARN root | pool.listMissingPatches(...) [1ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:57 xoa-installation xo-server[657]: 2020-04-14T00:14:57.993Z xo:api WARN root | pool.listMissingPatches(...) [3ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:58 xoa-installation xo-server[657]: 2020-04-14T00:14:58.993Z xo:api WARN root | pool.listMissingPatches(...) [3ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:59 xoa-installation xo-server[657]: 2020-04-14T00:14:59.003Z xo:api WARN root | pool.listMissingPatches(...) [9ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:59 xoa-installation xo-server[657]: 2020-04-14T00:14:59.006Z xo:api WARN root | pool.listMissingPatches(...) [2ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:59 xoa-installation xo-server[657]: 2020-04-14T00:14:59.009Z xo:api WARN root | pool.listMissingPatches(...) [2ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:14:59 xoa-installation xo-server[657]: 2020-04-14T00:14:59.012Z xo:api WARN root | pool.listMissingPatches(...) [2ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
Apr 14 02:15:00 xoa-installation xo-server[657]: 2020-04-14T00:15:00.993Z xo:api WARN root | pool.listMissingPatches(...) [3ms] =!> Error: connect EHOSTUNREACH 192.168.0.25:443
.
.
Is there a possibility to get the graphs back in XOA again?
Thanks for your help.
Hi there!
We have updated our XCP-NG Nodes and now we've no statistics in our XOA-Gui from the Time before the Update:
Is this normal and how can we prevent this?
Hi there!
I get an 'Disconnected' Information under the 'XOA' Icon an I don't understand what I've to restart to connect it again :(...
Does anyone have any idea?
@olivierlambert said in How to detect when Backups fails in XOA!?:
Hi,
I'm not sure to understand.
- XOA and Docker? XOA is not available in a container, it's a Debian based virtual appliance. What are you using?
- There is a plugin to do that. Have you read our official doc? https://xen-orchestra.com/docs/backup_reports.html
Hi everyone!
Can you give me an suggestion who I can detect at its best when Backups fails with XOA!?
Is there an possibility to monitor this?
And what can I do to ensure that my Docker-Container with the installed XOA is running?
If it's not running what can I do to get my backed-up VMs working?
Thanks for your help!
How can I get this *.vhd-Files? Do I have to give XOA as "Backup-Type" an .vhd-File? At the moment my created fiels are *.xva-Files....
@Danp
Thanks für your fast reply. We're performing Full-Backups from our VMs