search

Layr-Labs / eigenda-operator-setup

Quick start setup guide for EigenDA
MIT License
80 stars 78 forks source link

EigenDA TVL in top 200 but getting "Complete an Error cycle...." in logs constantly and not signing batches #39

Closed spidey-169 closed 8 months ago

spidey-169 commented 8 months ago

Hi,

My EigenDA operator is currently not signing blocks, and only showing the "Complete an Error Cycle...." message in the logs. I have registered my operator, delegated to it from another address and ensured that my .env file has the correct parameters.

https://goerli.eigenlayer.xyz/operator/0x866a3529d9d6abc8d0d73433fcf0926105727c07

I used the official docs to setup my DA, and using Ubuntu 22.04, 1TB HDD, 8GB Ram adn 4 CPU

This is the screenshot confirming operator registration and details

Screen Shot 2024-01-15 at 11 43 20 PM

When I start my EigenDA, it immediately starts giving me the error message ""Complete an Error Cycle...." as shown here

Screen Shot 2024-01-15 at 11 25 44 PM

I have ensured that the BLS,ECDSA key paths are correct and same in both .env and docker_compose.yml and I am using 0.2.1 release

This is the screenshot confirming it successfully opted in

Screen Shot 2024-01-15 at 11 20 50 PM

Here are the settings for my .env file

Screen Shot 2024-01-15 at 11 10 37 PM

My DA can't seem to get outside the "Complete an Error cycle...." message log, and I have tried restaerting node, Opting-again and Recreating docker containers too.

I have also sent a message in the support link, but wanted to open an issue as I saw a few other folks facing the same issue.

acomg commented 8 months ago

Did you enter your IP in [NODE_HOSTNAME]?

spidey-169 commented 8 months ago

I am using 'localhost' currently. Should that be an issue? I have confirmed with a few others that should be fine

shrimalmadhur commented 8 months ago

I am using 'localhost' currently. Should that be an issue? I have confirmed with a few others that should be fine

Yes. It should be a publicly available IP. although the node software already updated it if you see the screenshot 88.99.3.143. Is this a public IP? If our disperser cannot reach it on port 32005 you won't be able to receive traffic.

spidey-169 commented 8 months ago

I am using 'localhost' currently. Should that be an issue? I have confirmed with a few others that should be fine

Yes. It should be a publicly available IP. although the node software already updated it if you see the screenshot 88.99.3.143. Is this a public IP? If our disperser cannot reach it on port 32005 you won't be able to receive traffic.

It works now, I think for some reason 32004 wasn't accessible and that was causing the issue. Thanks for resolving the issue.

spidey-169 commented 8 months ago

Issue solved. Thanks