Reply from RackNerdAug 10, 2023
Hello Davide,
It appears this is a repost of a review you shared back in November 2022? Since then, we have not been made aware of any further issues, and to our knowledge, you have not maintained any active service with us since. We welcome open communication if there is still anything outstanding to discuss, just e-mail us at bizdev[@]racknerd[dot]com and we'd be happy to help.
For clarity, we've included our previous response from November 2022 below. To recap, our analysis indicated the issue stemmed from your specific configuration. Despite offering an unmanaged service, our team had provided suggestions to assist you at that time.
—
Original Response Below:
Hi @davide -- appreciate you following up. I was able to pull up your account, and in the one and only support ticket I am able to see under your account (let me know if I'm mistaken, or if you may have created a ticket from a different email, etc), it looks like our team had reached out to you as a follow up (but we did not hear back from you after our response on July 7), suggesting that you may have OOM'd as a result of the applications running within your VPS. You mentioned here you purchased an expansion/upgrade pack, but I am not seeing any upgrades or addons purchased, your VPS is still intact with the original included amount of RAM with the package nor do I see any communication within your account related to purchasing an upgrade. In your ticket, you mentioned some concerns about your VM utilizing swap space, and I do see that our team followed up and made some suggestions for you with regards to optimizing your vm.swappiness level from within your VM's operating system level. By default most Linux distributions have the vm.swappiness level at 60, and also keep in mind https://www.linuxatemyram.com/ - so it is normal for some swap usage to be utilized unless you specifically notate otherwise in the vm.swappiness level within your OS.
Furthermore, I just personally checked the node your VPS resides on (DAL107KVM) and do not see any current issues nor any resource contention (this node actually looks to be pretty quiet in terms of resource utilization). Even still we'd like to work with you on a resolution path here, if you don't mind, ultimately we're only happy if our customers are happy, so let's work together on identifying an amicable solution.