Hi @BenjiReis,
Yes. Problem solved by adding the following lines to the resolv.conf file:

domain Mydoamin.com
search Mydoamin.com

@olivierlambert :

# xe pdb-unplug
Unknown command: pdb-unplug
For usage run: 'xe help'

@olivierlambert:

# xe sr-forget uuid=4b89fe07-7859-ddee-fb5f-77d3f45b0753
The SR is still connected to a host via a PBD. It cannot be destroyed or forgotten.
sr: 4b89fe07-7859-ddee-fb5f-77d3f45b0753 (SMB ISO library)

Where is xe pbd-unplug uuid=<UUID of PBD> command?

@olivierlambert Thanks, but the problem is that I get the same error for forgetting ISO SR.

@olivierlambert, Yes:

# ping ISOREPO
PING ISOREPO.Mydoamin.com (172.20.1.18) 56(84) bytes of data.
64 bytes from ISOREPO.Mydoamin.com (172.20.1.18): icmp_seq=1 ttl=128 time=1.44 ms
64 bytes from ISOREPO.Mydoamin.com (172.20.1.18): icmp_seq=2 ttl=128 time=0.350 ms
64 bytes from ISOREPO.Mydoamin.com (172.20.1.18): icmp_seq=3 ttl=128 time=0.426 ms
64 bytes from ISOREPO.Mydoamin.com (172.20.1.18): icmp_seq=4 ttl=128 time=0.373 ms
^C
--- ISOREPO.Mydoamin.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 0.350/0.648/1.444/0.460 ms

About the PBD:

# xe sr-list
uuid ( RO)                : f6852f22-2099-a9b6-1731-95807eaa95c6
          name-label ( RW): DVD drives
    name-description ( RW): Physical DVD drives
                host ( RO): xcp-ng
                type ( RO): udev
        content-type ( RO): iso


uuid ( RO)                : 4b89fe07-7859-ddee-fb5f-77d3f45b0753
          name-label ( RW): SMB ISO library
    name-description ( RW): SMB ISO Library [\\ISOREPO\ISO\OS\]
                host ( RO): xcp-ng
                type ( RO): iso
        content-type ( RO): iso


uuid ( RO)                : 00f82a18-a9f6-f7bc-9ca1-f42698d46b5f
          name-label ( RW): Local storage
    name-description ( RW): 
                host ( RO): xcp-ng
                type ( RO): lvm
        content-type ( RO): user


uuid ( RO)                : 71424c21-0260-af80-b394-200e49ec767a
          name-label ( RW): XCP-ng Tools
    name-description ( RW): XCP-ng Tools ISOs
                host ( RO): xcp-ng
                type ( RO): iso
        content-type ( RO): iso


uuid ( RO)                : daf51f1b-bb25-4a58-3358-f3f5671a2771
          name-label ( RW): Removable storage
    name-description ( RW): 
                host ( RO): xcp-ng
                type ( RO): udev
        content-type ( RO): disk


uuid ( RO)                : c5129868-a590-68ca-e587-db708ad61f38
          name-label ( RW): Hardware HBA virtual disk storage
    name-description ( RW): Hardware HBA SR [HP - 500143801914D7C0]
                host ( RO): xcp-ng
                type ( RO): lvmohba
        content-type ( RO): 

Hi @olivierlambert,
The ISO file is located on a Windows server. I can see that file via other computers in the network. From the XCP-ng host, I can ping that server.

Hello,
I upgraded XO to the latest version. I want to create a VM and the operating system ISO file is on another server. I had previously mounted it via SMB:

I created a new virtual machine and when I try to run it I get the following error message:

SR_BACKEND_FAILURE_140(, Incorrect DNS name, unable to resolve., )

Even when I try to delete this SMB ISO I get the same error message. What is wrong?

Thank you.

Thank you @olivierlambert.

Hello,
In the current XO directory, I did git pull command. It seems that some files have changed and need to be updated. Do I have to redo all the steps I did to install XO to update?

Thank you.

Hello,
I created a network as below:

When I want to remove this network, it shows me the following error:

PIF_VLAN_STILL_EXISTS(OpaqueRef:d9c8b8df-718e-4bc3-bfe5-d7894d73871b)

How to solve it?

Thank you.

Hello,
How can I add a new disk to my VM via CLI?
Can I remove /usr/local/share/.cache/yarn directory?
Thank you.

@Danp, The problem is that I cannot log into XO and add a hard disk to the server.

Sure @Danp.

# df -h
Filesystem               Size  Used Avail Use% Mounted on
udev                     1.9G     0  1.9G   0% /dev
tmpfs                    390M  1.2M  388M   1% /run
/dev/mapper/XO--vg-root  9.9G  9.8G     0 100% /
tmpfs                    1.9G     0  1.9G   0% /dev/shm
tmpfs                    5.0M     0  5.0M   0% /run/lock
/dev/xvda1               455M  107M  324M  25% /boot
/dev/mapper/XO--vg-home   18G  1.2G   16G   7% /home
tmpfs                    390M     0  390M   0% /run/user/1000
overlay                  9.9G  9.8G     0 100% /var/lib/docker/overlay2/0e011d58e7503beccd9282090df460ef949a1dca7403f5a5c4c46263ab5b0d1c/merged
overlay                  9.9G  9.8G     0 100% /var/lib/docker/overlay2/2b13a8e34054bf192c39d1f4086cf71f5f0c6929b7650e1400e0fb2c7a46f0b5/merged
overlay                  9.9G  9.8G     0 100% /var/lib/docker/overlay2/92d4574890e095d4721be60502c4cba0e17c48ed37a2ddad4214d47b68587425/merged
overlay                  9.9G  9.8G     0 100% /var/lib/docker/overlay2/bb69a180860c8eb012ad5fdf82e227906d887cc66ba1c6a2ae23d52802bc394e/merged
overlay                  9.9G  9.8G     0 100% /var/lib/docker/overlay2/a419c094f8e5f4ea8672d1d0b01947d2db9a206be5554a43fcb5f1fb72c3c3bd/merged
overlay                  9.9G  9.8G     0 100% /var/lib/docker/overlay2/4e28ba0551b4d24fb0430a46c53d119b18ef1b0a50cab3d984c8b196492e0fb0/merged
overlay                  9.9G  9.8G     0 100% /var/lib/docker/overlay2/b080821d7cd8f946abe06574c60843e0b025b7be528f4dac07b60f5b627325fe/merged

Hi @Danp,
Thank you so much for your reply.
I got the following error:

# ./node_modules/xo-server/dist/recover-account-cli.mjs admin
Password (leave empty for random): *******
✖ MISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
undefined

Hello,
I can't find xo-server-recover-account tool. Is it an extra tool?

Thank you.

@olivierlambert, I just enabled and disabled the server and the problem went away.

@olivierlambert said in CERT_NOT_YET_VALID:

Hi,

You might check the NTP configuration on the host or in your XOA.

Hi,
Thank you so much.

Hello,
I added another XCP-ng server (Test) and added it to the XO as shown below:

But I can't see it in the Hosts section. It shows me a red triangle with a CERT_NOT_YET_VALID error. Why?

Thank you.

@Danp, does this cause a problem?

Hi @Danp,
In the Always Running section, when you click on forever, you will go to the Github address and it is written there.