I am new to the forum here but did make sure to read the guidelines and the formatting suggestions. If there's still something I'm doing incorrectly or not at all (that I should in fact be doing) then feel free to let me know.
I believe it's best to start of with some brief context and mention that the problem I'm going to describe I experience on both FreeBSD 12.1-p10 as well as the latest patch for FreeBSD 11.4. I will leave the technical specifications of the machine at the very end of this post. I own a VPS instance which is QEMU/KVM-powered (version 2.12.0 according to an employee of the VPS provider). The problem is that after minimum a day but sometimes multiples days later FreeBSD indiscriminately starts killing processes, including sshd when I try to SSH in. At the console I can see it even killed multiple instances of getty and complains about a lack of swap space.
Once or twice caught it while this process was ongoing and
This particular virtual machine has access to a single processor and 1 GB of system memory. I have two swap partitions: the first is 256 MB in size while the latter (which I intend to eventually configure for holding memory dumps) is 1GB in size. I doubt it's relevant but for the sake of completeness I'll mention that the storage space allocated to the machine is 20 GB. They also refused to use the qcow2 image but they were willing to add the iso so I could install it myself.
I believe it's best to start of with some brief context and mention that the problem I'm going to describe I experience on both FreeBSD 12.1-p10 as well as the latest patch for FreeBSD 11.4. I will leave the technical specifications of the machine at the very end of this post. I own a VPS instance which is QEMU/KVM-powered (version 2.12.0 according to an employee of the VPS provider). The problem is that after minimum a day but sometimes multiples days later FreeBSD indiscriminately starts killing processes, including sshd when I try to SSH in. At the console I can see it even killed multiple instances of getty and complains about a lack of swap space.
Once or twice caught it while this process was ongoing and
$ ps -auxw
as well as $ top -S
reported barely any (a few MiBs at most) of the swap space was being used and no process seemed to be using a large amount of system memory either. I recall that the majority of it was listed as "Wired", approximately 600M - I have no idea what the significance of this is and definitely don't know what "wired" means.This particular virtual machine has access to a single processor and 1 GB of system memory. I have two swap partitions: the first is 256 MB in size while the latter (which I intend to eventually configure for holding memory dumps) is 1GB in size. I doubt it's relevant but for the sake of completeness I'll mention that the storage space allocated to the machine is 20 GB. They also refused to use the qcow2 image but they were willing to add the iso so I could install it myself.
Last edited by a moderator: