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

issue that seems to be going well at the first but eventually gets stuck (Full node) #2804

Open
jungrae-prestolabs opened this issue Mar 15, 2024 · 0 comments

Comments

@jungrae-prestolabs
Copy link

jungrae-prestolabs commented Mar 15, 2024

Detail

  • binary version: conflux conflux-rust/v2.3.4-b9befd1-20240118/x86_64-linux-gnu/rustc1.73.0
  • Snapshot: conflux-fullnode-db-snapshot-2024-03-12.tgz

Run full node procedure;

  1. download binary
  2. unzip it
  3. download snapshot
  4. tar -xfzf it
  5. move blockchain_data, pos_db from snapshot content into run folder
  6. edit the hydra.toml
  7. start.sh start the node

Few hours later every new start, it got stuck with [shared-mem] INFO core/src/pos/mempool/shared_mempool/coordinator.rs:250 {"event":"live","name":"g_c_runtime"} message from log/pos.log.

The weird thing is just restarting process make stuck issue (but, its not ultimate solution at all)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant