Fullnode - Out of memory error on 4GB RAM


  • Reward

    Hi Dev team,

    My fullnode has not been able to sync fully since yesterday as it keeps going down with an out of memory error. It has 4 GB RAM which should be sufficient for a full node. The error message is pretty long so just pasting the first few lines from the log:

    *fatal error: runtime: out of memory

    runtime stack:
    runtime.throw(0xde3fda, 0x16)
    /usr/local/go/src/runtime/panic.go:616 +0x81
    runtime.sysMap(0xc4ff020000, 0x2f60000, 0xa5f300, 0x145c5f8)
    /usr/local/go/src/runtime/mem_linux.go:216 +0x20a
    runtime.(*mheap).sysAlloc(0x1442680, 0x2f60000, 0xb2d520)
    /usr/local/go/src/runtime/malloc.go:470 +0xd4
    runtime.(*mheap).grow(0x1442680, 0x17aa, 0x0)
    /usr/local/go/src/runtime/mheap.go:907 +0x60
    runtime.(*mheap).allocSpanLocked(0x1442680, 0x17aa, 0x145c608, 0xc41deb7423)
    /usr/local/go/src/runtime/mheap.go:820 +0x301
    runtime.(*mheap).alloc_m(0x1442680, 0x17aa, 0x101, 0x18)
    /usr/local/go/src/runtime/mheap.go:686 +0x118
    runtime.(*mheap).alloc.func1()
    /usr/local/go/src/runtime/mheap.go:753 +0x4d
    runtime.(mheap).alloc(0x1442680, 0x17aa, 0x10101, 0x0)
    /usr/local/go/src/runtime/mheap.go:752 +0x8a
    runtime.largeAlloc(0x2f53fc9, 0xc420060101, 0x4559fa)
    /usr/local/go/src/runtime/malloc.go:826 +0x94
    runtime.mallocgc.func1()
    /usr/local/go/src/runtime/malloc.go:721 +0x46
    runtime.systemstack(0x0)
    /usr/local/go/src/runtime/asm_amd64.s:409 +0x79
    runtime.mstart()
    /usr/local/go/src/runtime/proc.go:1175


  • Reward

    Could you reproduce this issue somewhere else? There error logs are too general to locate the real issue. Have you checked memory consumption of other processes that happened to be running at the same time?


  • Reward

    There aren't any other major processes running on the system. Its a VPS specifically for Vite. On one of the other nodes which hasn't gone down yet (but is syncing very slowly), gvite is using 90% of the available RAM.

    I'll try to monitor for any other spikes though.


  • Reward

    For now, marking this as solved. The node synced but only after I assigned some swap memory to it on top of the 4GB RAM. Will look out to see if it happens again.


Log in to reply