ETH2 Beacon Chain validator lighthouse version2.3 was restart over 100 times

0

As title said, I upgrade my beacon chain validator client, lighthouse from 2.01 to 2.30, the network is ok for infura endpoints. And my lighthouse log show that the process is restart again and again from a " signal", but I have never kill the process manually.

I have contact the lighthouse developer in discord last night and we try many ways : delete the old data and rebuild, check the account for directory and fix service config ,etc... but the client is restarting again and again. So he advise me to find the AWS support for some system layer reasons. Thank you for you kindness! I am slashed by the ETH Council mechanisms because of I am down, for a loss about 20 -50 US dollars per day... So pls help me to stop the leak..

Thank you !

You can see this:

Jun 04 07:24:05 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:05.163 WARN Syncing eth1 block cache est_blocks_remaining: initializing deposits, service: slot_notifier Jun 04 07:24:12 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:12.269 WARN Error processing HTTP API request method: GET, path: /eth/v1/validator/duties/proposer/123706, status: 503 Service Unavailable, elapsed: 203.36992ms Jun 04 07:24:12 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:12.269 WARN Error processing HTTP API request method: POST, path: /eth/v1/validator/duties/attester/123706, status: 503 Service Unavailable, elapsed: 284.612105ms Jun 04 07:24:12 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:12.558 WARN Error processing HTTP API request method: POST, path: /eth/v1/validator/duties/attester/123707, status: 503 Service Unavailable, elapsed: 508.545µs Jun 04 07:24:13 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:13.572 INFO Sync state updated new_state: Evaluating known peers, old_state: Stalled, service: sync Jun 04 07:24:14 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:14.462 INFO Sync state updated new_state: Stalled, old_state: Evaluating known peers, service: sync Jun 04 07:24:17 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:17.060 WARN Low peer count peer_count: 0, service: slot_notifier Jun 04 07:24:17 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:17.061 INFO Searching for peers current_slot: 3958619, head_slot: 3958240, finalized_epoch: 123693, finalized_root: 0x2cdf…f3fb, peers: 0, service: slot_notifier Jun 04 07:24:17 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:17.061 WARN Syncing eth1 block cache est_blocks_remaining: initializing deposits, service: slot_notifier Jun 04 07:24:23 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:23.063 WARN Error processing HTTP API request method: GET, path: /eth/v1/validator/duties/proposer/123706, status: 503 Service Unavailable, elapsed: 187.939µs Jun 04 07:24:23 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:23.065 WARN Error processing HTTP API request method: POST, path: /eth/v1/validator/duties/attester/123706, status: 503 Service Unavailable, elapsed: 64.754µs Jun 04 07:24:23 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:23.068 WARN Error processing HTTP API request method: POST, path: /eth/v1/validator/duties/attester/123707, status: 503 Service Unavailable, elapsed: 68.668µs Jun 04 07:24:28 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:28.859 INFO Sync state updated new_state: Syncing Finalized Chain, old_state: Stalled, service: sync Jun 04 07:24:29 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:29.076 INFO Syncing est_time: --, distance: 380 slots (1 hr 16 mins), peers: 2, service: slot_notifier Jun 04 07:24:29 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:29.159 WARN Syncing eth1 block cache est_blocks_remaining: initializing deposits, service: slot_notifier Jun 04 07:24:35 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:35.059 WARN Error processing HTTP API request method: POST, path: /eth/v1/validator/duties/attester/123706, status: 503 Service Unavailable, elapsed: 173.062µs Jun 04 07:24:35 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:35.174 WARN Error processing HTTP API request method: GET, path: /eth/v1/validator/duties/proposer/123706, status: 503 Service Unavailable, elapsed: 8.127441ms Jun 04 07:24:35 ip-172-31-20-245 lighthouse[14902]: Jun 04 07:24:35.359 WARN Error processing HTTP API request method: POST, path: /eth/v1/validator/duties/attester/123707, status: 503 Service Unavailable, elapsed: 131.716µs Jun 04 07:24:42 ip-172-31-20-245 systemd[1]: lighthousebeacon.service: Main process exited, code=killed, status=9/KILL Jun 04 07:24:42 ip-172-31-20-245 systemd[1]: lighthousebeacon.service: Failed with result 'signal'. Jun 04 07:24:47 ip-172-31-20-245 systemd[1]: lighthousebeacon.service: Scheduled restart job, restart counter is at 122. Jun 04 07:24:47 ip-172-31-20-245 systemd[1]: Stopped Lighthouse Eth2 Client Beacon Node. Jun 04 07:24:47 ip-172-31-20-245 systemd[1]: Started Lighthouse Eth2 Client Beacon Node. Jun 04 07:24:47 ip-172-31-20-245 lighthouse[15860]: Jun 04 07:24:47.930 INFO Logging to file path: "/var/lib/lighthouse/beacon/logs/beacon.log" Jun 04 07:24:47 ip-172-31-20-245 lighthouse[15860]: Jun 04 07:24:47.933 INFO Lighthouse started version: Lighthouse/v2.3.0-6f73298 Jun 04 07:24:47 ip-172-31-20-245 lighthouse[15860]: Jun 04 07:24:47.934 INFO Configured for network name: mainnet Jun 04 07:24:47 ip-172-31-20-245 lighthouse[15860]: Jun 04 07:24:47.954 INFO Data directory initialised datadir: /var/lib/lighthouse Jun 04 07:24:47 ip-172-31-20-245 lighthouse[15860]: Jun 04 07:24:47.954 WARN Running HTTP server on port 5052

  • Hi.

    I think you are asking about issues after updating the Ethereum Client.
    How does your system relate to AWS? Are you using an AWS Managed Block chain? We recommend that you select the appropriate tag.

    If you have nothing to do with AWS, you may want to post to the Ethereum forums.

asked 2 years ago591 views
1 Answer
0

I can't find the appropriate tags... and I have fix it , thanks for your anwser~!

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions