frankf1957

@huttarichard I have never had this collision you speak of. I just checked my testnet system, and there is no node binary found on the PATH. I tried both of...

[elrond-node-0-dede76b030d3.log-20220705-1639.tar.gz](https://github.com/ElrondNetwork/elrond-go/files/9048184/elrond-node-0-dede76b030d3.log-20220705-1639.tar.gz)

These are validator nodes only. These are not full-copy nodes either. These nodes are not used to resolve API requests. I am running these nodes in support of the development...

I will change my systemd unit files to add --log-save to cause the nodes to log to disk. If this happens again we may find details in the disk logs...

Done and nodes restarted. The ExecStart directive in the systemd unit files are all set like this one now: ~~~ ExecStart=/home/elrond/elrond-nodes/node-0/node -log-save -profile-mode -log-logger-name -log-correlation -log-level *:DEBUG -rest-api-interface localhost:8080 ~~~

I have another instance of a running node killed by the the kernel oom killer. Messages recorded in /var/log/syslog: ~~~ Jul 7 21:52:20 elrond-devnet-en6-hel1-1 kernel: [454779.767489] apps.plugin invoked oom-killer: gfp_mask=0xcc0(GFP_KERNEL),...

Hi @bogdan-rosianu - Should be plenty of resources - this machine has 32G Ram and 16 vCPUs, no swap configured: ~~~ $ free -m total used free shared buff/cache available...

Hi @AdoAdoAdo I am still experiencing this issue with my DEVNET nodes. When I reported this issue the node version was D1.3.31. It was upgraded to D1.3.36 as soon as...

[syslog.oom-kill.log](https://github.com/ElrondNetwork/elrond-go/files/9376374/syslog.oom-kill.log)

I got a "File size too big" error trying to upload the node logs tar.gz file. I have unpacked them, and will upload individually.