Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stuck sync #2217

Open
Father-Web3 opened this issue Jul 27, 2024 · 4 comments
Open

Stuck sync #2217

Father-Web3 opened this issue Jul 27, 2024 · 4 comments
Labels
s-triage Needs to be reviewed, designed and prioritized

Comments

@Father-Web3
Copy link

What is the bug?
node does not sync

How can it be reproduced? (optional)
{"message":" ███████████████░░░░░░░░░░░░░░░░░░░░░░░░░ 37% | Getting snapshot | 1353/3600 | ETA: 56h40m","timestamp":"2024-07-27T10:19:51.608Z","type":"err","process_id":0,"app_name":"hubble"}
{"message":"\n","timestamp":"2024-07-27T10:19:51.608Z","type":"err","process_id":0,"app_name":"hubble"}

Additional context (optional)
sync stops and does not continues sync process time keeps changing from 44 hours to 66 hours I tried reinstalling vps but same

@github-actions github-actions bot added the s-triage Needs to be reviewed, designed and prioritized label Jul 27, 2024
@Father-Web3
Copy link
Author

Father-Web3 commented Jul 27, 2024

After few tries im getting this error now
image
image

@ATella12

This comment was marked as spam.

@Father-Web3
Copy link
Author

Based on the issue you described, here are some potential solutions that might help try it again

  1. Check node resources: Ensure the node has sufficient CPU, memory, and storage to complete the sync process.
  2. Restart node: Try restarting the node to see if the sync process resumes.
  3. Reset node database: Reset the node's database and restart the sync process from scratch.
  4. Check network connection: Verify the node's connection to the network and ensure it's stable.
  5. Update node software: Ensure the node's software is up-to-date, as newer versions may resolve existing issues.
  6. Check firewall and network configuration: Verify that the node's connection to the network is not blocked by firewalls or network configuration issues.
  7. Increase sync timeout: If the node is timing out during sync, try increasing the sync timeout value.
  8. Use a different snapshot source: If the issue persists, try using a different snapshot source or downloading the snapshot manually.
  9. *Reinstall node software: If none of the above steps work, try reinstalling the node software.

still same issue

@lampungnetworking
Copy link

Screenshot_20240801-111747950

I also experienced this. I have opened the required port, Reset DB Restarted the node but it doesn't produce perfect results, is it because of the apikey limit?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s-triage Needs to be reviewed, designed and prioritized
Projects
None yet
Development

No branches or pull requests

3 participants