Getting this? bash: /usr/local/bin/node: No such file or directory Fix with: [root@xoa-org01 bin]# node -v -bash: /usr/local/bin/node: No such file or directory [root@xoa-org01 bin]# . ~/.bash_profile [root@xoa-org01 bin]# node > .exit [root@xoa-org01 bin]# node -v v8.16.2 [root@xoa-org01 bin]# Thx, TK

If you're getting this error:   Oct 14 01:43:26 xcpng01 xapi: [error|xcpng01.nix.mds.xyz|3179 UNIX /var/lib/xcp/xapi|dispatch:SR.get_uuid D:3c84eaa48cb2|backtrace] SR.get_uuid D:855756122ab7 failed with exception Db_exn.DBCache_NotFound("missing row", "SR", "OpaqueRef:NULL")

To create a plugin entry for XCP-ng 8.0.1, follow the following procedure ( We will use the GlusterFS plugin for this example. ): Create the GlusterFS repo: [19:40 xcpng02 sm]# cat /etc/yum.repos.d/gluster63.repo [gluster63] name=Gluster 6.3 baseurl=http://mirror.centos.org/centos/7/storage/x86_64/gluster-6/ gpgcheck=0 enabled=1 [19:41 xcpng02 sm]#

HTTPS pages are slow to load.  If you have this issue, try the following: Visit Services -> Cryptsvc (Cryptographic Services) -> Properties -> Logon Tab -> Select Local System Account Cheers, TK

Create local storage under XCP-ng as follows.  

Creating PV's, VG's and LV's under XCP-ng.   [06:47 xcpng02 ~]# [06:47 xcpng02 ~]# pvremove /dev/sdb   pvremove /dev/sdb: Command not permitted while global/metadata_read_only is set. [06:47 xcpng02 ~]# pvremove /dev/sdb –config global{metadata_read_only=0}   Labels on physical volume "/dev/sdb" successfully wiped. [06:47 xcpng02 ~]# pvcreate /dev/sdb –config global{metadata_read_only=0}   Physical volume "/dev/sdb" successfully created. [06:47 […]

Getting this? [root@mdskvm-p01 ~]# gluster volume delete mdsgv01 Deleting volume will erase all information about the volume. Do you want to continue? (y/n) y volume delete: mdsgv01: failed: Some of the peers are down [root@mdskvm-p01 ~]# [root@mdskvm-p01 ~]# gluster volume remove-brick mdsgv01  mdskvm-p01.nix.mds.xyz:/mnt/p01-d01/glusterv01 force Remove-brick force will not migrate files from the removed bricks, so […]

NOTE: Experimental steps.  Use at your own discretion.  Also note that ultimately, these steps didn't resolve the subject errors though they were successful in updating the VDSM certs.  I ended up blowing the cluster away (as I didn't have much on it anyway). Getting this with oVirt? VDSM mdskvm-p01.nix.mds.xyz command Get Host Capabilities failed: General […]

Getting this? /var/log/glusterfs/bricks/mnt-p01-d01-glusterv01.log [2019-09-25 10:53:37.847426] I [MSGID: 100030] [glusterfsd.c:2847:main] 0-/usr/sbin/glusterfsd: Started running /usr/sbin/glusterfsd version 6.5 (args: /usr/sbin/glusterfsd -s mdskvm-p01.nix.mds.xyz –volfile-id mdsgv01.mdskvm-p01.nix.mds.xyz.mnt-p01-d01-glusterv01 -p /var/run/gluster/vols/mdsgv01/mdskvm-p01.nix.mds.xyz-mnt-p01-d01-glusterv01.pid -S /var/run/gluster/defbdb699838d53b.socket –brick-name /mnt/p01-d01/glusterv01 -l /var/log/glusterfs/bricks/mnt-p01-d01-glusterv01.log –xlator-option *-posix.glusterd-uuid=f7336db6-22b4-497d-8c2f-04c833a28546 –process-name brick –brick-port 49155 –xlator-option mdsgv01-server.listen-port=49155) [2019-09-25 10:53:37.848508] I [glusterfsd.c:2556:daemonize] 0-glusterfs: Pid of current running process is 23133 [2019-09-25 10:53:37.858381] I [socket.c:902:__socket_server_bind] 0-socket.glusterfsd: closing […]

Getting this in a two node cluster? volume set: failed: Quorum not met. Volume operation not allowed. If you can't afford a third, you'll have to disable the quorum: [root@mdskvm-p01 glusterfs]# [root@mdskvm-p01 glusterfs]# gluster volume info Volume Name: mdsgv01 Type: Replicate Volume ID: f5b57076-dbd4-4d77-ae13-c1f3ee3adbe0 Status: Stopped Snapshot Count: 0 Number of Bricks: 1 x 2 […]