stopped a node in its tracks today. This is the first time I have ever seen this message. I was fiddling with the node's config earlier and ended up resetting it to default. Now, I get this error.
I used this hack because of the lack of hardware rng support. The problem did never appear afterwards.
I already mentioned it in the Gitlab issue linked in the other answer and copied it here for convince.
I haven't seen this myself before, but other people have apparently. According to that, the issue should be fixed now, but perhaps there is some useful stuff in the comments that might help you
# check hard limit on user
ulimit -Hn
# check soft limit on user
ulimit -Sn
sudo vi /etc/security/limits.conf
Add a line of “<USERNAME> soft nofile <limit>”
This issue affected a few people early on, it would crash nodes randomly. I've myself seen this at random times early but have not seen such occurrences since (due to the below fix and node updates). The recommended solution at the time is to increase the linux limits on number of files open, you can follow the solution here.
To summarize:
# check hard limit on user
ulimit -Hn
# check soft limit on user
ulimit -Sn
sudo vi /etc/security/limits.conf
Add a line of “<USERNAME> soft nofile <limit>”
此错误:
今天停止了其节点的前进.这是我第一次看到此消息.我之前在摆弄节点的配置,最后将其重置为默认值.现在,我收到此错误.