-
Notifications
You must be signed in to change notification settings - Fork 528
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OOM kill #2576
Comments
What version of Acala? Is this a new node? How big is the db folder? Can you try to remove |
Yes,it is a new node. acala version: 2.19.0-unknown db folder: |
|
How long does it take to crash? Would you be able to plot a graph of the memory usage since the node starts? Would you be able to reproduce this on a different machine? |
启动后,同步30s-1m就触发了oom killl. 我切换到full node 一样出现这种情况 |
2023-07-19 01:50:59 Acala Node |
|
What's the OS and kernel version? |
Linux distribution: Ubuntu 20.04.5 LTS 5.4.0-135-generi |
I am suspecting this is due to a kernel bug. The version you are using looks like old. Is it possible for you to try to upgrade to a recent version or try on a machine with recent OS? |
我现在删除数据, --database paritydb 用这个db试试 |
I'll try upgrading the kernel |
start_acala.sh: line 3: 3204 Killed acala --base-path /opt/rockx/acala --chain=acala --execution wasm --rpc-cors all --rpc-external --ws-external --pruning archive --no-prometheus -- --chain=polkadot system info:ubuntu 22.04TLS ,kennel: 5.15.0-76-generic |
Can you try this https://askubuntu.com/a/1405588 |
This handling will cause the system to fake death, and then the server cannot be logged in and only be restarted |
I don't really think this is an issue in Acala node. Could you try other chains like Polkadot or other parachains? And let me know if this happens on other machines. |
statemint\polkadex\Moonbeam There are no problem with these chains |
Why don't others have this problem? |
This is the only report of OOM issue we have received and I cannot reproduce the issue. Can you try to reproduce this on a different machine? |
I test on another server |
It's really a server problem, I replaced a server that configured the same configuration, without OOM-Kill |
I run the acala archive node, can't synchronize the data. The system always has been in OOM KILL
💻 CPU: Intel(R) Xeon(R) E-2236 CPU @ 3.40GHz
💻 CPU cores: 6
💻 Memory: 64091MB
💻 Kernel: 5.4.0-135-generic
💻 Linux distribution: Ubuntu 20.04.5 LTS
The startup parameter configuration is:
acala --base-path /opt/data/acala --chain=acala --execution wasm --wasm-execution compiled --db-cache 16000 --rpc-cors all --rpc-external --ws-external --pruning archive --no-prometheus -- --chain=polkadot
how to fix this issues??
The text was updated successfully, but these errors were encountered: