Comments (7)
$ for i in $(seq -w 1 10); do echo -n $i ": "; ssh neth-$i.ih-eu-mda1.nimbus.holesky '/data/beacon-n
ode-holesky-unstable/bin/nimbus_beacon_node --version | grep Compiler'; done
01 : Nim Compiler Version 2.0.8 [Linux: amd64]
02 : Nim Compiler Version 2.0.8 [Linux: amd64]
03 : Nim Compiler Version 2.0.8 [Linux: amd64]
04 : Nim Compiler Version 2.0.8 [Linux: amd64]
05 : Nim Compiler Version 2.0.8 [Linux: amd64]
06 : Nim Compiler Version 2.0.3 [Linux: amd64]
07 : Nim Compiler Version 2.0.3 [Linux: amd64]
08 : Nim Compiler Version 2.0.3 [Linux: amd64]
09 : Nim Compiler Version 2.0.3 [Linux: amd64]
10 : Nim Compiler Version 2.0.8 [Linux: amd64]
$ for i in $(seq -w 1 10); do echo -n $i ": "; ssh erigon-$i.ih-eu-mda1.nimbus.holesky '/data/beacon-node-holesky-unstable/bin/nimbus_beacon_node --version | grep Compiler'; done
01 : Nim Compiler Version 2.0.8 [Linux: amd64]
02 : Nim Compiler Version 2.0.8 [Linux: amd64]
03 : Nim Compiler Version 2.0.8 [Linux: amd64]
04 : Nim Compiler Version 2.0.8 [Linux: amd64]
05 : Nim Compiler Version 2.0.8 [Linux: amd64]
06 : Nim Compiler Version 2.0.3 [Linux: amd64]
07 : Nim Compiler Version 2.0.3 [Linux: amd64]
08 : Nim Compiler Version 2.0.8 [Linux: amd64]
09 : Nim Compiler Version 2.0.3 [Linux: amd64]
10 : Nim Compiler Version 2.0.3 [Linux: amd64]
$ for i in $(seq -w 1 10); do echo -n $i ": "; ssh geth-$i.ih-eu-mda1.nimbus.holesky '/data/beacon-n
ode-holesky-unstable/bin/nimbus_beacon_node --version | grep Compiler'; done
01 : Nim Compiler Version 2.0.8 [Linux: amd64]
02 : Nim Compiler Version 2.0.8 [Linux: amd64]
03 : Nim Compiler Version 2.0.8 [Linux: amd64]
04 : Nim Compiler Version 2.0.8 [Linux: amd64]
05 : Nim Compiler Version 2.0.8 [Linux: amd64]
06 : Nim Compiler Version 2.0.3 [Linux: amd64]
07 : Nim Compiler Version 2.0.3 [Linux: amd64]
08 : Nim Compiler Version 2.0.3 [Linux: amd64]
09 : Nim Compiler Version 2.0.3 [Linux: amd64]
10 : Nim Compiler Version 2.0.8 [Linux: amd64]
user@epenomi:~/nimbus-eth2$
Nim 2.0.3 is not expected to work. The fix for this was in 2.0.8.
from nimbus-eth2.
This issue appears to only affect unstable
branch:
> ansible nimbus.holesky -o -a 'curl -s 0:9303/eth/v1/node/syncing | jq -c ".data | { sync_distance }"' | sort
erigon-01.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
erigon-02.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
erigon-03.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
erigon-04.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
erigon-05.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
erigon-06.ih-eu-mda1.nimbus.holesky | {"sync_distance":"101599"}
erigon-07.ih-eu-mda1.nimbus.holesky | {"sync_distance":"101597"}
erigon-08.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
erigon-09.ih-eu-mda1.nimbus.holesky | {"sync_distance":"101593"}
erigon-10.ih-eu-mda1.nimbus.holesky | {"sync_distance":"101587"}
geth-01.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
geth-02.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
geth-03.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
geth-04.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
geth-05.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
geth-06.ih-eu-mda1.nimbus.holesky | {"sync_distance":"101599"}
geth-07.ih-eu-mda1.nimbus.holesky | {"sync_distance":"101600"}
geth-08.ih-eu-mda1.nimbus.holesky | {"sync_distance":"101597"}
geth-09.ih-eu-mda1.nimbus.holesky | {"sync_distance":"101595"}
geth-10.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
neth-01.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
neth-02.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
neth-03.ih-eu-mda1.nimbus.holesky | {"sync_distance":"1"}
neth-04.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
neth-05.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
neth-06.ih-eu-mda1.nimbus.holesky | {"sync_distance":"101597"}
neth-07.ih-eu-mda1.nimbus.holesky | {"sync_distance":"101594"}
neth-08.ih-eu-mda1.nimbus.holesky | {"sync_distance":"101595"}
neth-09.ih-eu-mda1.nimbus.holesky | {"sync_distance":"101588"}
neth-10.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
Mostly nodes with high counts of validators.
from nimbus-eth2.
Here's stable
branch nodes for comparison:
> ansible nimbus.holesky -o -a 'curl -s 0:9301/eth/v1/node/syncing | jq -c ".data | { sync_distance }"' | sort
erigon-01.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
erigon-02.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
erigon-03.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
erigon-04.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
erigon-05.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
erigon-06.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
erigon-07.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
erigon-08.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
erigon-09.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
erigon-10.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
geth-01.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
geth-02.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
geth-03.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
geth-04.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
geth-05.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
geth-06.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
geth-07.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
geth-08.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
geth-09.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
geth-10.ih-eu-mda1.nimbus.holesky | {"sync_distance":"1"}
neth-01.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
neth-02.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
neth-03.ih-eu-mda1.nimbus.holesky | {"sync_distance":"1"}
neth-04.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
neth-05.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
neth-06.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
neth-07.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
neth-08.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
neth-09.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
neth-10.ih-eu-mda1.nimbus.holesky | {"sync_distance":"0"}
No issues whatsoever.
from nimbus-eth2.
Indeed, well spotted, the cause was use of NIM_COMMIT=version-2-0
for the affected nodes which was not removed after the upgrade to Nim 2.0 compiler has taken place. Here's the fix:
infra-nimbus#b55f23af
- holesky: drop override of nim_commit to version-2-0
Changes will be rolled out in the next hour or so.
from nimbus-eth2.
btw, recommending NIM_COMMIT=upstream/version-2-0
for these. sometime there are folks who push an outdated commit to origin/version-2-0
(the status fork) and if upstream/
is not specified explicitly it never bumps to the latest in tests.
from nimbus-eth2.
Indeed, well spotted, the cause was use of
NIM_COMMIT=version-2-0
for the affected nodes which was not removed after the upgrade to Nim 2.0 compiler has taken place. Here's the fix:* [`infra-nimbus#b55f23af`](https://github.com/status-im/infra-nimbus/commit/b55f23af) - holesky: drop override of nim_commit to version-2-0
Changes will be rolled out in the next hour or so.
Have these changes been rolled out? Just checked and still:
$ for i in $(seq -w 1 10); do echo -n $i ": "; ssh geth-$i.ih-eu-mda1.nimbus.holesky '/data/beacon-node-holesky-unstable/bin/nimbus_beacon_node --version | grep Compiler'; done
01 : Nim Compiler Version 2.0.8 [Linux: amd64]
02 : Nim Compiler Version 2.0.8 [Linux: amd64]
03 : Nim Compiler Version 2.0.8 [Linux: amd64]
04 : Nim Compiler Version 2.0.8 [Linux: amd64]
05 : Nim Compiler Version 2.0.8 [Linux: amd64]
06 : Nim Compiler Version 2.0.3 [Linux: amd64]
07 : Nim Compiler Version 2.0.3 [Linux: amd64]
08 : Nim Compiler Version 2.0.3 [Linux: amd64]
09 : Nim Compiler Version 2.0.3 [Linux: amd64]
10 : Nim Compiler Version 2.0.8 [Linux: amd64]
$ for i in $(seq -w 1 10); do echo -n $i ": "; ssh neth-$i.ih-eu-mda1.nimbus.holesky '/data/beacon-node-holesky-unstable/bin/nimbus_beacon_node --version | grep Compiler'; done
01 : Nim Compiler Version 2.0.8 [Linux: amd64]
02 : Nim Compiler Version 2.0.8 [Linux: amd64]
03 : Nim Compiler Version 2.0.8 [Linux: amd64]
04 : Nim Compiler Version 2.0.8 [Linux: amd64]
05 : Nim Compiler Version 2.0.8 [Linux: amd64]
06 : Nim Compiler Version 2.0.8 [Linux: amd64]
07 : Nim Compiler Version 2.0.3 [Linux: amd64]
08 : Nim Compiler Version 2.0.3 [Linux: amd64]
09 : Nim Compiler Version 2.0.3 [Linux: amd64]
10 : Nim Compiler Version 2.0.8 [Linux: amd64]
$ for i in $(seq -w 1 10); do echo -n $i ": "; ssh erigon-$i.ih-eu-mda1.nimbus.holesky '/data/beacon-node-holesky-unstable/bin/nimbus_beacon_node --version | grep Compiler'; done
01 : Nim Compiler Version 2.0.8 [Linux: amd64]
02 : Nim Compiler Version 2.0.8 [Linux: amd64]
03 : Nim Compiler Version 2.0.8 [Linux: amd64]
04 : Nim Compiler Version 2.0.8 [Linux: amd64]
05 : Nim Compiler Version 2.0.8 [Linux: amd64]
06 : Nim Compiler Version 2.0.3 [Linux: amd64]
07 : Nim Compiler Version 2.0.3 [Linux: amd64]
08 : Nim Compiler Version 2.0.8 [Linux: amd64]
09 : Nim Compiler Version 2.0.3 [Linux: amd64]
10 : Nim Compiler Version 2.0.3 [Linux: amd64]
from nimbus-eth2.
I believe this is now resolved.
from nimbus-eth2.
Related Issues (20)
- Checkpoint-synced nodes appear to not use ERA files HOT 2
- Error: Unhandled exception: Asynchronous task [sendMessageSlow() at pubsubpeer.nim:301] was cancelled! [FutureDefect] HOT 8
- Release tarballs missing vendor folder
- Single command for beacon node and checkpoint sync. Remove separate command for `trustedNodeSync` HOT 3
- Require flag when resuming from past-weak-subjectivity database / genesis HOT 1
- build error: incompatible pointer type HOT 7
- Check conten-type and return 415 if not supported by route HOT 7
- Beacon node's P2P degrades permanently after 40 minutes of no connectivity HOT 8
- Bug: Error build with cmd "make -jX nimbus_beacon_node" HOT 11
- Compilation error when "import libp2p/multicodec" is added to sync_manager.nim HOT 12
- Checkpoint sync fails with "Attempt to download checkpoint state timed out" on holesky on all endpoints HOT 7
- [SEC]
- Can no longer use systemd's MemoryDenyWriteExecute on nimbus-beacon-node 24.6.0 HOT 2
- 8GB need for compilation HOT 1
- nimbus spontanously crashes with "database disk image is malformed" HOT 7
- `import` command to create database from era files
- Display of block reward difference between EL block and MEV block HOT 8
- Implement beacon API rewards endpoints
- blob_sidecars with empty response HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nimbus-eth2.