Hi all,
Twice this morning my VPS running FreeBSD v11 became unresponsive. Logging into the console at my host service it appears to have run out of swap space and twice I was forced to reboot. The server has 1GB of RAM and 1.7GB swap.
I am pretty sure it is a www/nextcloud process, but obviously I can't be 100% sure.
I've never encountered this issue before in all my years running a FreeBSD server.
A couple of questions:
First, are there any techniques to contain www/apache24 (or lang/php56?) to prevent the entire server from being affected? Ie, a jail?
Second, are there any mechanisms for determining what process might be leaking memory? I mentioned the issue on the Nextcloud forum this morning, and a dev told me to open an issue on Github, but I feel that if I don't make some effort to determine whether the issue is in fact a Nextcloud process they may just shrug.
Thanks for any ideas.
Twice this morning my VPS running FreeBSD v11 became unresponsive. Logging into the console at my host service it appears to have run out of swap space and twice I was forced to reboot. The server has 1GB of RAM and 1.7GB swap.
I am pretty sure it is a www/nextcloud process, but obviously I can't be 100% sure.
I've never encountered this issue before in all my years running a FreeBSD server.
A couple of questions:
First, are there any techniques to contain www/apache24 (or lang/php56?) to prevent the entire server from being affected? Ie, a jail?
Second, are there any mechanisms for determining what process might be leaking memory? I mentioned the issue on the Nextcloud forum this morning, and a dev told me to open an issue on Github, but I feel that if I don't make some effort to determine whether the issue is in fact a Nextcloud process they may just shrug.
Thanks for any ideas.