After updating the kernel to 3.14.0, the error ‘Swap not configured (instance 10.5.4.3:9100)’ is displayed on the details page.
After restarting the node, the correct configuration is displayed - no error.
After updating the kernel to 3.14.0, the error ‘Swap not configured (instance 10.5.4.3:9100)’ is displayed on the details page.
After restarting the node, the correct configuration is displayed - no error.
Did you check the swap of the node when the alert was shown?
Did you wait a few minutes if the alert goes away? Maybe it was some old (wrong) alert?
This also occurs if for example you created a swapfile and configured it in /etc/fstab but it wasn’t initialized by swapon.
may be I’m wrong.
After a while the error came back.
I checked it with lsblk: no SWAP partion is shown.
~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sr0 11:0 1 1024M 0 rom
vda 254:0 0 512G 0 disk
├─vda1 254:1 0 2M 0 part
├─vda2 254:2 0 1G 0 part /boot
└─vda3 254:3 0 511G 0 part /var/lib/containers/storage/overlay
I’m questioning my mental health right now because I’m ‘sure’ that during the update, swap usage rose to about 20%. Displayed in the old node details.
I was obviously hallucinating…
Since this happens with all cloud servers, it’s probably because the provider doesn’t provide a SWAP partition.
So I created a swap file.
I am deeply confused about my perceptions.
most of cloud providers does not want the usage of swap on SSD, hence the lack of swap