eth-pkg / eth-nodes Goto Github PK
View Code? Open in Web Editor NEWComposable, Reproducible builds for Ethereum Ecosystem (Debian/Ubuntu)
License: GNU Affero General Public License v3.0
eth-nodes's People
Contributors
Stargazers
Watchers
eth-nodes's Issues
Integrate dh-ethpkg-javascript
Fix eth-node-erigon debian12 version 2.53.2-1 test
Err system.d service if node doesn't have hardware requirements
Based on official docs
There is enough disk space considering the chosen network and sync mode.
Memory and CPU is not halted by other programs.
Operating system is updated to the latest version.
System has the correct time and date.
Your router and firewall accept connections on listening ports. By default Ethereum clients use a listener (TCP) port and a discovery (UDP) port, both on 30303 by default
fix eth-node-teku git version information
Not building from a git checkout. Version information will not be available. Building from a git checkout is strongly recommended.
Setup minimal config for eth-node-erigon
Acceptance criteria:
- test should be running that node starts, and no error
- test upgrade/remove/install
- system.d service is running without error
- dpkg-configure reconfigures config
Fix eth-node-lighthouse debian12 version 4.5 test
The Lighthouse build is failing under build env.
Integrate sbuild environment
Remove configuration/service packages from build for node build milestone
Fix eth-node-teku debian12 version 23.10.0-1 test
CKZG4844UtilsTest > testFlattenBlobsWithUnexpectedSizeThrows() FAILED
org.opentest4j.AssertionFailedError at CKZG4844UtilsTest.java:42
CKZG4844UtilsTest > testFlattenBlobsWithBigBoySizeThrows() FAILED
org.opentest4j.AssertionFailedError at CKZG4844UtilsTest.java:53
21 tests completed, 2 failed
> Task :infrastructure:kzg:test FAILED
> Task :teku:test
Exception in thread "nioEventLoopGroup-4-1" java.util.concurrent.CompletionException: java.util.concurrent.RejectedExecutionException: Task tech.pegasys.teku.infrastructure.events.AsyncEventDeliverer$QueueReader@1279c4ab rejected from java.util.concurrent.ThreadPoolExecutor@42b81fe8[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0]
at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320)
at java.base/java.util.concurrent.CompletableFuture$UniAccept.tryFire(CompletableFuture.java:722)
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2147)
at tech.pegasys.teku.infrastructure.async.SafeFuture.lambda$propagateResult$3(SafeFuture.java:146)
at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863)
at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841)
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2147)
at tech.pegasys.teku.infrastructure.async.SafeFuture.lambda$propagateResult$3(SafeFuture.java:146)
at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863)
at java.base/java.util.concurrent.CompletableFuture.uniWhenCompleteStage(CompletableFuture.java:887)
at java.base/java.util.concurrent.CompletableFuture.whenComplete(CompletableFuture.java:2325)
at tech.pegasys.teku.infrastructure.async.SafeFuture.whenComplete(SafeFuture.java:623)
at tech.pegasys.teku.infrastructure.async.SafeFuture.whenComplete(SafeFuture.java:31)
at tech.pegasys.teku.infrastructure.async.SafeFuture.propagateResult(SafeFuture.java:141)
at tech.pegasys.teku.infrastructure.async.SafeFuture.lambda$exceptionallyCompose$34(SafeFuture.java:423)
at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863)
at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841)
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2147)
at tech.pegasys.teku.infrastructure.async.SafeFuture.lambda$propagateResult$3(SafeFuture.java:146)
at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863)
at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841)
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2147)
at tech.pegasys.teku.infrastructure.async.SafeFuture.lambda$propagateResult$3(SafeFuture.java:146)
at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863)
at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841)
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2147)
at org.ethereum.beacon.discovery.network.NettyDiscoveryServerImpl.lambda$startServer$1(NettyDiscoveryServerImpl.java:101)
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:590)
at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:557)
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:492)
at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:636)
at io.netty.util.concurrent.DefaultPromise.setSuccess0(DefaultPromise.java:625)
at io.netty.util.concurrent.DefaultPromise.trySuccess(DefaultPromise.java:105)
at io.netty.channel.DefaultChannelPromise.trySuccess(DefaultChannelPromise.java:84)
at io.netty.channel.AbstractChannel$AbstractUnsafe.safeSetSuccess(AbstractChannel.java:990)
at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:578)
at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1334)
at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:600)
at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:579)
at io.netty.handler.logging.LoggingHandler.bind(LoggingHandler.java:230)
at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:602)
at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:579)
at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:973)
at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:260)
at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:356)
at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:842)
Caused by: java.util.concurrent.RejectedExecutionException: Task tech.pegasys.teku.infrastructure.events.AsyncEventDeliverer$QueueReader@1279c4ab rejected from java.util.concurrent.ThreadPoolExecutor@42b81fe8[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0]
at java.base/java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2065)
at java.base/java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:833)
at java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1365)
at tech.pegasys.teku.infrastructure.events.AsyncEventDeliverer.subscribe(AsyncEventDeliverer.java:60)
at tech.pegasys.teku.infrastructure.events.EventChannel.subscribeMultithreaded(EventChannel.java:167)
at tech.pegasys.teku.infrastructure.events.EventChannels.subscribeMultithreaded(EventChannels.java:102)
at tech.pegasys.teku.infrastructure.events.EventChannels.subscribe(EventChannels.java:84)
at tech.pegasys.teku.networking.eth2.ActiveEth2P2PNetwork.startup(ActiveEth2P2PNetwork.java:128)
at tech.pegasys.teku.networking.eth2.ActiveEth2P2PNetwork.lambda$start$0(ActiveEth2P2PNetwork.java:122)
at java.base/java.util.concurrent.CompletableFuture$UniAccept.tryFire(CompletableFuture.java:718)
... 56 more
FAILURE: Build failed with an exception.
- What went wrong:
Execution failed for task ':infrastructure:kzg:test'.
There were failing tests. See the report at: file:///<>/infrastructure/kzg/build/reports/tests/test/index.html
Fix eth-node-prysm debian12 version 4.1.1.1-1 test
Setup minimal config for eth-node-teku
Acceptance criteria:
- test should be running that node starts, and no error
- test upgrade/remove/install
- system.d service is running without error
- dpkg-configure reconfigures config
Client configuration and upgrades
Test if different client versions if configuration changed, can be upgraded.
Setup minimal config for eth-node-lodestar
Acceptance criteria:
- test should be running that node starts, and no error
- test upgrade/remove/install
- system.d service is running without error
- dpkg-configure reconfigures config
Test packages against autopkgtest, if client actually work after install. These are integrations tests for debian.
Re-add configuration packages for configuration milestone
Add reproducible build flags to all clients
Currently running the packaging process, some clients still result in the wrong hash, even though the dependencies are the same and the build environment is reproducible.
Completion criteria:
Check all clients, and run the verify command to see the hash. Please note that lodestar might not be reproducible.
Setup minimal config for eth-node-nethermind
Acceptance criteria:
- test should be running that node starts, and no error
- test upgrade/remove/install
- system.d service is running without error
- dpkg-configure reconfigures config
Setup minimal config for eth-node-besu
Acceptance criteria:
- test should be running that node starts, and no error
- test upgrade/remove/install
- system.d service is running without error
- dpkg-configure reconfigures config
Integrate dh-ethpkg-dotnet
Integrate dotnet building
Research Fedora support
Update Readme
Readme is outdated, needs to be updated with the current supports.
- How to run the project
- Dependencies of project
- How the project works
- FAQ
- Contribution
Fix eth-node-geth debian12 version 1.13.4-1 test
Extend arch support beyond amd64
Backport to debian 11
Setup minimal config for eth-node-prysm
Acceptance criteria:
- test should be running that node starts, and no error
- test upgrade/remove/install
- system.d service is running without error
- dpkg-configure reconfigures config
Seperate config and service packages from client builds
Configs and service packages should be easy to rebuild so configs can be tested and shipped easily.
Setup minimal config for eth-node-lighthouse
Acceptance criteria:
- test should be running that node starts, and no error
- test upgrade/remove/install
- system.d service is running without error
- dpkg-configure reconfigures config
Docker inside chroot
Is it possible to make docker work inside of chroot?
Integrate Integrate dh-ethpkg-golang-bazel or similar
Integrate build environment for bazel
Prysm libs are linked against unused libraries
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/eth-node-prysm/usr/lib/eth-node-prysm/bin/validator debian/eth-node-prysm/usr/lib/eth-node-prysm/bin/beacon-chain were not linked against libdl.so.2 (they use none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/eth-node-prysm/usr/lib/eth-node-prysm/bin/validator debian/eth-node-prysm/usr/lib/eth-node-prysm/bin/beacon-chain were not linked against libresolv.so.2 (they use none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/eth-node-prysm/usr/lib/eth-node-prysm/bin/validator debian/eth-node-prysm/usr/lib/eth-node-prysm/bin/beacon-chain were not linked against libpthread.so.0 (they use none of the library's symbols)
Setup minimal config for eth-node-geth
Acceptance criteria:
- test should be running that node starts, and no error
- test upgrade/remove/install
- system.d service is running without error
- dpkg-configure reconfigures config
Add github actions
Add build for checking if packages are built
Chroot and dependencies in different repositories
There are two questions here:
- ca-certificates and external repos is a chicken and egg problem
- external repositories are non-standard, also
aptfails to install if adding as such
The main problem here is that the chroot environment requires ca-certificates present to add additional repositories as the repositories are external.
The second problem is that additional repositories are non-uniform, so adding them is not an easy feat.
Add ntp as dependency for all service packages
Time should be synced for nodes.
Node.js reproducibility
Cand node.js projects built with reproducibility in mind? Locking packages does allow for the same dependency, but the build process or hashes of built modules still could be different.
Research: Chroot and reproducibility when it comes to debian
The chroot environment is reproducible, but it points against Debian, which means it is not fully reproducible. It will create different environments at different points in time, which might be a problem.
The same issue might arise using apt install when the latest packages are fetched.
Fix eth-node-lodestar debian12 version 1.13.3-1 test
Integrate dh-ethpkg-java
Golang dependencies and debian conflicting way of packaging
Debian requires packages to be rebuilt into Debian packages, while the clients download from GitHub. This is conflicting, and the dependencies should be the ones defined by the original authors, not the ones in Debian.
Use the new pkgbuilder system
Completion Criteria:
- use pkgbuilder instead of makefile
- integrate into local build
Document structure of node dependency, graph
Explain in docs how ethereum nodes virtual package system works.
Setup minimal config for eth-node-nimbus
Acceptance criteria:
- test should be running that node starts, and no error
- test upgrade/remove/install
- system.d service is running without error
- dpkg-configure reconfigures config
Note: this is both the execution and consensus client configuration
Integrate dh-ethpkg-golang
The build system for dh-ethpkg-golang needs to be integrated
fix eth-node-geth build
error: missing fields
┌─ [email protected]:1:1
│
1 │ name = "eth-node-geth-service-@variant"
│ ^ ty, summary, priority are missing
Add ubuntu lts support
Fix eth-node-nethermind debian12 version 1.21.1-1 test
Failed! - Failed: 1, Passed: 859, Skipped: 11, Total: 871, Duration: 2 m 50 s - Nethermind.Blockchain.Test.dll (net7.0)
Nethermind.AuRa.Test -> /<<PKGBUILDDIR>>/src/Nethermind/Nethermind.AuRa.Test/bin/Release/net7.0/Nethermind.AuRa.Test.dll
Test run for /<<PKGBUILDDIR>>/src/Nethermind/Nethermind.AuRa.Test/bin/Release/net7.0/Nethermind.AuRa.Test.dll (.NETCoreApp,Version=v7.0)
Inhibit nodes to shut down until state is sync
Keeping a node online
Your node doesn't have to be online all the time, but you should keep it online as much as possible to keep it in sync with the network. You can shut it down to restart it, but keep in mind that:
Shutting down can take a few minutes if the recent state is still being written on disk.
Forced shut downs can damage the database requiring you to resync the entire node.
Your client will go out of sync with the network and will need to resync when you restart it. While the node can begin syncing from were it was last shutdown, the process can take time depending on how long it has been offline.
eth-node-geth build is failing, specification file is not correct
error: missing fields
┌─ [email protected]:1:1
│
1 │ name = "eth-node-geth-service-@variant"
│ ^ ty, summary, priority are missing
Integrate dh-ethpkg-rust
Integrate dh-ethpkg-rust
Add validator running services for ALL clients
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.