D
Deleted member 33567
Guest
Hello,
I recently installed and configured a fully working 3 nodes cluster HA with CEPH and all works fine.
Up to the point when in SYSLOG of each nodes, I get this, repetitively each day:
APPARMOR Related:
PVE DAEMON Related:
Next I have this on NODE1:
While NODE2 has:
How to remediate the issue from NODE1: not correctly installed, no idea why this is there, these are predefined images from OVH, and since then we had them reinstalled they all run with KernelCare on them since first day...
Next about QEMU2 Images. I recently downloaded from Centos repository a GenericCloud image, in QEMU2 format, and I am curious how do I add such images to allow users to deploy them as KVM or LXC.
I recently installed and configured a fully working 3 nodes cluster HA with CEPH and all works fine.
Up to the point when in SYSLOG of each nodes, I get this, repetitively each day:
APPARMOR Related:
Code:
Jul 21 03:40:06 node01-sxb-pve01 kernel: audit_printk_skb: 384 callbacks suppressed
Jul 21 03:40:06 node01-sxb-pve01 kernel: audit: type=1400 audit(1500601206.172:6044): apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/named" name="/run/systemd/journal/dev-log" pid=12986 comm="named" requested_mask="w" denied_mask="w" fsuid=0 ouid=0PVE DAEMON Related:
Code:
Jul 21 03:17:51 node01-sxb-pve01 pvedaemon[8049]: Use of uninitialized value in numeric ne (!=) at /usr/share/perl5/PVE/API2/Qemu.pm line 1433.Next I have this on NODE1:
Code:
proxmox-ve: not correctly installed (running kernel: 4.4.67-1-pve) pve-manager: 4.4-15 (running version: 4.4-15/7599e35a) pve-kernel-4.4.67-1-pve: 4.4.67-92 pve-kernel-4.4.49-1-pve: 4.4.49-86 lvm2: 2.02.116-pve3 corosync-pve: 2.4.2-2~pve4+1 libqb0: 1.0.1-1 pve-cluster: 4.0-52 qemu-server: 4.0-110 pve-firmware: 1.1-11 libpve-common-perl: 4.0-95 libpve-access-control: 4.0-23 libpve-storage-perl: 4.0-76 pve-libspice-server1: 0.12.8-2 vncterm: 1.3-2 pve-docs: 4.4-4 pve-qemu-kvm: 2.7.1-4 pve-container: 1.0-100 pve-firewall: 2.0-33 pve-ha-manager: 1.0-41 ksm-control-daemon: 1.2-1 glusterfs-client: 3.5.2-2+deb8u3 lxc-pve: 2.0.7-4 lxcfs: 2.0.6-pve1 criu: 1.6.0-1 novnc-pve: 0.5-9 smartmontools: 6.5+svn4324-1~pve80 zfsutils: 0.6.5.9-pve15~bpo80 ceph: 10.2.9-1~bpo80+1While NODE2 has:
Code:
proxmox-ve: 4.4-92 (running kernel: 4.4.67-1-pve) pve-manager: 4.4-15 (running version: 4.4-15/7599e35a) pve-kernel-4.4.67-1-pve: 4.4.67-92 pve-kernel-4.4.62-1-pve: 4.4.62-88 lvm2: 2.02.116-pve3 corosync-pve: 2.4.2-2~pve4+1 libqb0: 1.0.1-1 pve-cluster: 4.0-52 qemu-server: 4.0-110 pve-firmware: 1.1-11 libpve-common-perl: 4.0-95 libpve-access-control: 4.0-23 libpve-storage-perl: 4.0-76 pve-libspice-server1: 0.12.8-2 vncterm: 1.3-2 pve-docs: 4.4-4 pve-qemu-kvm: 2.7.1-4 pve-container: 1.0-100 pve-firewall: 2.0-33 pve-ha-manager: 1.0-41 ksm-control-daemon: 1.2-1 glusterfs-client: 3.5.2-2+deb8u3 lxc-pve: 2.0.7-4 lxcfs: 2.0.6-pve1 criu: 1.6.0-1 novnc-pve: 0.5-9 smartmontools: 6.5+svn4324-1~pve80 zfsutils: 0.6.5.9-pve15~bpo80 ceph: 10.2.9-1~bpo80+1How to remediate the issue from NODE1: not correctly installed, no idea why this is there, these are predefined images from OVH, and since then we had them reinstalled they all run with KernelCare on them since first day...
Next about QEMU2 Images. I recently downloaded from Centos repository a GenericCloud image, in QEMU2 format, and I am curious how do I add such images to allow users to deploy them as KVM or LXC.