Problems running a node on VPS

[Morblias]

bitcoind keeps closing over and over on a VPS and I am not sure why. I have used 512MB RAM ones in the past that worked just fine. Right now I am using a 768MB RAM one which is causing all kinds of problems. I reboot, start bitcoind, and a couple minutes later it just disappears from the running processes. It is up to block ~270k right now, but will not run for more then 2 minutes before crashing. There is still 15gb free on the hard drive too, so that isn't the issue. Any ideas?

It's supposedly running, but won't show anything. Then the process crashes: https://i.imgur.com/q9FiL1f.png

Last 30 lines in debug.log before it crashed: https://i.imgur.com/6EHQ4wF.png

Also, I have a 2nd node on another VPS from this company with 1GB RAM that is working. Would 768MB RAM be causing this problem? I am kind of confused since a while ago I ran a node on a 512MB RAM VPS with no problems.

[Morblias]

After a bit of googling and reddit help, it looks like the kernel is killing it.



Are there any workarounds, or am I basically shit out of luck unless I upgrade the VPS to more RAM?

[grue]

you can try running with -disablewallet to decrease memory usage.

[2112]

Are there any workarounds, or am I basically shit out of luck unless I upgrade the VPS to more RAM?

Code:

swapon -a

is your friend.

[cp1]

Yeah, it probably isn't using swap space.  Follow this:   https://www.digitalocean.com/community/articles/how-to-configure-virtual-memory-swap-file-on-a-vps

[Morblias]

Unfortunately the VPS didn't allow swap, so I had to cancel that one and buy a different service. At least I know now not to deal with ones without swap.

[dewdeded]

Crashes are standard, during syncing, with < 1 GB RAM.

Set "maxconnections=8" (or even lower like 5) in config and it wont crash anymore because of memorey running out.