Open userbox020 opened 1 year ago
adriantpaez
commented
1 year ago Hi @userbox020, and thank you for reporting! Could you provide more context about your setup? If possible, please share your OS, architecture, Sedge version, and the command or sequence of commands that produced the error 🙏🏻
userbox020
commented
1 year ago @adriantpaez sure,
OS:
Distributor ID: Ubuntu
Description: Ubuntu 22.04.3 LTS
Release: 22.04
Codename: jammyArchitecture:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 46 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 48
On-line CPU(s) list: 0-47
Vendor ID: GenuineIntel
Model name: Intel(R) Xeon(R) CPU E5-2678 v3 @ 2.50GHz
CPU family: 6
Model: 63
Thread(s) per core: 2
Core(s) per socket: 12
RAM: 128GBSedge Version:
2023-11-02 01:34:23 -- [INFO] [Logger Init] Log level: info
2023-11-02 01:34:24 -- [INFO] You are running the latest version of sedge. Version: v1.2.3
sedge v1.2.3Sequence of commands:
./sedge cli
2023-11-02 01:39:51 -- [INFO] [Logger Init] Log level: info
2023-11-02 01:39:51 -- [INFO] You are running the latest version of sedge. Version: v1.2.3
? Select network goerli
? Select node type full-node
? Generation path /media/2TB_M2/test/sedge-data
? Container tag, sedge will add to each container and the network, a suffix with the tag
? Do you want to set up a validator? Yes
? Enable MEV Boost? Yes
? Mev-Boost image flashbots/mev-boost:latest
? Insert relay URLs if you don't want to use the default values listed below Default values are listed below. (
? Insert relay URLs if you don't want to use the default values listed below Default values are listed below.
https://0xafa4c6985aa049fb79dd37010438cfebeb0f2bd42b115b89dd678dab0670c1de38da0c4e9138c9290a398ecd9a0b3110@builder-relay-goerli.flashbots.net
https://0x821f2a65afb70e7f2e820a925a9b4c80a159620582c1766b1b09729fec178b11ea22abb3a51f07b288be815a1a2ff516@bloxroute.max-profit.builder.goerli.blxrbdn.com
https://0x8f7b17a74569b7a57e9bdafd2e159380759f5dc3ccbd4bf600414147e8c4e1dc6ebada83c0139ac15850eb6c975e82d0@builder-relay-goerli.blocknative.com
https://0xb1d229d9c21298a87846c7022ebeef277dfc321fe674fa45312e20b5b6c400bfde9383f801848d7837ed5fc449083a12@relay-goerli.edennetwork.io
https://0xb1559beef7b5ba3127485bbbb090362d9f497ba64e177ee2c8e7db74746306efad687f2cf8574e38d70067d40ef136dc@relay-stag.ultrasound.money
? Select execution client geth
? Select consensus client lighthouse
? Select validator client lighthouse
? Validator grace period. This is the number of epochs the validator will wait for security reasons before starting 1
? Graffiti to be used by the validator (press enter to skip it)
? Checkpoint sync URL https://goerli.checkpoint-sync.ethpandaops.io
? Please enter the Fee Recipient address 0xaF371c9b7f94e00e265B5471599a533f3eE02566
? Do you want to expose all ports? Yes
? Select JWT source create
2023-11-02 01:41:18 -- [INFO] Generating JWT secret for client authentication
2023-11-02 01:41:18 -- [INFO] JWT secret generated
2023-11-02 01:41:18 -- [INFO] Generating docker-compose script for current selection of clients
2023-11-02 01:41:18 -- [INFO] Generated docker-compose script for current selection of clients
2023-11-02 01:41:18 -- [INFO] Generating environment file for current selection of clients
2023-11-02 01:41:18 -- [INFO] Generated environment file for current selection of clients
2023-11-02 01:41:18 -- [INFO] Cleaning generated docker-compose and environment files
2023-11-02 01:41:18 -- [INFO] Cleaned generated files
? Select keystore source create
? Select mnemonic source create
? Select passphrase source random
? Withdrawal address 0xaF371c9b7f94e00e265B5471599a533f3eE02566
? Number of validators 1
? Existing validators. This number will be used as the initial index for the generated keystores. 0
2023-11-02 01:41:55 -- [INFO] Generating keystores...
2023-11-02 01:41:55 -- [INFO] Keystores generated successfully
2023-11-02 01:41:55 -- [INFO] Generating deposit data...
2023-11-02 01:41:55 -- [INFO] Deposit data generated successfully
2023-11-02 01:41:56 -- [INFO] Importing validator keys into the validator client...
2023-11-02 01:41:56 -- [INFO] Setting up containers
2023-11-02 01:41:56 -- [INFO] Running command: docker compose -f /media/2TB_M2/test/sedge-data/docker-compose.yml build validator
[+] Building 0.0s (0/0) docker:default
2023-11-02 01:41:56 -- [INFO] Running command: docker compose -f /media/2TB_M2/test/sedge-data/docker-compose.yml pull validator
[+] Pulling 1/1
✔ validator Pulled 2.0s
2023-11-02 01:41:58 -- [INFO] Running command: docker compose -f /media/2TB_M2/test/sedge-data/docker-compose.yml create validator
[+] Creating 2/0
✔ Container sedge-validator-blocker Created 0.0s
✔ Container sedge-validator-client Recreated 0.0s
2023-11-02 01:41:58 -- [INFO] Running command: docker build -t sedge/validator-import-lighthouse --build-arg NETWORK=goerli --build-arg LH_VERSION=sigp/lighthouse:v4.3.0 /tmp/sedge-validator-import-context-2059151183
[+] Building 1.7s (11/11) FINISHED docker:default
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 492B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/library/debian:stable-20221004-slim 1.6s
=> [1/7] FROM docker.io/library/debian:stable-20221004-slim@sha256:92ed72016796475ea1f18f84cd8e2f8519ece3a9ea27fdde1157464078ea5371 0.0s
=> [internal] load build context 0.0s
=> => transferring context: 640B 0.0s
=> CACHED [2/7] RUN apt-get update && apt-get install -y curl 0.0s
=> CACHED [3/7] RUN version=$(echo sigp/lighthouse:v4.3.0 | cut -d':' -f 2) && curl -L https://github.com/sigp/lighthouse/releases/download/$version/lighthouse-$version-x86_64-unknow 0.0s
=> CACHED [4/7] RUN tar -xvf lh.gz 0.0s
=> CACHED [5/7] COPY validator-init.sh . 0.0s
=> CACHED [6/7] RUN chmod +x validator-init.sh 0.0s
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:a27324bbaff092eb764a8eb3d914324ce304be5f400a91f95b68086a86a50157 0.0s
=> => naming to docker.io/sedge/validator-import-lighthouse 0.0s
2023-11-02 01:42:00 -- [INFO] Importing validator keys
2023-11-02 01:42:00 -- [INFO] The keys import container is starting
2023-11-02 01:42:01 -- [FATA] validator import container exited with non-zero exit code: validator-import service container with id c066a30f3b02bce217179177219270cd97ee57ef3615875863c4ca455ee933d0 ends with status code 132. Here are the logs for more details:
Found validator key in /keystore/validator_keys/keystore-m_12381_3600_0_0_0.json
Importing validator...
Running account manager for goerli network
Nov 02 07:42:00.951 WARN CPU seems incompatible with optimized Lighthouse build, advice: If you get a SIGILL, please try Lighthouse portable build
validator-dir path: "/data/validators"
WARNING: DO NOT USE THE ORIGINAL KEYSTORES TO VALIDATE WITH ANOTHER CLIENT, OR YOU WILL GET SLASHED.
Keystore found at "/keystore/validator_keys/keystore-m_12381_3600_0_0_0.json":
- Public key: 0x8e1726c508a81f9bfacdfa9c008e88c8cf0e80c5346980e920840d849b2c54159e7cd8c22e7ac636339e45491b791034
- UUID: 9f3b1141-7bf0-4cf6-929d-9b40c10e549f
If you enter the password it will be stored as plain-text in validator_definitions.yml so that it is not required each time the validator client starts.
Enter the keystore password, or press enter to omit it:
Illegal instruction (core dumped)I'm not expert but seems validator part raising the error
userbox020
commented
1 year ago @adriantpaez I have been looking at sedge source code and I can confirm the Core Dump Error it was generated by the validator pipeline. No idea how to solve it because I'm not a programmer, any help would be appreciate.
userbox020
commented
1 year ago Sup bro @adriantpaez nobody supporting the project for goerli validators?
hello im installing geth, lighthouse, lighthouse and after the keystore password step i get the follow error and it exit