Server issues

Server issues

UPDATE: 2018-05-25

Geth has been identified as the ultimate culprit by eating all available RAM causing the server to go to a crawl. I’ve switched the node to parity to fix the issue.

The change to parity as the main websocket thin client provider however has caused an error related to filters uninstall call in the RPC. Etherwall 2.2.3 has been released with a fix so parity can be used as the backend.

Syncing is still in progress. I will update the server status and remove the warning message when it’s done.

ORIGINAL: 2018-05-23

The main Etherwall server hosting both the services for thin client and this website is experiencing memory related issues atm.

The culprit seems to be geth itself taking up all RAM (32gb+) and causing OOM killer to kick in. The last long downtime might have been related to this issue as well.

Last server downtime caused a loss of recent DB data as well due to a hard reset. I’m currently trying to find out how to limit impact if geth decides to gobble up all the RAM again.

The DB data lost is related to the historic transactions requests. The DB is being rebuilt from scratch but historical transactions list will remain outdated for a few days.

 


Comments are closed.