Beacon-Chain logs getting stuck | high CPU temperatures

Since the Prysm update to Version: 1.0.7 (v1.1.0 upstream) my beacon chain (bc) log getting stuck, after running for ~1d without any notable issues. Then the client memory and the cpu temperature starts to increase.

There are no error messages on the bc log. When the bc log gets stuck the validator keeps running without any notable issues, except: the effectiveness of my validator declines slightly.

Restarting of the bc container solves the problem just temporary. After ~1d the bc log gets stuck again.

Thanks for any help!

Before filing a new issue, please provide the following information.

Core DAppNode Packages versions

  • 0.2.14
  • 0.2.7, commit: 12ae223f
  • 0.2.5
  • 0.2.37, commit: 2b96e582
  • 0.2.41
  • 0.2.6

System info

  • docker version: Docker version 18.09.8-ce, build 0dd43dd87fd530113bf44c9bba9ad8b20ce4637f
  • docker compose version: docker-compose version 1.25.5, build unknown
  • platform: linux, x64, 4.19.0-12-amd64
  • Disk usage: 434328567808

It’s already fixed :smile:

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.