farcasterxyz / hub-monorepo

Implementation of the Farcaster Hub specification and supporting libraries for building applications on Farcaster
https://www.thehubble.xyz
MIT License
712 stars 414 forks source link

Stuck sync #2217

Open Father-Web3 opened 4 months ago

Father-Web3 commented 4 months ago

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

Father-Web3 commented 4 months ago

After few tries im getting this error now image image

ATella12 commented 3 months ago

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.
Father-Web3 commented 3 months ago

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 commented 3 months ago

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?